SSH tunnels for vnc and telnet #24
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
These changes will break telnet handler. The URLs, such as telnet://route-server.he.net, are used not only in EVE-NG. Also, the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Maybe one solution for issue #17 would be to create SSH tunnels. In this PR I redirected telnet and VNC into SSH tunnel. VNC tunnel is a bit buggy - sometimes it requires one to click twice on the same device in the topology, beacuse the VNC connects to device's VNC console before a SSH tunnel is created.
Documentation has been changed accordingly.
Tested on Arch Linux with Mozilla Firefox 58.0.1.