Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Grant Taylor <gtaylor@riverviewtech.net>
To: lartc@vger.kernel.org
Subject: [LARTC] Layer 3 switching...
Date: Thu, 04 Oct 2007 20:56:44 +0000	[thread overview]
Message-ID: <4705538C.7070403@riverviewtech.net> (raw)

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

             reply	other threads:[~2007-10-04 20:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-04 20:56 Grant Taylor [this message]
2007-10-05 10:05 ` [LARTC] Layer 3 switching John Default
2007-10-05 14:48 ` Grant Taylor
2007-10-06 11:16 ` John Default
2007-10-06 12:39 ` Mohan Sundaram
2007-10-08 14:48 ` Grant Taylor
2007-10-08 15:00 ` Grant Taylor

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=4705538C.7070403@riverviewtech.net \
    --to=gtaylor@riverviewtech.net \
    --cc=lartc@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox