Re: vlans and cloning

On Tue, Jul 11, 2006 at 08:27:14AM +1200, Andrew Thompson wrote:
On Mon, Jul 10, 2006 at 09:04:41AM -0700, Brooks Davis wrote:
On Mon, Jul 10, 2006 at 10:52:33AM +0200, Andre Oppermann wrote:
Sam Leffler wrote:
I committed the revised netif cloning api so you can now specify
parameters when cloning. I also modified the vlan code to use this
mechanism so doing something like:

ifconfig vlan create vlan 1 vlandev em0


/me wants to do:

"ifconfig em0.1 inet 192.168.2.2/24"

Even simpler. And yes, this works already but only if if_vlan.ko
was loaded before or compiled into the kernel. It doesn't do auto-
load.

Unless cause ifconfig to autoload all if_ modules when cloning fails,
it's impossiable to support this without having if_vlan loaded. That
said the current plan it to eliminate if_vlan and integrate vlan support
directly into if_ethersubr.c to allow use to correctly handle the
default vlan case among otherthings.

Is anyone working on this? The bridge code needs access to the vlan tag
to properly hash the address as each vlan is a seperate broadcast
domain, this would be much easier with vlan merged to if_ethersubr.c.

I think it ended up with Robert's name on it at the last devsummit, but
he's got a lot of higher priority stuff on his plate. It doesn't look
like this change would be all that much work. The one thing that might
be worth investigating is seeing if there's a sane way to make vlan tag
parsing part of ether_input, but keep if_vlan.c around as a module for
actual support of trunks so we get most of the architectural benefits of
correctly treating vlan tags as part of the spec, but let embedded
users who don't need trunks avoid the overhead.

-- Brooks

--
Any statement of the form "X is the one, true Y" is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4

Attachment: pgpvxGpJmoMKU.pgp
Description: PGP signature

Relevant Pages

  • Re: vlans and cloning
    ... ifconfig vlan0 vlan 1 vlandev em0 ... root@homelynx# ifconfig vlan32 vlan 32 vlandev rl0 ...
    (freebsd-arch)
  • Re: vlans and cloning
    ... ifconfig vlan0 vlan 1 vlandev em0 ... you can still specify the name of the cloned device. ...
    (freebsd-arch)
  • Re: problem with vlan interfaces in 6-STABLE
    ... >> I have a small problem with my vlan interfaces configured from rc.conf: ... The config did not change during the update: ... > to ifconfig in RELENG_6. ... those from the parent, ...
    (freebsd-stable)
  • Re: vlans and cloning
    ... ifconfig vlan0 vlan 1 vlandev em0 ... root@homelynx# ifconfig vlan32 vlan 32 vlandev rl0 ...
    (freebsd-arch)
  • Re: vlans and cloning
    ... I also modified the vlan code to use this ... ifconfig vlan create vlan 1 vlandev em0 ... Unless cause ifconfig to autoload all if_ modules when cloning fails, ...
    (freebsd-arch)