Enhancement - Logical interface & vrf creation via Zebra

[jhiggins-NZ]

Foreword:

• I know its unlikely to happen, but just to add to https://github.com/FRRouting/frr/wiki/Feature-Requests in case it ever does.
  .
  .
  Enhancement:
• As a user I would like to create VRFs, Tunnels, Loopbacks, Sub-interfaces, VLAN interfaces / BVIs & VLANs / Bridges etc, from the CLI.
• This would then be reliably signalled to Linux kernel via netlink.
• Upon configuration being saved, it would also make sense for it to be saved in /etc/network/interfaces file too.
  .
  .
  Long term it would also be great if zebra had more control, thus giving engineers and provisioning systems less places to apply configuration.

Thanks.

[k0ste]

As a user I would like to create VRFs, Tunnels, Loopbacks, Sub-interfaces, VLAN interfaces / BVIs & VLANs / Bridges etc, from the CLI.

I think about it more than 5 years :)
ppp, 802.3ad is also will be in demand.

Upon configuration being saved, it would also make sense for it to be saved in /etc/network/interfaces file too.

I against this. Because not all live in debian world. For example netctl or network-scripts is profile-based network manager.
I think frr should manage all type of ip links and save his configuration in zebra.conf. And should work without external support, e.g. frr should be as network-manager.

[donaldsharp]

If someone wants to implement this that would be fine.

[donaldsharp]

Additionally this would be a fairly major project that would need work across all platforms. Feature request added to the wiki