-
Notifications
You must be signed in to change notification settings - Fork 30
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
ssh support #30
Comments
I just added the ssh support. It is in first stages and needs little finishing touches and then I'll request merge to this official library. For time being, you can pull mine on you own risk. pbk@pbk-mbp15 [~]netconify --facts -s "146.180.226.36,4011,," -u test-user --passwd "pasword1" I omitted ssh console user and pass, since they're same for device authentication, but if they are different, you can specify them. pbk@pbk-mbp15 [~]netconify --facts -s "146.180.226.36,4011,console-user,console-password" -u test-user --passwd "pasword1" |
r2600,, I get the following: `MAC:~$netconify --facts --ssh=10.0.0.8,3020,terminalUsername,terminalPassword -u username --passwd "junosPassword?" Traceback (most recent call last): ` |
I noted some problems with tty_ssh.py in issue #50. Trying cloning my fork. sudo pip install git+https://github.com/jeffbrl/py-junos-netconify.git@issue-50-fix |
jeffbri i tried cloning your fork unfortunately it didnt work |
Not sure what error you encountered. Try cloning my fork with 'git clone' and then switching to the issue-50-fix branch. Run 'python setup.py install'. |
Jeff, |
Would be great if netconify could initiate connections to a console server via ssh rather than just telnet. Our entire console server infrastructure relies on ssh to reach console ports rather than telnet.
Thanks for your consideration.
The text was updated successfully, but these errors were encountered: