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

duplicate hostnames/Ip addresses in ARP search screen #5631

Closed
breeman1 opened this Issue Jan 27, 2017 · 1 comment

Comments

Projects
None yet
2 participants
@breeman1

breeman1 commented Jan 27, 2017

DO NOT DELETE THIS INFORMATION.

Please read this information carefully.

GitHub issues is for feature requests or bugs, please do not post issues asking for help or how to do X, Y or Z.
You can use our irc channel ##librenms on freenode to ask questions or our community site.

Please confirm each of the sections below by putting an x in the box like [x].

  • [x ] Is your install up to date? Updating your install
    Please do not submit an issue if your install is not up to date within the last 24 hours or on a stable monthly release.
  • [x ] Please include all of the information between the ==================================== section of ./validate.php which you can run from the cli.
  • [ x] Unless your issue is for a WebUI fix or feature then please provide ALL info asked for here.
  • [ x] Please provide as much detail as possible.
  • Please do NOT post more than 10 lines of debug information here, use a pastebin service or GitHub Gists.

snap7
When I try to search for ARP entries in the ARP Search screen I get a lot of duplicate hostname/ip address names in the "All Devices" drop down menu.
I doubt this is the intended behavior, Please see below;
snap5

laf added a commit to laf/librenms that referenced this issue Jan 28, 2017

@laf laf closed this in #5641 Jan 28, 2017

laf added a commit that referenced this issue Jan 28, 2017

@lock

This comment has been minimized.

Show comment
Hide comment
@lock

lock bot May 18, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed.

lock bot commented May 18, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed.

@lock lock bot locked as resolved and limited conversation to collaborators May 18, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.