VLAN number cannot be forced by router port description

[Morten Brekkevold]

According to our own documentation, https://nav.uninett.no/wiki/subnetsandvlans#guide_lines_for_configuring_router_interface_descriptions , it should be possible to use the NTNU router port description conventions to let NAV know which VLAN tag is associated with a routed prefix.

This would be useful for pure L3 devices that don't speak 802.1Q, where NAV cannot autodiscover the prefix/VLAN mapping.

I believe this used to work under getDeviceData, but it appears that the corresponding code in ipdevpoll parses the VLAN number from the description, and then goes on to ignore it.

As referenced by this post in the nav-users mailing list: https://postlister.uninett.no/sympa/arc/nav-users/2015-03/msg00007.html

Using the convention correctly should force the specified VLAN to be associated with the prefix.

[Morten Brekkevold (mbrekkevold)]

fix here: https://nav.uninett.no/hg/stable/rev/a97f53df2156