Versions:
OPNsense 25.1.7-amd64
FreeBSD 14.2-RELEASE-p3
OpenSSL 3.0.16
Setup:
2 WAN connections, 1 physical connection to switch, several VLANs, crowdsec & ips (from the "regular" intrusion detection) active on both WAN interfaces, maltrail active on all VLANs, and network configured as router-on-a-stick.
Issue:
I am running ip cams on vlan 1006, which are being streamed to my nas on vlan 1002
The traffic graph correctly shows the traffic of both interfaces, BUT:
it is also showing that exact same traffic going over the default, untagged vlan ("lan_default") where there is no real traffic.
the "top hosts" dots are also showing correctly that there's pretty much no traffic on that default vlan, but the graphs itself do not (see attached screenshot, showing only that default lan)
this same inconsistency also shows on insights, and is not fixed by a reboot, reset of netflow/rrd data, or repair of netflow data.
i've been using opnsense for years, and admittedly i changed too much at once (updating to 25.1.7, rebuilding fw rules back mostly to interface instead of floating because of the number of rules, ....) but have never had an issue like this (that wasn't fixed by resetting the graphs or just rebooting the machine)
so, does anyone have any idea where to go look for this issue ?
OPNsense 25.1.7-amd64
FreeBSD 14.2-RELEASE-p3
OpenSSL 3.0.16
Setup:
2 WAN connections, 1 physical connection to switch, several VLANs, crowdsec & ips (from the "regular" intrusion detection) active on both WAN interfaces, maltrail active on all VLANs, and network configured as router-on-a-stick.
Issue:
I am running ip cams on vlan 1006, which are being streamed to my nas on vlan 1002
The traffic graph correctly shows the traffic of both interfaces, BUT:
it is also showing that exact same traffic going over the default, untagged vlan ("lan_default") where there is no real traffic.
the "top hosts" dots are also showing correctly that there's pretty much no traffic on that default vlan, but the graphs itself do not (see attached screenshot, showing only that default lan)
this same inconsistency also shows on insights, and is not fixed by a reboot, reset of netflow/rrd data, or repair of netflow data.
i've been using opnsense for years, and admittedly i changed too much at once (updating to 25.1.7, rebuilding fw rules back mostly to interface instead of floating because of the number of rules, ....) but have never had an issue like this (that wasn't fixed by resetting the graphs or just rebooting the machine)
so, does anyone have any idea where to go look for this issue ?