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

Netmap lists interface under wrong netbox #1523

Closed
sigmunau opened this issue Jun 2, 2017 · 1 comment
Closed

Netmap lists interface under wrong netbox #1523

sigmunau opened this issue Jun 2, 2017 · 1 comment
Milestone

Comments

@sigmunau
Copy link
Contributor

sigmunau commented Jun 2, 2017

When nav topolog has linked a network interface to a netbox, but not a specific interface on that netbox and this link is selected in netmap the interface name is listed under the wrong netbox.

image

In the attached screenshot xe-1/0/47 and xe-0/0/47 are interfaces on uninett-tor-sw3.uninett.no and ae3 is at uninett-gsw1.uninett.no

@sigmunau sigmunau added the netmap label Jun 2, 2017
@lunkwill42
Copy link
Member

lunkwill42 commented Oct 20, 2017

Not surprised here. I've started some code review of Netmap due to randomly failing tests under Python 3, and it turns out a lot of the Netmap code assumes direction in an undirected graph when attaching metadata to graph edges - which makes it all the more likely that information will leak between nodes in the topology graph.

@lunkwill42 lunkwill42 added the bug label Oct 20, 2017
lunkwill42 added a commit that referenced this issue Oct 20, 2017
conclusion: Netmap is b0rked, #1523 explains the symptom, but a larger
code review is needed.
@lunkwill42 lunkwill42 added this to the 4.8.0 milestone Nov 20, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants