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

Whitelist/blacklist interface names #4

Open
XioNoX opened this issue Feb 8, 2019 · 2 comments
Open

Whitelist/blacklist interface names #4

XioNoX opened this issue Feb 8, 2019 · 2 comments
Labels
enhancement New feature or request

Comments

@XioNoX
Copy link

XioNoX commented Feb 8, 2019

Juniper devices have a lot of system interfaces that don't make sens for us to be imported.

It would be useful to be able to define both a whitelist and blacklist of interfaces names pattern we want to import.
For example in my scripts, I do pattern matching on the following:
interfaces_whitelist = ['et-', 'xe-', 'ge-', 'ae', 'fxp', 'gr-', 'lo0', 'vme', 'reth', 'st', 'me0', 'em0']
interfaces_blacklist = ['.32767', '.32768', '.16386', '.16385', '.16384', 'fxp2', 'bme']
Both white and black are needed to prevent some system sub-interfaces.

@aruhier
Copy link
Contributor

aruhier commented Feb 8, 2019

Hi,
Thanks a lot for the feedback. It could be interesting indeed. I could add some regex to whitelist/blacklist interfaces as you did.

@aruhier aruhier added the enhancement New feature or request label Feb 8, 2019
@XioNoX
Copy link
Author

XioNoX commented Feb 13, 2019

Piggybacking on that feature request.
Similarly it would be useful to ignore link-local fe80:: and similar IPs not configured by a user.

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

No branches or pull requests

2 participants