Re: vlans and cloning

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

causes a single request to clone a vlan together with the tag+parent
device parameters (i.e. and no subsequent SIOCSETVLAN request).

Given the above do we still need to support setting vlan tag+device
separately or can we just require everything be specified when doing the
clone operation? This would change the user api but otherwise I can see
no reason for continuing to support the old mechanism where you do:

ifconfig vlan create
ifconfig vlan0 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.

--
Andre

_______________________________________________
freebsd-arch@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: vlans and cloning
    ... I also modified the vlan code to use this ... ifconfig vlan create vlan 1 vlandev em0 ... Given the above do we still need to support setting vlan tag+device ...
    (freebsd-arch)
  • carp+pfsync+freevrrpd+jail
    ... Using carp and pfsync i have made the redundand firewall ... vlan 101 vlandev em0" ... And when host2 is ths slave and i'm starting to ping carp0 address - no traffic appears on master host - that means that the local carp interface responding to my packets.. ...
    (freebsd-stable)
  • Re: vlans and cloning
    ... I also modified the vlan code to use this ... ifconfig vlan create vlan 1 vlandev em0 ... Given the above do we still need to support setting vlan tag+device ...
    (freebsd-arch)