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

fix: cdp matching incorrect ports #7491

Merged
merged 1 commit into from Oct 15, 2017

Conversation

Projects
None yet
3 participants
@murrant
Member

murrant commented Oct 15, 2017

Need either remote device_id or mac_address to find a port, otherwise, we might match an incorrect port.

DO NOT DELETE THIS TEXT

Please note

Please read this information carefully. You can run ./scripts/pre-commit.php to check your code before submitting.

Testers

If you would like to test this pull request then please run: ./scripts/github-apply <pr_id>, i.e ./scripts/github-apply 5926

fix: cdp matching incorrect ports
Need either remote device_id or mac_address to find a port, otherwise, we might match an incorrect port.

@murrant murrant added the Bug 🐞 label Oct 15, 2017

@scrutinizer-notifier

This comment has been minimized.

Show comment
Hide comment
@scrutinizer-notifier

scrutinizer-notifier Oct 15, 2017

The inspection completed: 1 new issues, 1 updated code elements

scrutinizer-notifier commented Oct 15, 2017

The inspection completed: 1 new issues, 1 updated code elements

@laf laf merged commit 2f2234d into librenms:master Oct 15, 2017

2 checks passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
license/cla Contributor License Agreement is signed.
Details

@murrant murrant deleted the murrant:fix-find_port branch Oct 16, 2017

@lock

This comment has been minimized.

Show comment
Hide comment
@lock

lock bot May 17, 2018

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

lock bot commented May 17, 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 17, 2018

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