From: Paolo Giarrusso <blaisorblade@yahoo.it>
To: Jeff Dike <jdike@addtoit.com>,
"Stephens, Allan" <allan.stephens@windriver.com>
Cc: Paolo Giarrusso <blaisorblade@yahoo.it>,
user-mode-linux-user@lists.sourceforge.net,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] [uml-user] Promiscuous mode interface bug?
Date: Fri, 4 Aug 2006 13:09:49 +0200 (CEST) [thread overview]
Message-ID: <20060804110949.78699.qmail@web25221.mail.ukl.yahoo.com> (raw)
In-Reply-To: <20060803214501.GA5677@ccure.user-mode-linux.org>
Jeff Dike <jdike@addtoit.com> ha scritto:
> 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.
Yes, it is, you can set one (or even more, for special purposes) MAC
addresses to accept on a card or configure it as "no hardware
filtering done"; I've observed a network driver doing this, and I
think set_mac is the hook for this.
> > 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.
I agree too; we may check however if the network stack implements
support for such "dumb" cards (probably by setting a flag) to avoid
coding it ourselves.
Chiacchiera con i tuoi amici in tempo reale!
http://it.yahoo.com/mail_it/foot/*http://it.messenger.yahoo.com
-------------------------------------------------------------------------
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 11:09 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 [this message]
2006-08-04 13:01 ` Steven James
-- 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=20060804110949.78699.qmail@web25221.mail.ukl.yahoo.com \
--to=blaisorblade@yahoo.it \
--cc=allan.stephens@windriver.com \
--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