Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Juniper VLAN interfaces are not properly associated with their VLANs #2357

Closed
lunkwill42 opened this issue Mar 11, 2022 · 0 comments · Fixed by #2360
Closed

Juniper VLAN interfaces are not properly associated with their VLANs #2357

lunkwill42 opened this issue Mar 11, 2022 · 0 comments · Fixed by #2360
Assignees
Milestone

Comments

@lunkwill42
Copy link
Member

lunkwill42 commented Mar 11, 2022

Where there aren't MIBs to associate VLAN interfaces with actual VLAN IDs, NAV parses the interface name to "guess" the correct VLAN.

Only a few patterns are supported, typically something like VLAN(\d+)

For Juniper, NAV supports interfaces named irb for regular routers, but Juniper's firewall devices sport something called reth interfaces, whose name patterns are different, but can still be used to extract a VLAN number:

A fw device may have multiple reth interfaces, e.g. reth0, reth1 etc. The sub-interfaces with VLAN numbers in their name would be named reth0.100 for vlan 100, or reth1.100 for vlan 100 on on the reth1 interfaces. Upstream team says that the matching pattern is more like reth(\d+)\.(\d+), where the latter subpattern is the VLAN tag.

NAV patterns should be updated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants