Interface ERRORS IN counters wrong? Cosmetic issue, bug or real problem?

Started by stefan00, November 05, 2024, 09:36:15 AM

Previous topic - Next topic
Hi,

The ERRORS IN counters show some weird, enormous numbers - in the 10^18 range. Is this cosmetic, a bug, or something wrong? I've seen this counters earlier already, not specific to the latest 24.7 update. Known issue?

screenshot see attachment.

OPNsense 24.7.7-amd64
FreeBSD 14.1-RELEASE-p5

HW: DEC3850

best&thanks,
stefan
OPNsense Hardware:
DEC3850
DEC750
Custom i5-14600K based router
KVM based VM

What is that interface?
I see you have VLANs is that Interface the Parent for those VLANs?

Regards,
S.
Networking is love. You may hate it, but in the end, you always come back to it.

OPNSense HW
APU2D2 - deceased
N5105 - i226-V | Patriot 2x8G 3200 DDR4 | L 790 512G - VM HA(SOON)
N100   - i226-V | Crucial 16G  4800 DDR5 | S 980 500G - PROD

Quote from: Seimus on November 05, 2024, 10:12:39 AM
I see you have VLANs is that Interface the Parent for those VLANs?

Yes, it is. But I don't think that's the problem.

Also, that number does not grow anymore. How could it, there is no chance to have 2^64 events ;-)
OPNsense Hardware:
DEC3850
DEC750
Custom i5-14600K based router
KVM based VM

Its common to see such errors in case you have a Parent interface assigned.
If you have VLANs for example the parent interface should be unassigned.

https://docs.opnsense.org/manual/how-tos/vlan_and_lagg.html#add-vlan-interfaces

Regards,
S.
Networking is love. You may hate it, but in the end, you always come back to it.

OPNSense HW
APU2D2 - deceased
N5105 - i226-V | Patriot 2x8G 3200 DDR4 | L 790 512G - VM HA(SOON)
N100   - i226-V | Crucial 16G  4800 DDR5 | S 980 500G - PROD

Quote from: Seimus on November 05, 2024, 10:59:35 AM
If you have VLANs for example the parent interface should be unassigned.

should, but don't have to ;-)

In this specific case I need to manually configure the link speed/mode since I use a Twinax cable and have some old switch on the other side. Unless manually configured, connection fails.

No IPs assigned on HW interface, no other errors, no errors on the switch side.

So to me it seems like something is wrong with the errors in reporting value.
OPNsense Hardware:
DEC3850
DEC750
Custom i5-14600K based router
KVM based VM

Interesting discovery: netstat shows a similar value, but not exactly the same (shouldn't it?).

root@DEC3850:~ # netstat -I ax0
Name    Mtu Network        Address                            Ipkts                 Ierrs                 Idrop      Opkts                 Oerrs                  Coll
ax0    1500 <Link#5>       f4:90:ea:00:64:37               81075814  18446744073709551500                     0  299476472                     0                     0
ax0       - fe80::%ax0/64  fe80::f690:eaff:fe00:6437%ax0          0                     -                     -          0                     -                     -
root@DEC3850:~ #



OPNsense UI:  18446744073709552000
netstat:      18446744073709551500


It would be pretty interesting to know what's the reason for this strange behavior.

OT: 24 series is awesome, thanks for the hard work :)
OPNsense Hardware:
DEC3850
DEC750
Custom i5-14600K based router
KVM based VM

I think, somewhere on the forum there was a discussion about this. I can not remember what was the reason for those errors...

How ever if you have this setup Parent (assigned) + child Interface (such as VLANs) it tends to sometimes create crazy amount of errors on the Parent. Usually shouldn't cause any performance impact. So you are correct it should be a cosmetic BUG.

Sadly there is no possibility to clear counters on interfaces in FreeBSD, the only way is to reboot the device..

Regards,
S.
Networking is love. You may hate it, but in the end, you always come back to it.

OPNSense HW
APU2D2 - deceased
N5105 - i226-V | Patriot 2x8G 3200 DDR4 | L 790 512G - VM HA(SOON)
N100   - i226-V | Crucial 16G  4800 DDR5 | S 980 500G - PROD