From: Stephen Hemminger <shemminger@vyatta.com>
To: Malcolm Scott <Malcolm.Scott@cl.cam.ac.uk>
Cc: Bridge@lists.linux-foundation.org,
Benoit PAPILLAULT <benoit.papillault@free.fr>
Subject: Re: [Bridge] frame destinated to individual port MAC address
Date: Fri, 15 Aug 2008 13:31:38 -0700 [thread overview]
Message-ID: <20080815133138.587c1005@extreme> (raw)
In-Reply-To: <alpine.DEB.1.10.0808152114540.27001@callisto.moose.malc.org.uk>
On Fri, 15 Aug 2008 21:17:27 +0100 (BST)
Malcolm Scott <Malcolm.Scott@cl.cam.ac.uk> wrote:
> At 22:06 today, Benoit PAPILLAULT wrote:
>
> > I am in a very preliminary phase, trying to learn how to implement
> > routing and bridging under Linux. In order for the routing protocol to
> > have proper topology view, it somehow needs to assign a unique IP on all
> > interfaces and for bridging and those interfaces needs to be in the same
> > bridge.
>
> By my understanding (and it's a while since I read that paper so I might be
> wrong) you don't need unique IP addresses on all interfaces; everything uses
> MAC addresses. To quote section 4.2 of the draft:
>
> o it runs directly over Layer 2, so therefore may be run with zero
> configuration (no IP addresses need to be assigned)
>
It looks an implementation or rbridge would do:
1. Set STP to "user mode" similar to user mode RSTP
2. Set IP address on bridge device (same as normal)
3. Run routing daemon with multiple sockets that use SO_BINDTODEVICE
to receive the packets by interface
4. Routing daemon would manage bridged interface state (blocking, forwarding, etc)
next prev parent reply other threads:[~2008-08-15 20:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-11 21:52 [Bridge] frame destinated to individual port MAC address Benoit PAPILLAULT
2008-08-11 23:31 ` Stephen Hemminger
2008-08-15 20:06 ` Benoit PAPILLAULT
2008-08-15 20:17 ` Malcolm Scott
2008-08-15 20:31 ` Stephen Hemminger [this message]
2008-08-15 21:12 ` Benoit PAPILLAULT
2008-08-15 21:03 ` Benoit PAPILLAULT
2008-08-15 22:03 ` Stephen Hemminger
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=20080815133138.587c1005@extreme \
--to=shemminger@vyatta.com \
--cc=Bridge@lists.linux-foundation.org \
--cc=Malcolm.Scott@cl.cam.ac.uk \
--cc=benoit.papillault@free.fr \
/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.