From: Jesse Gross <jesse@nicira.com>
To: Seblu <seblu@seblu.net>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: bnx2 vlan issue
Date: Thu, 24 Mar 2011 12:55:08 -0700 [thread overview]
Message-ID: <AANLkTi=zfhwHTB7kitgwk3AzSa0aFFyxgM_ZY-3wObR5@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimnKRDY8QLiJMMLqNzCA_-6UJmUDHKf-i1Yt3V5@mail.gmail.com>
On Thu, Mar 24, 2011 at 5:58 AM, Seblu <seblu@seblu.net> wrote:
>> I don't necessarily disagree that there should be a better way to do
>> this, though as of the moment the above is probably your best bet.
>>
>> To me, the most important thing is to have consistent behavior across
>> different cards.
>
> Speaking of that, i've tryed 2.6.38 on my station (dell opitplex 980)
> to use the new bridging schema and it doesn't work.
> Exactly the case previously described: ip on br0 (eth0+eth1) and ip on
> br0.42. eth0 driver is e1000e and eth1 is tg3. br0.42 don't receive
> traffic.
> I have to open a bug report?
The change was deliberate, not an accidental mistake, so don't expect
2.6.38 to suddenly switch back to the previous behavior. There's no
need to file a bug report - the new behavior is known (I was the one
who changed it in the first place). I will look into nicer semantics
in the future.
next prev parent reply other threads:[~2011-03-24 19:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 14:51 bnx2 vlan issue Seblu
2011-03-17 18:02 ` Seblu
2011-03-17 19:16 ` Jesse Gross
2011-03-17 23:22 ` Seblu
2011-03-22 2:05 ` Jesse Gross
2011-03-22 10:59 ` Seblu
2011-03-22 23:19 ` Jesse Gross
2011-03-24 12:58 ` Seblu
2011-03-24 19:55 ` Jesse Gross [this message]
2011-03-25 0:26 ` Seblu
2011-04-02 2:01 ` Jesse Gross
2011-06-17 6:10 ` Dominique Martinet
2011-06-17 16:47 ` Jesse Gross
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='AANLkTi=zfhwHTB7kitgwk3AzSa0aFFyxgM_ZY-3wObR5@mail.gmail.com' \
--to=jesse@nicira.com \
--cc=netdev@vger.kernel.org \
--cc=seblu@seblu.net \
/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).