From: Stephen Hemminger <shemminger@osdl.org>
To: linux-kernel@vger.kernel.org
Cc: linux-net@vger.kernel.org, bridge@osdl.org
Subject: [announce] bridge-utilities 1.0
Date: Wed, 26 May 2004 10:51:47 -0700 [thread overview]
Message-ID: <20040526105147.650ddfa9@dell_ss3.pdx.osdl.net> (raw)
I've released a new version of the bridge-utilities to go with the recent
kernel changes. The utilities have certainly matured enough to earn the
1.0 moniker. This release is fixes the internal issues that broke running
32 bit utilities on 64bit systems, and fixes scaling issues.
The tarball can be downloaded from:
http://prdownloads.sourceforge.net/bridge
Changes:
- Uses sysfs for bridge and port parameter changes.
- Uses new ioctl's for add/delete bridges and interfaces
that are 32/64bit compatible.
- Allows 1000's of interfaces in a bridge.
- Performance improvement with lots of bridges/interfaces
- Better error handling
- More complete configuration and build
Getting full functionality requires a build system with:
- libsysfs from the sysfsutils package
http://linux-diag.sourceforge.net/Sysfsutils.html
- kernel (and headers) from 2.6.7-rc1 or later
Note: libsysfs has not been fully integrated by the main linux vendors.
So producing a full functional package is not possible with the default spec
file.
The utilities will build (and run) on earlier systems it will just default to
the old interface and which doesn't have 32/64 bit compatibility.
The API in libbridge changed, because it didn't scale to lots of interfaces.
Previously, the library would read the status of all bridges and interfaces
when initialized. The new interface takes names (not objects) and looks more
like syscalls. Since libbridge is shipped as a static library, it will not
break binary utilities, but anything compiled from source would break.
Not a big issue because there is no existing standard package using the
bridge API anyway.
Ethernet bridging mailing list is bridge@osdl.org, to sign up
please use http://lists.osdl.org/mailman/listinfo/bridge
reply other threads:[~2004-05-26 17:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040526105147.650ddfa9@dell_ss3.pdx.osdl.net \
--to=shemminger@osdl.org \
--cc=bridge@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@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
all inboxes | Powered by JetHome®