All of lore.kernel.org
 help / color / mirror / Atom feed
From: "S Mohan" <smohan@vsnl.com>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] Bridging
Date: Tue, 25 Feb 2003 02:41:08 +0000	[thread overview]
Message-ID: <marc-lartc-104614018513133@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104611165608075@msgid-missing>

I'm using bridging on LEAF - a mini distro and it works well. The
numbering scheme however seems to suggest not so mature a code. I'm on
that list too and work is going on a iptables replacement when bridging
is being used - called ebtables. Reason being that while bridging,
iptables can be used only on the forward table/chain.

Mohan
-----Original Message-----
From: lartc-admin@mailman.ds9a.nl [mailto:lartc-admin@mailman.ds9a.nl]
On Behalf Of Jay Wineinger
Sent: Monday, February 24, 2003 11:58 PM
To: lartc@mailman.ds9a.nl
Subject: [LARTC] Bridging


Not really contributing to the discussion on MAC forwarding, but Im
wondering about the maturity of linux bridging.  I looked at the
sourceforge page Martin posted and it seems that the last updates were
made duing 2002, nothing in 2003 yet.  Does this mean that bridging is
fairly stable and complete or that development is just going slow?  Just
curious.

Jay

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      parent reply	other threads:[~2003-02-25  2:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-24 18:27 [LARTC] Bridging Jay Wineinger
2003-02-24 19:01 ` Kirby C. Bohling
2003-02-24 19:55 ` Victor Cassar
2003-02-25  2:41 ` S Mohan [this message]

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=marc-lartc-104614018513133@msgid-missing \
    --to=smohan@vsnl.com \
    --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 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.