From: John Fastabend <john.r.fastabend@intel.com>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: netdev@vger.kernel.org
Subject: Re: [ANNOUNCE] iproute2 3.4.0
Date: Mon, 21 May 2012 15:02:30 -0700 [thread overview]
Message-ID: <4FBABB76.7080406@intel.com> (raw)
In-Reply-To: <20120521150106.6ac4ca0d@nehalam.linuxnetplumber.net>
On 5/21/2012 3:01 PM, Stephen Hemminger wrote:
> On Mon, 21 May 2012 14:48:26 -0700
> John Fastabend <john.r.fastabend@intel.com> wrote:
>
>> On 5/21/2012 2:37 PM, Stephen Hemminger wrote:
>>> To go with kernel release of 3.4 here is the update to
>>> iproute2. There wasn't a lot new features in this release, mostly
>>> manual pages and cleanups.
>>>
>>> Source:
>>> http://www.kernel.org/pub/linux/utils/net/iproute2/iproute2-3.4.0.tar.gz
>>>
>>> Repository:
>>> git://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git
>>>
>>> Changes:
>>>
>>
>> Hi Stephen,
>>
>> Any plans to push the new 'bridge' tool into the next release? We
>> have been using it internally and it works great. I also wanted
>> to add some code to it for managing the forwarding tables of the
>> embedded switching elements and have been experimenting with some
>> code to enable VEB/VEPA modes.
>>
>> If you want me to help with testing or otherwise let me know.
>>
>
> It is on my TODO list, but haven't got to it yet. Will put in for 3.5.
> The name will be 'bridge' not 'br' to avoid conflict wit X10
Sounds good thanks. Figured it was on your TODO list somewhere
thought I would check though.
prev parent reply other threads:[~2012-05-21 22:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 21:37 [ANNOUNCE] iproute2 3.4.0 Stephen Hemminger
2012-05-21 21:48 ` John Fastabend
2012-05-21 22:01 ` Stephen Hemminger
2012-05-21 22:02 ` John Fastabend [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=4FBABB76.7080406@intel.com \
--to=john.r.fastabend@intel.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
/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;
as well as URLs for NNTP newsgroup(s).