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

ARP records aren't closed when router goes down #596

Closed
jmbredal opened this issue Jan 17, 2017 · 2 comments
Closed

ARP records aren't closed when router goes down #596

jmbredal opened this issue Jan 17, 2017 · 2 comments
Labels
Milestone

Comments

@jmbredal
Copy link
Collaborator

jmbredal commented Jan 17, 2017

As described by Matej Gregr on the nav-users list:

Hello,
I noticed, that NAV does not close arp entries after monitored node
become unavailable. For example: There is an active mac address
11:22:33:44:55:66 with end_time set to infinity. When the monitored node
goes down, the mac address remains in active state, so you can find it
using machinetracker as a still active address, which apparently is not
true.

I suggest, that there should be another rule in database, enssuring that
arp entries will be closed.

Something like:

CREATE OR REPLACE RULE netbox_status_close_arp AS ON UPDATE TO netbox
WHERE NEW.up='n'
DO UPDATE arp SET end_time=NOW()
WHERE netboxid=OLD.netboxid AND end_time='infinity';


Imported from Launchpad using lp2gh.

@jmbredal
Copy link
Collaborator Author

(by mbrekkevold)
fix here: http://metanav.uninett.no/hg/default/rev/6141946f75bb

@jmbredal jmbredal added this to the 3.9.0 milestone Jan 17, 2017
@jmbredal
Copy link
Collaborator Author

Translated changeset references:
http://metanav.uninett.no/hg/default/rev/6141946f75bb: 3e6f2df

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

No branches or pull requests

1 participant