From: "Kirby C. Bohling" <kbohling@birddog.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Bridging
Date: Mon, 24 Feb 2003 19:01:13 +0000 [thread overview]
Message-ID: <marc-lartc-104611336010997@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104611165608075@msgid-missing>
Jay,
I can't comment directly on it, but I've used the bridging setup in
a RedHat 7.3 machine recently. The last Twisted Pair to BNC tranceiver
we had broke, so I had to build one out of a Linux machine. Worked
great on a little network (don't ask why I had to keep the BNC around,
I'm still pissed about it).
Never had any problems with the bridge. It's was not on a network that
had managed switches, so it didn't have to do interact with any of that
to ensure no network loops, but for a simple bridge it works great.
Turned the machine on, let it run for 15 days no problems on the
network, found a replacement tranceiver and life was good.
I know I used the ancient bridging code in the 1.2 kernel and never
had any problems with it (it's been re-written since then I believe).
The new code is great, took 5 minutes to figure it out from the man
page. The only thing that thru me was you have to ifconfig up the
bridging interface.
Thanks,
Kirby
On Mon, 2003-02-24 at 12:27, Jay Wineinger wrote:
> 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/
>
--
Real Programmers view electronic multimedia files with a hex editor.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-02-24 19:01 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 [this message]
2003-02-24 19:55 ` Victor Cassar
2003-02-25 2:41 ` S Mohan
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-104611336010997@msgid-missing \
--to=kbohling@birddog.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.