From: Eric Dumazet <eric.dumazet@gmail.com>
To: netdev@vger.kernel.org
Subject: Re: Problems with dropped packets on bonded interface for 3.x kernels
Date: Mon, 21 Nov 2011 09:02:29 +0100 [thread overview]
Message-ID: <1321862549.17419.12.camel@edumazet-laptop> (raw)
In-Reply-To: <20111121074453.GA7596@china>
Le lundi 21 novembre 2011 à 01:44 -0600, Albert Chin a écrit :
> So only "unknown" protocols are dropped? I just ran tcpdump for 96
> packets and inspected the output. The only packets received are LACP,
> ARP, STP (Spanning Tree Protocol), DTP (Dynamic Trunking Protocol).
> How are these "unknown"?
No protocol handler is setup to analyze some them in your box.
(ARP is handled of course)
Like if you receive IPv6 packets while IPv6 was not compiled/loaded into
your kernel.
Nothing you have to worry about. We receive plenty of unknown packets
these days...
next prev parent reply other threads:[~2011-11-21 8:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-21 5:16 Problems with dropped packets on bonded interface for 3.x kernels Albert Chin
2011-11-21 6:32 ` Eric Dumazet
2011-11-21 7:44 ` Albert Chin
2011-11-21 8:02 ` Eric Dumazet [this message]
2011-11-21 8:08 ` Albert Chin
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=1321862549.17419.12.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
/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