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

Hardcoded console URIs (gns3+telnet) #21

Open
akrpic77 opened this issue Jul 27, 2021 · 1 comment
Open

Hardcoded console URIs (gns3+telnet) #21

akrpic77 opened this issue Jul 27, 2021 · 1 comment
Labels
enhancement New feature or request
Milestone

Comments

@akrpic77
Copy link

When gns3 server is deployed in "cloud" and accessible only via HTTP(S), hard-coded console URLs don't make sense, as nothing is listening at the node.console port, ... there should be option to go over websocket to access the console. maybe gns3+telnet+ws ?

In log-console.component.ts:

 `gns3+telnet://${node.console_host}:${node.console}?name=${node.name}&project_id=${node.project_id}&node_id=${node.node_id}`
@akrpic77
Copy link
Author

by modifying gns3-gui (add %N for node uuid, and %w for ws://), I managed to access console from gns3-gui over websockets using this as a Custom Console:
xterm -T "%d" -e "bash -c '(websocat --exit-on-eof --binary tcp-listen:127.1.0.1:%p %w/v2/projects/%i/nodes/%N/console/ws &) && telnet 127.1.0.1 %p'"

this could also be done with gns3-webclient-pack, relaying console access over websockets

@grossmj grossmj transferred this issue from GNS3/gns3-web-ui Sep 4, 2021
@grossmj grossmj added the enhancement New feature or request label Sep 14, 2021
@grossmj grossmj modified the milestones: 2.2.38, 3.0, 3.1 Jan 30, 2023
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