"
Do you happen to have any firewall rules involving the bogons alias? Either the alias or how it's interpreted seems to have changed.
https://forum.opnsense.org/index.php?topic=47827.0
https://forum.opnsense.org/index.php?topic=47827.0
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages1
#2
25.1, 25.4 Production Series / (Possible?) New/Updated Bogons list breaks all sorts of stuff
July 02, 2025, 07:50:34 PM
As best as I can tell this must have recently changed as all sorts of stuff started acting strangely and I see a bunch of other people reporting similar odd issues.
The bogons alias includes, in addition to bogons, !10.0.0.0/8, !172.16.0.0/12, !192.16.0.0/16, etc. This is fine if you're using it alone in a rule to block as-intended, but if you've e.g. added it into an additional alias with private networks and are blocking on that...suddenly things can go haywire. E.g. a rule that *was* blocking "bogons and private IPs would now potentially be blocking bogons and NONPRIVATE IPs which is...unexpected.
The bogons alias includes, in addition to bogons, !10.0.0.0/8, !172.16.0.0/12, !192.16.0.0/16, etc. This is fine if you're using it alone in a rule to block as-intended, but if you've e.g. added it into an additional alias with private networks and are blocking on that...suddenly things can go haywire. E.g. a rule that *was* blocking "bogons and private IPs would now potentially be blocking bogons and NONPRIVATE IPs which is...unexpected.
#3
25.1, 25.4 Production Series / New/Updated Bogons list breaks all sorts of stuff
July 02, 2025, 07:50:04 PM
As best as I can tell this must have recently changed as all sorts of stuff started acting strangely and I see a bunch of other people reporting similar odd issues.
The bogons alias includes, in addition to bogons, !10.0.0.0/8, !172.16.0.0/12, !192.16.0.0/16, etc. This is fine if you're using it alone in a rule to block as-intended, but if you've e.g. added it into an additional alias with private networks and are blocking on that...suddenly things can go haywire. E.g. a rule that *was* blocking "bogons and private IPs would now potentially be blocking bogons and NONPRIVATE IPs which is...unexpected.
The bogons alias includes, in addition to bogons, !10.0.0.0/8, !172.16.0.0/12, !192.16.0.0/16, etc. This is fine if you're using it alone in a rule to block as-intended, but if you've e.g. added it into an additional alias with private networks and are blocking on that...suddenly things can go haywire. E.g. a rule that *was* blocking "bogons and private IPs would now potentially be blocking bogons and NONPRIVATE IPs which is...unexpected.
Pages1
