igb stats double counting in 12-CURRENT r319025
Hi everyone, I have noticed my networking statistics appear to be double counting on two of my FreeBSD 12-CURRENT boxes running r319025. Could someone please help me to find the problem (I believe it is likely to be a bug in the networking driver). I discovered the double counting by comparing the output of "systat -ifstat" (which reports 988 KB/s) with the output of "iftop -B" (which reports 491 KB/s). I know that iftop is the correct one, because my internet speed only gives me around ~500 KB/s unfortunately. # systat -ifstat -match igb0 ... Interface Traffic PeakTotal igb0 in988.008 KB/s988.008 KB/s 36.295 GB out16.953 KB/s 16.953 KB/s 295.774 GB # iftop -i igb0 -B ... TX: cum: 31.7KB peak: 9.69KB rates: 9.69KB 7.92KB 7.92KB RX:1.54MB 491KB 491KB 394KB 394KB The two interfaces in these boxes are: $ pciconf -lvv | grep igb1 -A4 igb1@pci0:4:0:0:class=0x02 card=0x8086 chip=0x15398086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = 'I211 Gigabit Network Connection' class = network subclass = ethernet $ pciconf -lvv | grep igb0 -A4 igb0@pci0:8:0:0:class=0x02 card=0x15331849 chip=0x15338086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = 'I210 Gigabit Network Connection' class = network subclass = ethernet Regards, Ben -- From: Benjamin Woods woods...@gmail.com ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 219699] Issue with IPv6 and neighbor notification
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219699 --- Comment #7 from Paul G Webster --- A little more on this fault; with the help of the host we have a working solution, from the host them self: --quote FreeBSD appears to use the link local address on the interface to send neighbor advertisements for the addresses it would like to be routed towards it, unfortunately our side only allows you to send neighbor advertisements from an allowed allocated prefix not an fe80:: address. I have added an exception for this, could you try stopping your work around for now and seeing if IPv6 carries on working? --/quote To cut a story short and many tickets later yes in fact the work around did work, the host is using 'ebtables' on there host; they have contacted the panel provider hoping they can patch the upstream. Will update if I can get a little more detail on what the patch was or a copy of it hopefully :) -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 219699] Issue with IPv6 and neighbor notification
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219699 --- Comment #8 from Paul G Webster --- The host provided the following information for what they had to do with ebtables to get freebsd working; --quote We use ebtables on the hosts to prevent IP stealing. We have a chain setup for each VM which basically says "this VMs mac can only use these IPs", this is what was dropping your v6 NA's. The patch to allow the link local address is simply: ebtables -A kvm922.0 -p IPv6 --ip6-src fe80::/10 -j ACCEPT With kvm922.0 being the chain that your VM belongs to. --/quote -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 219428] em network driver broken in current
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219428 --- Comment #5 from gitdev --- Created attachment 183184 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=183184&action=edit dmesg from affected system Boot output from affected system, amd64 with atom D525 booting 12-CURRENT r319167. There should be em0-em5 ethernet devices recognized, and em3-em5 configured as a bridge. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 219428] em network driver broken in current
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219428 --- Comment #6 from gitdev --- Created attachment 183187 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=183187&action=edit debug output Debug output for r319481 on amd64 panic: Assertion adapter->tx_num_queues > 0 failed at /usr/src/sys/dev/e1000/if_em.c:2664 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 213814] AWS/EC2: no egress traffic stats on ixv(4) xn(4)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213814 Kubilay Kocak changed: What|Removed |Added Priority|--- |Normal Summary|AWS/EC2: no egress traffic |AWS/EC2: no egress traffic |stats on ixv(4) |stats on ixv(4) xn(4) CC||freebsd-virtualization@Free ||BSD.org Assignee|freebsd-virtualization@Free |freebsd-net@FreeBSD.org |BSD.org | Flags||mfc-stable11? Keywords||needs-qa, regression Status|New |Open --- Comment #11 from Kubilay Kocak --- Re-assign to more appropriate ML (freebsd-net), cc'ing original ML (virtualization). -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
