[Xorp-users] VLAN Interfaces

[Ben Greear]

On 02/14/2011 12:52 PM, Joe Coco wrote:
>
>> Thanks for the useful test case.
>
>> I found some of the problems:
>
>> First, I fixed the vlan naming to use "eth1.5" format.
>
> Was that simply a change from:
>
> -    vlanreq.u.name_type = VLAN_NAME_TYPE_PLUS_VID_NO_PAD;      // vlan10
> +    vlanreq.u.name_type = VLAN_NAME_TYPE_RAW_PLUS_VID_NO_PAD; /* eth1.100 */
>
> in  fea/data_plane/ifconfig/ifconfig_set_netlink_socket.cc  ?

After some more looking, I think using VLANs as VIFS like this is not
worth the effort.  We'd have to do some hard-core hacking on
the vif class...basically re-implement all or most of the Interface
logic.

And even that doesn't really scale..because you can have vlans on vlans, macvlans,
bridge devices and various other stacking.

So, I think I'd propose that virtual interfaces be created outside of xorp.
Please note that xorp.ct *should* work fine if you start it before the
VLANs are created, and then create them sometime later.  It should also
deal with dynamically adding/deleting interface config from within
xorpsh, independently of the coming and going of interfaces in the
OS.  (I put a lot of effort into this for our WISER product, but
problems could remain..so yell if you find bugs of this nature.)

If someone has a use case that would be difficult in this scenario,
please post to the list...

Thanks,
Ben

-- 
Ben Greear <greearb at candelatech.com>
Candela Technologies Inc  http://www.candelatech.com