Messages

hotfix directories are merged as single release after subsequent releases to avoid people catching unpatched releases, best never to use hotfix annotation with opnsense-revert.


Cheers,
Franco

Awesome - thanks for confirming that.  Appreciated!

After the upgrade my rules weren't working either. After reading this post I opened my aliases and edited and re-saved each alias and they all started working.

Just sharing that a revert to 22.1.7_1 is the only durable fix for this I've found.  I tried the disable/enable alias trick as well.  It works, but after a reboot the aliases return to not working correctly, and of course neither will the rules that depend on them.

Did you use opnsense-revert to get to 22.1.7_1? Struggling to find the process...thx

Yes, that's correct.  You'll want to run this:

Code Select Expand

opnsense-revert -r 22.1.7_1 opnsense

Then reboot, everything should come back up as it was.  If you can't reboot after install, you can probably do the disable/enable on aliases to bring them up for the current session, and then the reverted opnsense package will handle loading them correctly on the next reboot.

I've tried to revert to 22.1.7_1 using the code snippet above from the CLI, and it appears that there isn't a 22.1.7_1 release - at least I don't see that folder on any of the mirrors I've checked.  Can someone please confirm if that release is correct, or is it just 22.1.7 ? (that folder exists)

I'm still having trouble even with 22.1.8_1, and just need things to work - no time to troubleshoot these days.  If someone could please advise which is the best release to revert to, I'd appreciate it.

OPNsense 21.1.9_1-amd64
FreeBSD 12.1-RELEASE-p19-HBSD
OpenSSL 1.1.1k 25 Mar 2021

Hello all - I'm having an issue with PPPoE not connecting at startup.  The workaround I have is to go into the interface where I disable then re-enable.  After doing this, my PPPoE sessions starts normally.

I have Bell FTTH service in Toronto, Canada.  I use a patched driver to allow for full speed with the GPON module directly connected into my SFP+ NIC:

bxe0: <QLogic NetXtreme II BCM57810 10GbE [BELL BYPASS] (B0) BXE v:1.7>

My interface card has 2 interfaces, and bxe1 is my LAN interface, which works without intervention.  Just my WAN connection via PPPoE on bxe0 (bxe0_vlan35) seems to require the workaround.

I've been simply living with the issue since coming over from pfSense where I didn't have this problem for the last several months.

What additional information can I provide?  I'm going to attach a ppp.log snip with my username and IP address masked.  The connection has been up since the 9th, so no issues at all after working around the initial reluctance to connect.

Thanks in advance,
ST

PS - apologies - I think I've put this in the wrong forum - mods, please move if you can.  Thanks.

Hi all,

I'm new to OPNsense, but have been a long time user of another BSD based firewall with a similar name. ;)

Using that firewall, my existing SNMP monitors on Windows clients would graph smoothly with 1000ms polling.  I seem to only get an update every 3000ms with OPNsense from multiple endpoints, running a mix of Windows OS.

Just wondering if there is a place to change the update frequency on the server side?  I did look through the snmpd.conf man page, but didn't see the obvious answer.

If not - I'll need to modify my monitoring tools to poll less frequently, but I'd prefer to have more frequent updates if possible. (?)

Thanks!

ST