On Tue, 24 Mar 2015 07:53:41 +0200 Mattias Söderholm mattias.soderholm@malax.fi wrote:
The Sophos UTM9 supports VLAN tagging, but we are not using it. We need to create new VLAN interfaces and reconfigure the whole UTM9 to get that active. Right now we only use separate network interfaces for different LAN segments.
Ok.
We are seeing a similar problem here, as well, though on routers that do support 802.1Q: We are deploying more and more Juniper routers, and we support no proprietary MIBs on this platform so far.
At leaast, these routers use a seemingly reliable pattern of interface naming that contains the VLAN tag, but it doesn't match the current VLAN pattern used by NAV (I think the Juniper's use "irb.<vlantag>"). We will likely be adding support for that pattern as well.
About the bug reporting for the VLAN number of a prefix through the interface description conventions you can create one. See that I need to have some Ubuntu account for the bug reporting...
Yes, I think Ubuntu merged Launchpad accounts with Ubuntu accounts at some point.
Anyway, I did post the bug here: https://bugs.launchpad.net/nav/+bug/1436388
Hoping to work on it tomorrow.
Today the whole VLAN entry being deleted and then recreated with a new ID.
I think it may be because NAV cannot trace a tagless VLAN entry on your L2 network, so it likely appears disused. Not entirely sure though - I would like to fix the above bug and have you test it before we dive into that.