netdev - Re: [Bridge] VLANs and bridge

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <OF89F33C42.59FE9B41-ONC125761E.002582F4-C125761E.0026292A@transmode.se>
Date:	Wed, 26 Aug 2009 08:56:49 +0200
From:	Joakim Tjernlund <joakim.tjernlund@...nsmode.se>
To:	Patrick McHardy <kaber@...sh.net>
Cc:	bridge@...ts.linux-foundation.org, netdev@...r.kernel.org,
	Simon Barber <simon@...erduper.net>
Subject: Re: [Bridge] VLANs and bridge

Patrick McHardy <kaber@...sh.net> wrote on 25/08/2009 16:00:44:
>
> Joakim Tjernlund wrote:
> > Simon Barber <simon@...erduper.net> wrote on 22/08/2009 19:12:10:
> >> Looking through B.1.3 it looks like the patch would need some
> >> enhancement. It provides a good basis - handling tagging/untagging and
> >> filtering, but would need a way to specify the untagged vlan separately
> >> for in and out.
> >
> > I see. Perhaps the VLAN maintainer(CC:ed) can comment too. Especially about extending
> > the VLAN code to allowed several VLANs in one interface?
>
> Just accepting additional VIDs on one VLAN device should be
> a relatively trivial change, all you need to do is call
> vlan_group_set_device() with the additional VIDs.
>
> I'd suggest to add something similar to the QoS-mapping lists
> in vlan_netlink.c for the additional VIDs.

Yes, this seems to be the easy part. There are a few bride issues though:
How would the bridge be able to filter pks based on VID?
How to control which VID to use at pkg TX?
Can you have the same VID on multiple VLAN interfaces?

     Jocke

--
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