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

Difference between Telnet / HTTP Console Command in IPv6 #3448

Closed
wangziyao318 opened this issue Feb 28, 2023 · 3 comments
Closed

Difference between Telnet / HTTP Console Command in IPv6 #3448

wangziyao318 opened this issue Feb 28, 2023 · 3 comments
Milestone

Comments

@wangziyao318
Copy link

wangziyao318 commented Feb 28, 2023

I use GNS3 client to connect to my remote GNS3 server with only public IPv6 address [2000:1234:5678:abcd::1]. I have some devices with telnet console and other devices with http console in one project.

If I input [2000:1234:5678:abcd::1] into Host, I can connect to the remote server, http console work, but telnet console NOT work
If I input 2000:1234:5678:abcd::1 into Host, I can connect to the remote server, telnet console work, but http console NOT work

The reason is that telnet IPv6 address should not be closed in square brackets, but http IPv6 address should be closed in square brackets.

telnet 2000:1234:5678:abcd::1 5000
curl http://[2000:1234:5678:abcd::1]:5050

So, I suggest GNS3 client to be able to distinguish them in console commands, because not everyone has a domain name to use. Thanks.

@grossmj grossmj added this to the 2.2.39 milestone Mar 21, 2023
@grossmj
Copy link
Member

grossmj commented May 14, 2023

Are you talking about console host in a "cloud" node?

Screenshot from 2023-05-14 20-15-01

@wangziyao318
Copy link
Author

I'm talking about the HTTP console of Docker nodes. They work quite well for GNS3 server in IPv4, but for gns3 server in IPv6, extra brackets [] are missing for the HTTP console.

Screenshot 2023-05-15 at 11 13 38 Screenshot 2023-05-15 at 11 16 01

@grossmj
Copy link
Member

grossmj commented May 22, 2023

This is fixed now. Please try in v2.2.40. Thanks again for catching that 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants