From: Paolo Giarrusso <blaisorblade@yahoo.it>
To: "Stephens, Allan" <allan.stephens@windriver.com>,
user-mode-linux-devel@lists.sourceforge.net
Cc: user-mode-linux-user@lists.sourceforge.net
Subject: Re: [uml-devel] [uml-user] Promiscuous mode interface bug?
Date: Wed, 2 Aug 2006 17:04:43 +0200 (CEST) [thread overview]
Message-ID: <20060802150443.99963.qmail@web25219.mail.ukl.yahoo.com> (raw)
In-Reply-To: <3A30AD378ECC6F41A4AC64F18E8B3F7F6E0A21@ala-mail04.corp.ad.wrs.com>
"Stephens, Allan" <allan.stephens@windriver.com> ha scritto:
> Hi Paolo:
>
> OK, let me take one more try at explaining what I've observed.
> (And my
> apologies for making this whole issue more confusing than necessary
> ...
> I'm pretty inexperienced when it comes to detailing with the
> details of
> network interface operation.)
>
> When I used "ethX=daemon", each interface I configured on a UML
> guest
> forwarded only the traffic that was destined for it to my network
> protocol software -- indicating that the uml_switch application was
> getting UML to filter things correctly.
Does it works corrently even with uml_switch -hub or not?
> When I used "ethX=mcast", each interface I configured on a UML
> guest
> forwarded all packets sent to the associated multicast group to my
> network protocol software
which I guess operates with raw sockets...
>, even though the interfaces were not
> configured as "promiscuous".
> The latter observation was the source of my original concern,
> causing me
> to ask "why doesn't UML mark the device as promiscuous if it is
> passing
> on all packets?". Your subsequent explanations now make me think
> that I
> should have asked "why isn't UML filtering out the unwanted packets
> since the device isn't configured as promiscuous?".
> I just repeated my "ethX=mcast" testing to make sure I hadn't done
> something stupid, like configure both interfaces with the same MAC
> address, but I still see the same result. This leads me to
> conclude
> that there is a real problem with the way UML is filtering packets
> on
> "ethX=mcast" interfaces. Admittedly, I can circumvent this problem
> being by manually configuring the interfaces as promiscuous, but it
> still looks like a bug.
> Does this (finally) make sense?
Yes, it makes a lot of sense (in fact I'm forwarding this to
uml-devel); I have looked at the code but I don't see any really
_obvious_ difference. Everything depends on uml_switch -hub result,
which I'd like to see.
Thanks for your effort meanwhile!
Bye
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 parent reply other threads:[~2006-08-02 15:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3A30AD378ECC6F41A4AC64F18E8B3F7F6E0A21@ala-mail04.corp.ad.wrs.com>
2006-08-02 15:04 ` Paolo Giarrusso [this message]
2006-08-03 16:29 [uml-devel] [uml-user] Promiscuous mode interface bug? Stephens, Allan
2006-08-03 18:26 ` Jeff Dike
-- strict thread matches above, loose matches on Subject: below --
2006-08-03 20:08 Stephens, Allan
2006-08-03 21:45 ` Jeff Dike
2006-08-04 11:09 ` Paolo Giarrusso
2006-08-04 13:01 ` Steven James
2006-08-04 15:25 Stephens, Allan
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=20060802150443.99963.qmail@web25219.mail.ukl.yahoo.com \
--to=blaisorblade@yahoo.it \
--cc=allan.stephens@windriver.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