From: Patrick McHardy <kaber@trash.net>
To: David Miller <davem@davemloft.net>
Cc: gil.beniamini@gmail.com, 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 12:59:03 +0200 [thread overview]
Message-ID: <4A2E4077.8080407@trash.net> (raw)
In-Reply-To: <20090608.143454.161329513.davem@davemloft.net>
David Miller wrote:
> From: Gil Beniamini <gil.beniamini@gmail.com>
> Date: Mon, 8 Jun 2009 21:05:25 +0300
>
>> My application is using PF_PACKET and SOCK_RAW in order to receive all
>> Ethernet packets for the machine-unicast MAC plus all broadcast
>> packets (like ARP broadcast).
>
>> That worked OK with kernel 2.6.20 (Ubuntu 7.04 with or without VLAN).
>>
>> Now with kernel 2.6.28 (Ubuntu 9.04) it works OK only without-VLAN,
>> but with VLAN the application receive only packets for the
>> machine-unicast MAC, but no broadcast (like ARP broadcast) packets,
>> only if I set the socket to PROMISC mode, I start receive also
>> broadcast packets.
Which driver are you using? Are you sniffing on the VLAN device
or on the underlying device?
next prev parent reply other threads:[~2009-06-09 10:59 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 [this message]
2009-06-09 11:27 ` Gil Beniamini
2009-06-09 11:40 ` Patrick McHardy
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=4A2E4077.8080407@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).