From: Bill Fink <billfink@mindspring.com>
To: Marco Berizzi <pupilla@hotmail.com>
Cc: <brian.haley@hp.com>, <tushar.n.dave@intel.com>,
<netdev@vger.kernel.org>, <eric.dumazet@gmail.com>
Subject: Re: rx_dropped packets stop with tcpdump running
Date: Sun, 22 Apr 2012 01:13:54 -0400 [thread overview]
Message-ID: <20120422011354.623b08d4.billfink@mindspring.com> (raw)
In-Reply-To: <DUB108-W57C2F8FCF145C20E3B8BF1B2220@phx.gbl>
On Fri, 20 Apr 2012 17:25:28 +0200, Marco Berizzi wrote:
> brian.haley@hp.com wrote:
> > 0x886d or 0x86DD? That second one is IPv6, you might just need to load the module.
>
> here is the tcpdump:
>
> 17:23:25.561398 00:19:99:90:ba:72 > ff:ff:ff:ff:ff:ff, ethertype Unknown (0x886d), length 64:
> 0x0000: 0001 0001 000c 24e2 0001 0019 9990 ba72 ......$........r
> 0x0010: 0000 0500 2304 6364 726f 447b d700 80f8 ....#.cdroD{....
> 0x0020: ffff 20d1 b631 80fa ffff e02b fb30 80fa .....1.....+.0..
> 0x0030: ffff ..
> 17:23:25.561402 00:19:99:90:ba:73 > ff:ff:ff:ff:ff:ff, ethertype Unknown (0x886d), length 64:
> 0x0000: 0001 0001 000c 24e2 0002 0019 9990 ba72 ......$........r
> 0x0010: 6700 5400 6800 7200 6500 7300 6800 6f00 g.T.h.r.e.s.h.o.
> 0x0020: 6c00 6400 0000 3700 3200 0000 0000 0000 l.d...7.2.......
> 0x0030: 0000 ..
FYI, a Google search for "ethertype 886d" revealed that this is
supposedly an Intel ANS probe. See:
http://fixunix.com/networking/337443-packets-broadcasting-every-second.html
-Bill
next prev parent reply other threads:[~2012-04-22 5:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 13:12 rx_dropped packets stop with tcpdump running Marco Berizzi
2012-04-19 13:24 ` Eric Dumazet
2012-04-19 13:28 ` Eric Dumazet
2012-04-19 17:57 ` Dave, Tushar N
2012-04-20 8:34 ` Marco Berizzi
2012-04-20 14:59 ` Brian Haley
2012-04-20 15:25 ` Marco Berizzi
2012-04-22 5:13 ` Bill Fink [this message]
2012-04-25 18:19 ` Dave, Tushar N
2012-05-03 11:08 ` Marco Berizzi
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=20120422011354.623b08d4.billfink@mindspring.com \
--to=billfink@mindspring.com \
--cc=brian.haley@hp.com \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pupilla@hotmail.com \
--cc=tushar.n.dave@intel.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;
as well as URLs for NNTP newsgroup(s).