Issue 447 in connectbot: Allow IPv6 address literals
conne...@googlecode.com
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 447 by LukeDuns...@gmail.com: Allow IPv6 address literals
http://code.google.com/p/connectbot/issues/detail?id=447
What steps will reproduce the problem?
1. Start ConnectBot
2. Select Telnet mode
3. Enter the following address: [fe80::21b:77ff:fe2c:b690]:22
Q: What is the expected output?
A: I expect it to add the host to the list, and at least attempt to connect.
Q: What do you see instead?
A: Instead, it rejects the address as invalid.
Q: What version of the product are you using?
A: Version 1.7.1
Q: What type of system are you trying to connect to?
A: In the above example it is a Linux PC but this is irrelevant.
I attempted to modify ConnectBot to fix this problem, but unfortunately
this was not possible because android.net.Uri does not support IPv6 address
literals in URIs :-(. This means that unless ConnectBot avoids using the
Android Uri class, we probably have to wait for Google to fix it.
conne...@googlecode.com
Comment #1 on issue 447 by wswartze...@gmail.com: Allow IPv6 address
literals
http://code.google.com/p/connectbot/issues/detail?id=447
IPv6 is now available over Verizon 3G in some areas. Is there any update
on this?
conne...@googlecode.com
Comment #2 on issue 447 by and...@jorgensenfamily.us: Allow IPv6 address
literals
http://code.google.com/p/connectbot/issues/detail?id=447
FWIW, this form is defined in STD66 http://tools.ietf.org/html/std66
Is there an issue already open on Android to properly support this?
conne...@googlecode.com
Comment #3 on issue 447 by snea...@gmail.com: Allow IPv6 address literals
https://code.google.com/p/connectbot/issues/detail?id=447
Just ran into this with the latest version.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings