From: Bert Vermeulen <bert@biot•com>
To: netdev@vger•kernel.org, Stephen Hemminger <stephen@networkplumber•org>
Subject: bridge/brctl/ip
Date: Sat, 2 Apr 2016 21:26:55 +0200 [thread overview]
Message-ID: <57001CFF.20508@biot.com> (raw)
Hi all,
I'm wondering about the current userspace toolset to control bridging in
the Linux kernel. As far as I can determine, functionality is a bit
scattered right now between the iproute2 (ip, bridge) and bridge-utils
(brctl) tools:
- creating/deleting bridges: ip or brctl
- adding/deleting ports to/from bridge: brctl only
- showing bridge fdb: brctl (in-kernel fdb), bridge (hardware offloaded
fdb) (!)
...and no doubt a few other things.
Also the brctl tool seems not to be getting updates, whereas the
iproute2 tools are of course updated regularly. Is brctl considered
obsolete?
If that is the case, would patches to add the missing functionality into
the bridge tool be welcome? I'm thinking primarily of creating/deleting
bridges, and adding/deleting ports in bridges.
--
Bert Vermeulen
bert@biot•com
next reply other threads:[~2016-04-02 19:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-02 19:26 Bert Vermeulen [this message]
2016-04-02 22:39 ` bridge/brctl/ip Andrew Lunn
2016-04-02 22:50 ` bridge/brctl/ip Nikolay Aleksandrov
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=57001CFF.20508@biot.com \
--to=bert@biot$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=stephen@networkplumber$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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