From: Nolwenn <donolwenn@gmail.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: hayeswang <hayeswang@realtek.com>, netdev@vger.kernel.org
Subject: Re: Possible bug with r8169 driver
Date: Sat, 29 Sep 2012 14:49:30 +0000 [thread overview]
Message-ID: <2565578.vyFL3Bzlf9@bureau> (raw)
In-Reply-To: <20120929072028.GA3730@electric-eye.fr.zoreil.com>
[-- Attachment #1: Type: text/plain, Size: 1337 bytes --]
Le samedi 29 septembre 2012 09:20:28 Francois Romieu a écrit :
> > > Can you send an 'ip -s link' before any ipv6 traffic flows, then
> > > after ?
> >
> > Before ipv6 traffic
> >
> > % ip -s link
>
> /me plugs brain and realizes that the driver does not update the device
> stats multicast field.
>
> The multicast stats will appear in the output of 'ethtool -S eth0'.
>
> Can you send two complete binary tcpdump captures (w/o -p option) in the
> same contexts ?
>
Before tcpdump and some mail checking
# ethtool -S eth0
NIC statistics:
tx_packets: 3309
rx_packets: 4672
tx_errors: 0
rx_errors: 0
rx_missed: 0
align_errors: 0
tx_single_collisions: 0
tx_multi_collisions: 0
unicast: 4672
broadcast: 0
multicast: 0
tx_aborted: 0
tx_underrun: 0
After tcpdump wihout mail checking
# ethtool -S eth0
NIC statistics:
tx_packets: 302
rx_packets: 491
tx_errors: 0
rx_errors: 0
rx_missed: 0
align_errors: 0
tx_single_collisions: 0
tx_multi_collisions: 0
unicast: 299
broadcast: 82
multicast: 110
tx_aborted: 0
tx_underrun: 0
The two dumps are attached (I hope it's what Michel wants !)
tcpdump -pw dump-eth0-promisc-off
tcpdump -w dump-eth0-promisc-on
[-- Attachment #2: dump-eth0-promisc-off --]
[-- Type: application/vnd.tcpdump.pcap, Size: 19747 bytes --]
[-- Attachment #3: dump-eth0-promisc-on --]
[-- Type: application/vnd.tcpdump.pcap, Size: 72227 bytes --]
next prev parent reply other threads:[~2012-09-29 14:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-27 14:24 Possible bug with r8169 driver Nolwenn
2012-09-27 22:21 ` Francois Romieu
2012-09-28 6:47 ` Nolwenn
2012-09-29 7:20 ` Francois Romieu
2012-09-29 14:49 ` Nolwenn [this message]
2012-09-29 19:01 ` Francois Romieu
2012-09-30 19:17 ` Nolwenn
2012-10-01 5:51 ` hayeswang
2012-10-01 18:56 ` Francois Romieu
2012-10-04 2:09 ` hayeswang
2012-11-07 9:54 ` Nolwenn
2012-11-07 19:06 ` Francois Romieu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2565578.vyFL3Bzlf9@bureau \
--to=donolwenn@gmail.com \
--cc=hayeswang@realtek.com \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox