From: Derrik Pates <demon@devrandom.net>
To: "Ronald G. Minnich" <rminnich@lanl.gov>
Cc: Adam Sulmicki <adam@cfar.umd.edu>,
Mark Williamson <maw48@cl.cam.ac.uk>,
xen-devel@lists.sourceforge.net, Kero-Chan <kerochan2@gmail.com>
Subject: Re: VIF setup
Date: Fri, 14 Jan 2005 23:17:41 -0500 [thread overview]
Message-ID: <41E89965.4000709@devrandom.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0501142038560.18474@linux.site>
Ronald G. Minnich wrote:
> Am I the only person who sees this as a tad odd? I can't escape thinking
> about a real bridge. Seems to me each eth or vif you add to a bridge
> should retain its IP and the bridge, basically being a device that does
> mac-layer routing, has no IP.
No, because the IP(s) assigned to a device cause the device to only
accept packets destinde for it; when the IP is 0.0.0.0, the interface
goes into promiscuous mode, and so it accepts all packets, whether
destined for it or not. Then, the bridge device enslaves all the
interfaces, and transports the packets among the participant interfaces.
> I guess this is an artifact of how it is implemented?
You could say that.
--
Derrik Pates
demon@devrandom.net
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
next prev parent reply other threads:[~2005-01-15 4:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-14 1:50 VIF setup Kero-Chan
2005-01-14 11:46 ` Mark Williamson
2005-01-14 14:05 ` Derrik Pates
2005-01-14 19:48 ` Adam Sulmicki
2005-01-15 3:40 ` Ronald G. Minnich
2005-01-15 4:17 ` Derrik Pates [this message]
2005-01-15 10:00 ` Jan Kundrát
2005-01-15 14:07 ` Felipe Alfaro Solana
2005-01-15 16:20 ` Jody Belka
2005-01-15 16:48 ` Martin Maney
2005-01-18 15:21 ` Mike Wray
-- strict thread matches above, loose matches on Subject: below --
2006-11-20 22:35 Jacob Gorm Hansen
2006-11-20 22:43 ` Ewan Mellor
2006-11-20 23:19 ` Jacob Gorm Hansen
2006-11-21 7:38 ` Keir Fraser
2006-11-21 9:42 ` Jacob Gorm Hansen
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=41E89965.4000709@devrandom.net \
--to=demon@devrandom.net \
--cc=adam@cfar.umd.edu \
--cc=kerochan2@gmail.com \
--cc=maw48@cl.cam.ac.uk \
--cc=rminnich@lanl.gov \
--cc=xen-devel@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.