From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Fri, 15 Aug 2008 13:31:38 -0700 From: Stephen Hemminger Message-ID: <20080815133138.587c1005@extreme> In-Reply-To: References: <48A0B4AD.6030703@free.fr> <20080811163159.49cf9980@extreme> <48A5E1E3.5060907@free.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [Bridge] frame destinated to individual port MAC address List-Id: Linux Ethernet Bridging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Malcolm Scott Cc: Bridge@lists.linux-foundation.org, Benoit PAPILLAULT On Fri, 15 Aug 2008 21:17:27 +0100 (BST) Malcolm Scott 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)