From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Default Date: Fri, 05 Oct 2007 10:05:35 +0000 Subject: Re: [LARTC] Layer 3 switching... Message-Id: <47060C6F.1040704@advaita.sytes.net> List-Id: References: <4705538C.7070403@riverviewtech.net> In-Reply-To: <4705538C.7070403@riverviewtech.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: lartc@vger.kernel.org Hi I was told that layer 3 switches are faster because "routing" there is done by some ASIC hardware. Is there any advantage in having another routing code in bridging when everything is done in software which is same slow as normal routing? The only speed gain would be in keeping the routing code very simple with limited functionality, but i think that the trend is to put there more and more functionality which would end up in having two same slow, same function code in two places. (i was taugth that packets are routed on L3, frames are switched(bridged) on L2. And L3 switch does L2 switching + L3 routing but in hardware. routers are completely a software thing, switches hardware thing, and bridge is switch in software.) Please excuse me if i am missing your idea completely. Grant Taylor wrote: > Is it even possible or even worth while to do layer 3 switching > (bridging) on a Linux system? > > Or would this be considered routing even though everything is done on > OSI Layer 2? > > Which would be faster, Layer 3 switching (bridging) on OSI Layer 2 or > routing on OSI Layer 3? > > > > Grant. . . . > _______________________________________________ > LARTC mailing list > LARTC@mailman.ds9a.nl > http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc -- ___________________________________ S pozdravom / Best regards John Default _______________________________________________ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc