[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTikSvs7jF9BZzbsYkLAawpCH2h1Z0r09ft219uaa@mail.gmail.com>
Date: Fri, 25 Feb 2011 17:08:01 -0800
From: Jesse Gross <jesse@...ira.com>
To: chriss <mail_to_chriss@....net>
Cc: netdev@...r.kernel.org
Subject: Re: 2.6.37 regression: adding main interface to a bridge breaks vlan
interface RX
On Fri, Feb 25, 2011 at 4:16 PM, chriss <mail_to_chriss@....net> wrote:
> Jesse Gross <jesse <at> nicira.com> writes:
>
>>
>> What driver is in use with the NIC you are seeing this on?
>>
>
> He there
>
> the device in question is (as lspci told)
> Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8110SC/8169SC Gigabit
> Ethernet (rev 10)
>
> handled by kernel module r8169.
I'm guessing that you're hitting the special case in this code in
r8169.c:rtl8169_vlan_rx_register():
/*
* Do not disable RxVlan on 8110SCd.
*/
if (tp->vlgrp || (tp->mac_version == RTL_GIGA_MAC_VER_05))
tp->cp_cmd |= RxVlan;
else
tp->cp_cmd &= ~RxVlan;
Since before you were getting the vlans directly off the device there
was a vlan group configured. However, now that the packets are going
through the bridge, the group is not being configured on the device
and the tag gets dropped. Assuming that this is the case, the
solution is to convert the driver to use the new vlan model, which
does not require knowledge of the vlan group.
Can you confirm this by running tcpdump -eni br0? I would expect that
you see the correct packets but without vlan tags.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists