Problems with 26.1: Health and Insight

[senseOPN]

Within Health, I can check "Packets" for my enabled interfaces.
Strangely, I also see Interface Groups in the "Subject" selection, but those do not work!
No packets are shown for the groups - so either this is a bug, or the bug is that Interface Groups are shown in the selection.

I can see that the timeline is different, but "Reset Zoom" does not change anything - the screenshots.


Also, when switching to "Traffic" instead of "Packets", I have one Interfaces that does NOT shown any traffic anymore - while for Packets, it can be seen. It seems like this Interface is handled like a Group.

And in Insight, I see daily packets from an Interface where the attached computer is shut down!
I cannot produce traffic, but still it get's shown:

To hunt this down, I let tcpdump run on the firewall to capture those packets - but there are no packets:

root@OPNsense:~ # ls tcpdump_igc4.out
-rw-r--r--  1 root wheel 0 Mar 12 17:45 tcpdump_igc4.out
root@OPNsense:~ # fuser tcpdump_igc4.out
tcpdump_igc4.out: 55959w
root@OPNsense:~ # ps auxwww | grep -w 55959
root    28731   0.0  0.0   13744    2464  0  S+   17:44       0:00.00 grep -w 55959
root    55959   0.0  0.0   21912    7952  0  SC   17:45       0:02.19 tcpdump -i igc4 -n -e -vvv -s 0 -XX -tttt


Yet... see screenshot ... the WebGUI shows them!

[senseOPN]

Not MUCH replies 😅

Nobody knows whether Interface Groups should appear in Health and actually work there?
For me, they appear and do not work!

Who and where to ask, if nobody here knows?!?

And then, the problems that I cannot switch to Traffic in Health instead of Packets - the display is broken!
And it was OK until I updated!

[Patrick M. Hausen]

Open an issue on Github to get developer attention. Stick to the provided template, i.e. fill it in or the bot will de-prioritise your issue.

[OPNenthu]

It may be the case that interface totals in FreeBSD cannot be collected for abstractions like interface groups?  In that case some process in OPNsense would need to aggregate the data for the groups.

Assuming that's true, and if there's no plan to implement that, then I would rather have the groups omitted from RRD and Netflow to de-clutter them.

Let's see what the official response is.