Patrick McHardy <[email protected]> writes: > I think there is one more case that matters, which is briding > from a device with VLAN stripping for a VLAN not configured > locally. The tag will be stripped and will be lost for forwarded > packets. I think we should drop such packets on RX. Anyway we shouldn't forward them. -- Krzysztof Halasa - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [PATCH 1/2] NET: Re-add VLAN tag for devices incapable of keeping it
- From: Patrick McHardy <[email protected]>
- Re: [PATCH 1/2] NET: Re-add VLAN tag for devices incapable of keeping it
- From: Ben Greear <[email protected]>
- Re: [PATCH 1/2] NET: Re-add VLAN tag for devices incapable of keeping it
- References:
- Re: expected behavior of PF_PACKET on NETIF_F_HW_VLAN_RX device?
- From: Rick Jones <[email protected]>
- [PATCH 1/2] NET: Re-add VLAN tag for devices incapable of keeping it
- From: "Dave Johnson" <[email protected]>
- Re: [PATCH 1/2] NET: Re-add VLAN tag for devices incapable of keeping it
- From: Patrick McHardy <[email protected]>
- Re: [PATCH 1/2] NET: Re-add VLAN tag for devices incapable of keeping it
- From: David Miller <[email protected]>
- Re: [PATCH 1/2] NET: Re-add VLAN tag for devices incapable of keeping it
- From: Patrick McHardy <[email protected]>
- Re: expected behavior of PF_PACKET on NETIF_F_HW_VLAN_RX device?
- Prev by Date: Re: [GIT PULL] x86 setup: correct booting on 486 (revised)
- Next by Date: Re: 2.6.24-rc1 - Regularly getting processes stuck in D state on startup
- Previous by thread: Re: [PATCH 1/2] NET: Re-add VLAN tag for devices incapable of keeping it
- Next by thread: Re: [PATCH 1/2] NET: Re-add VLAN tag for devices incapable of keeping it
- Index(es):
 |