Messages

I am also having this issue. 
Sometimes the gateway comes back but I had a situation today where it dropped about midnight and was still down at 5am even though i could ping the monitor address from Opnsense. 
This has only started to become a problem since 26.1 - was fine on 25.7.11_4.   Editing and applying nothing on the gateway config gets it going again.

Check the shortcut you're using to get to Opnsense.
It might have some trailing stuff that has state information in it that is no longer valid.
This bit me on the behind once too.

So it seems Google backups aren't a thing anymore so I set up Git backup which worked great.  For 8 commits.
I haven't changed anything at the Git end but Opnsense seems to think there are changes at that end that it won't overwrite.
The following is in the system log:

git-backup git out of sync (To ssh://... ! [rejected] master -> master (fetch first) error: failed to push some refs to 'ssh://github.com/...'; hint: Updates were rejected because the remote contains work that you do not hint: have locally. This is usually caused by another repository pushing to hint: the same ref. If you want to integrate the remote changes, use hint: 'git pull' before pushing again. hint: See the 'Note about fast-forwards' in 'git push --help' for details.

I certainly have got better things to do than edit files on github and the repo is private which i checked 88 times when I set it up.
Anyone know if this will just happen again if I somehow delete the config backup so it can start again, or a better way to fix this?

I suspect this is an AI post, no such options exist in the UI.

There are a pile of files (35) and directories (9) missing from /usr/local/share/netdata/web.
I copied them from an older OPNsense VM i had from testing something ages ago and it works again.
There are a couple of issues about this logged in Github but they don't seem to be gaining much traction.

My protectli beeper has never worked - until now - has been doing just the very faint clicking.
I know this is old but I thought I would leave this here for future somebody who finds it. 
Updating from AMI bios to Coreboot for another reason has also caused the beeper to suddenly start working.
Hope this helps someone.

The patch has worked for me.
Thanks all.

The SSH banner still shows the old logo rather than the sexy new one.
Loving 25.1 !

Did a clean install then restored a backup. 
Below is a screenshot of the not-great upgrade dashboard in all its glory.
My temperature sensors still look like this though although the logo and network problems are resolved.
A screenshot of just the temperature dashboard widget after the reinstall attached also.

Thought I would post this here - my upgrade didn't go quite right at all.
The first update to _4 went fine.
I normally have 4 gateways showing (2 IP4, 2 IP6).  After the second upgrade to 25.1 three of them were missing and no internet at all.
The UI showed 25.1 as the version but with the old logo and 4 new temperature sensors had appeared with 100 degree readings.
Reverted to pre-upgrade ZFS snapshot and tried again with the same result.
I've gone back to that snapshot again and will clean install tonight after work.  Sorry I didn't get logs but can do another test if required.

Mine too, was also doing it on r1 well before r2 was available but i was on r6 for a minute so may have been to do with that also.

wicked, thank you heaps!

OK, that's done and things have changed.  The output of that is now:
FreeBSD 14.1-RELEASE-p6 stable/24.7-n267981-8375762712f SMP

Hopefully that fixes it and thank you so much for your help!
Out of interest though - what did I do to end up with the wrong kernel?

Opnsense up till now has been rock solid.  I updated to 24.7.11 this morning and have had 4 kernel panics since..
Only one has been submitted for review, but from the dump this seems to be the most relevant part without posting the whole thing:

Dump header from device: /dev/gpt/swapfs
  Architecture: amd64
  Architecture Version: 4
  Dump Length: 78336
  Blocksize: 512
  Compression: none
  Dumptime: 2024-12-18 09:29:41 +1000
  Hostname: my.hostname
  Magic: FreeBSD Text Dump
  Version String: FreeBSD 14.1-RELEASE-p6 stable/24.7-n267979-0d692990122 SMP
  Panic String: pf_build_tcp: unsupported af 0
  Dump Parity: 306338569
  Bounds: 0
  Dump Status: good
 .......

   KDB: enter: panic
panic.txt0600003614730404545  7145 ustarrootwheelpf_build_tcp: unsupported af 0version.txt0600007414730404545  7542 ustarrootwheelFreeBSD 14.1-RELEASE-p6 stable/24.7-n267979-0d692990122 SMP

Any suggestions?

Testing the other day with the first patch seemed to go ok with failing over and then back when unplugging and plugging the WAN cable.  I had a real outage today though and everything failed over to the backup WAN perfectly but then did not come back when the primary was healthy again.
I've just applied Franco's patch 0c9d8c94 now, and tested by unplugging and plugging again and that also worked fine.   

But then I had a thought and tested it by unplugging the coax cable on the primary WAN instead of the NIC,  The failover to backup worked fine but when the coax was reconnected there was presumably no reconnect event and the primary was not detected up again.
After that unplugging and replugging the NIC also didn't fail to the primary until I just clicked Apply in the System-Gateways-Configuration page and the primary came back to life.