vlans and cloning

[Sam Leffler]

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

That can still be done and is just different syntax to ifconfig.

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