[quagga-dev 10491] Re: Adding "encapsulation dot1q" option to interfaces

Greg Troxel gdt at ir.bbn.com
Wed May 1 12:51:06 BST 2013

Adrian Ban <bluelightning at mantech.ro> writes:

> For the part of netlink/rtnetlink I can handle it (already found what
> I need and also the parameters I need to set in the netlink message,
> inspired from iproute, to be send to the kernel).
> But before I send the message to the kernel I need to make some sanity
> checks before the "encapsulation dot1q <1-4094>" command to be send.
> So this is what I want to do:
> 1. check the interface name to be in a format like this: eth0.243
> 2. extract the real interface from the interface name: eth0
> 3. check if the dot1q parameter is in the range 1-4094 (already done it)
> 4. check if the specific dot1q vlan id is already token by another
> subinterface of the same interface
> 5. send the message to the kernel to create the subinterface with the
> name and the specific vlan id
> 6. zebra should check automatically that a new interface is up and it
> should install all needed stuff (hope this is the flow from what I
> could get form the quagga sources).

If this is part of quagga it should support all the operating systems
and kernel communication methods.  Have you looked at the BSD routing
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
URL: <http://lists.quagga.net/pipermail/quagga-dev/attachments/20130501/19c87a96/attachment-0001.sig>

More information about the Quagga-dev mailing list