You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 ?
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
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:
The text was updated successfully, but these errors were encountered: