-
Notifications
You must be signed in to change notification settings - Fork 344
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
Utilizing ncclient bind_addr parameter #1279
Comments
Hi @elinewman12 Thanks |
@chidanandpujar I implemented the change on a fork but it uses version 2.3.0. So far, testing has proven successful with the use of bind_addr |
HI @elinewman12 Thanks |
@elinewman12 Could you please provide more information on use case of the "bind_addr" argument in the |
I concur with the OP, it would be useful to be able to pass the "bind_addr" parameter when instantiating the Device object. I've personally ended up creating fork of junos-eznc device.py (version 2.7.0) so that it accepts the bind_addr parameter and then passes it to the ncclient's "connect" function.
|
Fixed #1340 |
Why does the current version of Junos not use the bind_addr optional parameter for providing a source address to bind when connecting Device objects? It would be an easy fix and at least my current team would heavily benefit from this addition. I had to create a fork from our currently used version of Junos (5 years old) but we couldn't upgrade to the latest version either way due to the lack of this feature.
The text was updated successfully, but these errors were encountered: