*** From dhcp-server -- To unsubscribe, see the end of this message. ***
According to Jeroen Massar:
>
> > How are you defining the term "switch?" To me, a bridge is a dual-port
> > switch, and a switch is a multi-port bridge :) The Linux bridge behavior
> > described is just plain broken.
> Switch = multiple seperate segments getting only seeing packets for that segment...
> Bridge = multiple seperate segments seeing ALL packets..
I've never heard of an ethernet bridge that did not learn the MAC
addresses of each segment to avoid unnecessary forwarding. I think
the term 'switch' was just an advertising ploy to better distinguish
them from repeaters/hubs.
> The linux bridge currently switches "outside" segments, it checks to see
> where a MAC address is and sends it to the correct segment.
> But whenever a packet originates FROM the host doing the switching itself,
> it simply uses the protocol's routing (or the programs mechanism), eg
> IProuting, for IP to determine where it needs to go...
That can't possibly work in the situation where the route doesn't
determine which interface to use (and if it did there would not
be much reason to bridge unless it is for other protocols). Does
the bridge present its own interface that can be used as the
target of routes covering the connected range?
Les Mikesell
[EMAIL PROTECTED]
------------------------------------------------------------------------------
To unsubscribe from this list, please visit http://www.fugue.com/dhcp/lists
If you are without web access, or if you are having trouble with the web page,
please send mail to [EMAIL PROTECTED] Please try to use the web
page first - it will take a long time for your request to be processed by hand.
Archives for this mailing list are available at
http://www.webnology.com/list-archives/dhcp/dhcp-server
------------------------------------------------------------------------------
