lib: Introducing interface type to struct interface

[raja-rajasekar]

Adding new field (interface type like Vlan,SVI,VRR etc..) in the struct interface to inform all zebra clients like ospf/bgp.

This can help protocols take appropriate action based on a specific interface type.

Ticket #3668878

Signed-off-by:.Chirag Shah.[email protected] Signed-off-by: Rajasekar Raja [email protected]

[raja-rajasekar]

Where is this interface type is gonna be used? For now, it's just an abandoned new struct member?

There is a bug/requirement to make the MACVLAN interface (vlan##-v0) ospf passive if configured via ospf network statement. A cleaner solution is to let the clients/protocols know the interface type to take action as needed.

[eqvinox]

There is a bug/requirement to make the MACVLAN interface (vlan##-v0) ospf passive

This sounds like what is really needed is a better secondary indicator?

If a user has multiple MACVLAN devices and is not using the main device at all, they may well want to have OSPF enabled on some of the interfaces…

Also, what is preventing the user from either using interface based OSPF config, or putting ip ospf passive on the MACVLAN devices?

[github-actions[bot]]

This PR is stale because it has been open 180 days with no activity. Comment or remove the autoclose label in order to avoid having this PR closed.