All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@vyatta.com>
To: Ambroz Bizjak <ambrop7@gmail.com>
Cc: netfilter@vger.kernel.org
Subject: Re: NCD, a light scripting language for network configs and much more
Date: Fri, 17 Aug 2012 12:07:02 -0700	[thread overview]
Message-ID: <20120817120702.62103ae4@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <CAOA3yKLQNQ-t4VGENKTH683eLXA3A8GwPJ1w7zwT=AUus_CkFw@mail.gmail.com>

On Fri, 17 Aug 2012 21:04:04 +0200
Ambroz Bizjak <ambrop7@gmail.com> wrote:

> Huh, really? I can't seem to find those commands. I only see a
> "bridge" program added to iproute2 which does "forwarding database
> management", and doesn't seem to have the usual addbr/addif commands.
> Anyway, if brctl did suddenly disappear, imagine how easier it would
> be to fix that script I showed you compared to fixing something
> hardcoded like NetworkManager :)
> 
> On Fri, Aug 17, 2012 at 6:22 PM, Stephen Hemminger
> <shemminger@vyatta.com> wrote:
> >
> > FYI - you can use ip commands now to control bridge.
> > For all the new features planned, they won't be controllable via brctl.

You can make a bridge with:
 # ip link add br3 type bridge

and delete with
 # ip link del br3

To add device to bridge
 # ip li set dev eth2 master br3

To take out of bridge
 # ip li set dev eth2 nomaster

The point is that bridge isn't special.

  reply	other threads:[~2012-08-17 19:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-17 10:03 NCD, a light scripting language for network configs and much more Ambroz Bizjak
2012-08-17 10:03 ` Ambroz Bizjak
2012-08-17 16:22 ` Stephen Hemminger
2012-08-17 16:22   ` Stephen Hemminger
2012-08-17 19:04   ` Ambroz Bizjak
2012-08-17 19:07     ` Stephen Hemminger [this message]
2012-08-17 19:16       ` Ambroz Bizjak

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=20120817120702.62103ae4@nehalam.linuxnetplumber.net \
    --to=shemminger@vyatta.com \
    --cc=ambrop7@gmail.com \
    --cc=netfilter@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.