All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: "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: Thu, 3 Aug 2006 14:26:12 -0400	[thread overview]
Message-ID: <20060803182612.GA4606@ccure.user-mode-linux.org> (raw)
In-Reply-To: <3A30AD378ECC6F41A4AC64F18E8B3F7F6E0E40@ala-mail04.corp.ad.wrs.com>

On Thu, Aug 03, 2006 at 09:29:51AM -0700, Stephens, Allan wrote:
> These differences may make sense to people who understand how the
> various transport mechanisms work, but it still leave me with a
> question: why, in the latter two cases, is UML allowing non-promiscuous
> interfaces to receive traffic that wasn't sent to them?  I can
> understand that configuring uml_switch as a hub means that packets may
> be forwarded to places they don't need to go, but shouldn't these
> packets still be filtered out somewhere further down the line?  As I
> naive user, I'm not expecting a (simulated) interface to receive traffic
> that wasn't addressed to it unless it has been explicitly configured as
> promiscuous.

Either you or I have a very basic misunderstanding of how these things
are supposed to work.  

You seem to be thinking that when you set an interface promiscuous, it
somehow reaches out to the switch and tells it to start sending it
everything, and when it is set non-promiscuous, it tells the switch to
only send stuff addressed to it.

I seem to be thinking that the packets that actually reach the
interface is not controlled by its promiscuous setting, and the
setting controls whether the packets reach the network stack and are
visible to software.

Needless to say, I think my thinking is closer to the truth.  There is
no mechanism that I know of for an interface to communicate its
promiscuous setting to a switch.  Switches do remember the MAC
associated with a port, but that is done by sniffing the packets going
by.

				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

  reply	other threads:[~2006-08-03 18:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-03 16:29 [uml-devel] [uml-user] Promiscuous mode interface bug? Stephens, Allan
2006-08-03 18:26 ` Jeff Dike [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-08-04 15:25 Stephens, Allan
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
     [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=20060803182612.GA4606@ccure.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --cc=allan.stephens@windriver.com \
    --cc=blaisorblade@yahoo.it \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.