From: Steven James <pyro@linuxlabs.com>
To: Jeff Dike <jdike@addtoit.com>
Cc: user-mode-linux-devel@lists.sourceforge.net,
Paolo Giarrusso <blaisorblade@yahoo.it>,
"Stephens, Allan" <allan.stephens@windriver.com>,
user-mode-linux-user@lists.sourceforge.net
Subject: Re: [uml-devel] [uml-user] Promiscuous mode interface bug?
Date: Fri, 4 Aug 2006 09:01:21 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.63.0608040840520.5542@localhost.localdomain> (raw)
In-Reply-To: <20060803214501.GA5677@ccure.user-mode-linux.org>
On Thu, 3 Aug 2006, Jeff Dike wrote:
> On Thu, Aug 03, 2006 at 01:08:51PM -0700, Stephens, Allan wrote:
>> Where I think my confusion is arising is in the details of how the
>> filtering
>> controlled by the promiscuous setting is actually done. If a packet
>> with
>> the "wrong" destination address arrives at an interface, who checks to
>> see
>> whether the interface has been configured as promiscuous and
>> passes/discards it
>> accordingly? I have naively assumed that this was handled in hardware
>> on the
>> NIC card in a real system, but is it really done by software?
>
> Ah, a light goes on. I believe that it is done on the card.
>
>> What I seem to
>> be
>> observing in my UML testing is that *nobody* is doing this filtering,
>> resulting in
>> unwanted packets being handed to my protocol (which sits directly on top
>> of the
>> Ethernet driver).
>
> And since UML doesn't have "cards", it may be that the driver should do the
> filtering at the bottom layer and it isn't.
IIRC, most but not all cards will do the filtering in hardware unless
they're in promiscuous mode. However if the card is in promiscuous mode or
doesn't support filtering, the next step is when eth_type_trans sets the
pkt_type of the skb to PACKET_OTHERHOST. I remember there being something
odd about the handling of ethernet headers a good while ago.
In any event, doing the filtering in the device would help, but won't work
when it's promisc (for example if tcpdump is running).
G'day,
sjames
>
> Jeff
>
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2006-08-04 13:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 20:08 [uml-devel] [uml-user] Promiscuous mode interface bug? Stephens, Allan
2006-08-03 21:45 ` Jeff Dike
2006-08-04 11:09 ` Paolo Giarrusso
2006-08-04 13:01 ` Steven James [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-08-04 15:25 Stephens, Allan
2006-08-03 16:29 Stephens, Allan
2006-08-03 18:26 ` Jeff Dike
[not found] <3A30AD378ECC6F41A4AC64F18E8B3F7F6E0A21@ala-mail04.corp.ad.wrs.com>
2006-08-02 15:04 ` Paolo Giarrusso
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=Pine.LNX.4.63.0608040840520.5542@localhost.localdomain \
--to=pyro@linuxlabs.com \
--cc=allan.stephens@windriver.com \
--cc=blaisorblade@yahoo.it \
--cc=jdike@addtoit.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=user-mode-linux-user@lists.sourceforge.net \
/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