From: Patrick McHardy <kaber@trash.net>
To: Gil Beniamini <gil.beniamini@gmail.com>
Cc: David Miller <davem@davemloft.net>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: SOCK_RAW does not receive broadcast (with VLAN unless PROMISC)
Date: Tue, 09 Jun 2009 13:40:34 +0200 [thread overview]
Message-ID: <4A2E4A32.1060705@trash.net> (raw)
In-Reply-To: <91ac27070906090427k6f57745xc72f9fcb6801957a@mail.gmail.com>
Gil Beniamini wrote:
> 9Jun09, The problem was seen with eth1 using driver e1000e, but also
> was reproduced on 3c59x, to me it seems that the problem is not
> related to a specific nic driver.
> VLAN is running for other NICs, but on the application specific nic
> (eth1) I use PF_PACKET (SOCK_RAW) , in order to get the raw-packet
> from the underlying device, and this start working again (like in
> older kernel) as soon as the application set the socket to PROMISC
> mode.
OK, that might explain it. e1000e performs VLAN filtering in hardware
and unless there are VLANs configured locally, all VLANs are filtered
out. Are you seeing seeing only unicast VLAN traffic or no VLAN traffic
at all? Please post a dump of the packets with and without promiscous
mode.
next prev parent reply other threads:[~2009-06-09 11:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <91ac27070906081105x30171bedra10d244d382a6934@mail.gmail.com>
2009-06-08 21:34 ` SOCK_RAW does not receive broadcast (with VLAN unless PROMISC) David Miller
2009-06-09 10:59 ` Patrick McHardy
2009-06-09 11:27 ` Gil Beniamini
2009-06-09 11:40 ` Patrick McHardy [this message]
2009-06-09 13:08 ` Gil Beniamini
2009-06-09 13:14 ` Patrick McHardy
2009-06-09 19:30 ` Brent Cook
2009-06-10 14:24 ` Gil Beniamini
2009-06-10 14:32 ` Patrick McHardy
2009-06-10 14:48 ` Gil Beniamini
2009-06-10 15:00 ` Patrick McHardy
[not found] ` <20090610170108.7710c64b@tux.DEF.witbe.net>
2009-06-10 15:29 ` Gil Beniamini
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=4A2E4A32.1060705@trash.net \
--to=kaber@trash.net \
--cc=davem@davemloft.net \
--cc=gil.beniamini@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).