Recent posts

#1
General Discussion / Re: Crowdsec v qfeeds
Last post by passeri - Today at 01:16:20 AM
I used free crowdsec and now paid q-feeds. Both are fine. Paid crowdsec is a greater step up in cost than is warranted on value compared with the first paid tier of q-feeds whereas the latter is fair value over either free tier. Just my view.
#2
26.7.9_1 kernel panic in mana(4) on Azure MANA hosts - boot loop Environment
  • OPNsense 26.7.9_1, FreeBSD 15.1-RELEASE-p6, kernel stable/26.7-n284285-1633399de9dd
  • Azure VM Standard_D2s_v5, built from the FreeBSD Foundation freebsd-14_1 image via the opnazure (dmauser) bootstrap
  • Two NICs (hn0 WAN / hn1 LAN). Accelerated Networking is disabled on both NICs in Azure, but the guest still receives a VF depending on host: mana0 on MANA hosts, mce0/mce1 (Mellanox) on others
  • VM is deallocated nightly and started at 07:00, so host/VF type varies day to day

Symptom Since updating to 26.7.9_1 (installed 16 Nov), any boot on a MANA host panics ~13s in, during "Setting up extended sysctls...", then reboots and repeats indefinitely. 2,779 consecutive panics across two outages (713 on 18 Nov, 2,066 between 19/11 and 20/11); 0 panics on any other kernel/VF combination.

Panic
Fatal trap 12: page fault while in kernel mode fault virtual address = 0x70 current process = sysctl ... mana_sysctl_tx_stat_agg_u64()
at mana_sysctl_tx_stat_agg_u64+0xd0 sysctl_root_handler_locked()
... userland_sysctl() ...
sys___sysctl() ...
[full trace attached] 

What the serial console log shows
  • n284285 booted normally on Mellanox hosts (mce0) on 16 and 17 Nov
  • Every n284285 boot on a MANA host (mana0) panicked with the trace above. None succeeded
  • Older kernels (n284159, p4, and n284176, p6) booted cleanly on MANA hosts many times, including a live mana0 detach/reattach
  • A plain restart stays on the same host and keeps looping. Stop/deallocate + start moved the VM to a Mellanox host, and the same kernel booted fine

Possibly related
  • 26.7.9 changelog: "system: invalidate sysctl cache on apply". The panic happens in the sysctl apply step at boot
  • The 26.7.2 boot loops were attributed to reading counters on an interface without allocated counters. This looks like the same class of bug, but in mana(4)

Workaround in place (not yet confirmed on a MANA host) Tunable hint.mana.0.disabled=1 (if_mana is a module, auto-loaded by devmatch on MANA hosts). Will update once it survives a MANA boot. 

Questions
  • Is this a known regression between n284176 and n284285?
  • Is the hint.mana.0.disabled workaround safe/recommended until a fix lands?
#3
26.7, 26.10 Series / Re: [CALL FOR TESTING] Defer P...
Last post by franco - Today at 12:18:17 AM
The patch is for 26.7.10.  I think you just hit a fluke with your ISP.  The patch could help avoid this in the future.


Cheers,
Franco
#4
General Discussion / Re: Internet only vlan with IP...
Last post by Maurice - Today at 12:10:21 AM
Patrick explained how to configure it. Why / how it works: A firewall rule with a gateway directs all matching packets to this gateway, ignoring the routing table (hence "policy routing" - the firewall rule is the policy which makes the routing decision). So all packets coming from the IoT network get sent to your WAN gateway, even if their destination address is in one of your private networks. The upstream gateway then either drops them or sends them back to OPNsense, in which case they get treated like any other packet coming in on the WAN.

Cheers
Maurice
#5
26.7, 26.10 Series / Issue with VLAN hardware offlo...
Last post by ChristopherL - November 19, 2026, 11:44:28 PM
Hi,

Overnight on a couple of devices I have set up for testing, VLAN interfaces would only accept packets when in promiscuous mode.

This didn't affect the parent interface, only the VLAN interfaces bound to it (eg. oce0 could pass packets, but Vlan0100 could not).

I have VLAN hardware offload disabled, but when I enabled that it immediately started working. And when I disabled it again, it continued to work.

These interfaces are linknets between a firewall and a router, so, to eliminate the risk of this happening again, it should be safe to leave them in promiscuous mode. So I have a functioning workaround. But it feels like a fairly significant issue for VLAN interfaces to shut down randomly, and I didn't find any mention of it on FreeBSD mailing lists, so I was wondering if it could be an OPNSense issue?

This may be related: https://github.com/opnsense/core/issues/8429

Versions:
OPNsense 26.10.0p1-amd64
FreeBSD 15.1-RELEASE-p6
OpenSSL 3.5.9
Licensed until 2029-05-08

The Interface details:
Emulex OCe14104B-NX PCIe 10Gb 4-Port SFP+ Ethernet Adapter
#6
General Discussion / Re: Crowdsec v qfeeds
Last post by sopex - November 19, 2026, 11:30:21 PM
I like CrowdSec more but both are fine.
#7
Hardware and Performance / Re: [solved] Intel i226 Firmwa...
Last post by daeona - November 19, 2026, 11:21:08 PM
Hey! I just made an account to post what I learned updating the firmware:

You can try to flash the incorrect size bin to the card but the updater only works if is the correct size one. That way if your ETrackId does not show up in the github list you can try without worry and find out if your card is 1MB or 2MB.

If the updater fails or takes a really long time, try another pcie slot. In my MSI A520M-A PRO the only way that I could flash a card is via the top x1 slot, putting the card in the x16 slot makes the updater fail.

#8
General Discussion / Re: Internet only vlan with IP...
Last post by Patrick M. Hausen - November 19, 2026, 11:05:10 PM
He already wrote that - just as I did for my suggestion.

In your allow rule explicitly set the gateway. There's a "gateway" field in the options.
Just like there is a "destination invert" field in the rule options that you could use with an alias containing your other local networks.
#9
General Discussion / Re: Internet only vlan with IP...
Last post by lancable - November 19, 2026, 10:55:15 PM
Quote from: Maurice on November 19, 2026, 06:53:16 PMA different approach is using policy routing. Create an "allow IOT IPv6 to any" rule with the gateway set to your IPv6 WAN gateway. Then add higher priority rules without a gateway for local services / subnets you want to make accessible.

A little crude, but works.

Cheers
Maurice

Thank you for your answer Maurice! This seems easy and elegant enough!
I dont have much experience with policy routing. Can you tell me why / how this works?

Thanks!
#10
General Discussion / Firewall rule match on (pcp) p...
Last post by vicking - November 19, 2026, 10:55:02 PM
I added three outbound rules to my vlan firewall with protocol, source and destination any and match priority of 7, 6 and one with any as a fallback.

Somehow it always matches the first rule with priority match of 7, even the priority is not 7. The fallback is never reached. So somehow it looks like the match is done on source, protocol and destination and because this is any, it will always be a match..

Is this normal behavior?