Forum

Connecting to an IP...
 
Notifications
Clear all

Connecting to an IPv6 enabled SSH2 Server

0 Posts
2 Users
0 Reactions
104 Views
(@jhookcs)
Active Member
Joined: 14 years ago
Posts: 4
Topic starter  

I know that IPv6 has been supported by AbsoluteTelnet for quite some time (since 2006 +/-) but I am trying to configure the software to connect to the server using the IPv6 address but it always throws this message in my face:

Connecting to [server ipv6 address here]:22
Connect to [server ipv6 address here] failed. Winsock Error: Appearance

Does the hostname field need to be populated by a resolved hostname or can I use the server's ipv6 address?

Please forgive me if this information is already available somewhere; I did search the forums and the website but maybe I missed something.

I will try connecting via a resolved hostname in the meantime to see if that will fix the issue. I will report back with the results soon.


   
ReplyQuote
(@jhookcs)
Active Member
Joined: 14 years ago
Posts: 4
Topic starter  

Ok, I tried using a DNS resolved FQDN (via AAAA record) and it worked! I don't know why I didn't think to try this sooner.

Well it seems I answered my own question.

If you are using IPv6 and are trying to connect to an IPv6 server, you must use a resolved hostname in the field (via dns server, resolv.conf or hosts file) and NOT the IPv6 address itself.


   
ReplyQuote
(@bpence)
Member Admin
Joined: 8 months ago
Posts: 1374
 

Thanks for the update!

I'll look into this further. You should be able to use either the hostname or the ipv6 address.

What version of Windows are you using?

Brian


   
ReplyQuote
(@bpence)
Member Admin
Joined: 8 months ago
Posts: 1374
 

BTW, version 9 added some verbose output during the connection phase so you can see whether you've gotten ipv6 or ipv4 addresses when it resolves the name. It then tries each address in order (IPV6 first). It is possible that the IPV6 connection can fail and the IPV4 connection can succeed. Prior to Absolute V9, you would not notice the difference. In V9, you can see each connect attempt to occur, along with info on which one was ultimately successful.

If you're not using V9, give it a whirl and post the connection output here for us to see!

Brian


   
ReplyQuote
(@jhookcs)
Active Member
Joined: 14 years ago
Posts: 4
Topic starter  

In response to what version I am using, it is Windows 7 Ultimate 64-bit.

I am using AbsoluteTelnet 9.18

[hide]Ok here is the output of when the hostname is 'www.ethericlight.net'

Running in FIPS 140-2 Mode
Validating FIPS certified DLL...Passed

Connecting to www.ethericlight.net:22
attempting [2001:4978:231:0:218:f8ff:fe0a:4226]:22... Success!
Authentication SUCCESS
Allocating PTY... SUCCESS
Start X11 forwarding... Skipped
Starting authentication agent... SUCCESS
Starting shell... SUCCESS

Here is the output when using '[2001:4978:231:0:218:f8ff:fe0a:4226] as the hostname:

Running in FIPS 140-2 Mode
Validating FIPS certified DLL...Passed

Connecting to [2001:4978:231:0:218:f8ff:fe0a:4226]:22
Connect to [2001:4978:231:0:218:f8ff:fe0a:4226] failed. Winsock Error: Appearance

Here it is the same address without the [ ] so the hostname is '2001:4978:231:0:218:f8ff:fe0a:4226'

Running in FIPS 140-2 Mode
Validating FIPS certified DLL...Passed

Connecting to [2001:4978:231:0:218:f8ff:fe0a:4226]:22
Connect to 2001:4978:231:0:218:f8ff:fe0a:4226 failed. Winsock Error: Appearance
[/hide]

Hopefully this was the output you were looking for, if not, let me know and I will try again.


   
ReplyQuote
(@bpence)
Member Admin
Joined: 8 months ago
Posts: 1374
 

I've been working on this tonight, and I did find an ipv6 issue at least under Windows 7 and possibly other versions as well. The problem was preventing Absolute from accepting IPV6 addresses directly. It would still resolve IPV6 addresses if the hostname is used.

Please give this a try:

http://www.celestialsoftware.net/telnet/AbsoluteTelnet9.19.exe

Brian


   
ReplyQuote
(@jhookcs)
Active Member
Joined: 14 years ago
Posts: 4
Topic starter  

[hide]Ok, I installed 9.19 and entered the hostname without brackets '2001:4978:231:0:218:f8ff:fe0a:4226' and it connected!

Running in FIPS 140-2 Mode
Validating FIPS certified DLL...Passed

Connecting to [2001:4978:231:0:218:f8ff:fe0a:4226]:22
attempting [2001:4978:231:0:218:f8ff:fe0a:4226]:22... Success!
Connected to www.ethericlight.net
Authentication SUCCESS
Allocating PTY... SUCCESS
Start X11 forwarding... Skipped
Starting authentication agent... SUCCESS
Starting shell... SUCCESS

here it is again with hostname with brackets [2001:4978:231:0:218:f8ff:fe0a:4226]

Running in FIPS 140-2 Mode
Validating FIPS certified DLL...Passed

Connecting to [2001:4978:231:0:218:f8ff:fe0a:4226]:22
attempting [2001:4978:231:0:218:f8ff:fe0a:4226]:22... Success!
Connected to www.ethericlight.net
Authentication SUCCESS
Allocating PTY... SUCCESS
Start X11 forwarding... Skipped
Starting authentication agent... SUCCESS
Starting shell... SUCCESS

and last but not least hostname as FQDN 'www.ethericlight.net'

Running in FIPS 140-2 Mode
Validating FIPS certified DLL...Passed

Connecting to www.ethericlight.net:22
attempting [2001:4978:231:0:218:f8ff:fe0a:4226]:22... Success!
Authentication SUCCESS
Allocating PTY... SUCCESS
Start X11 forwarding... Skipped
Starting authentication agent... SUCCESS
Starting shell... SUCCESS
[/hide]
So it works beautifully! The FQDN I used has both ipv4 and ipv6 dns records, so the above proves that your software does indeed seek out ipv6 first before it tries ipv4.

Thanks again, and I love your software as it never disappoints with its features and stability.

-Jason

If in the future you need me to test out ipv6 related issues let me know.


   
ReplyQuote
(@bpence)
Member Admin
Joined: 8 months ago
Posts: 1374
 

Thanks for reporting the problem!!

I'm glad I could help.

Brian


   
ReplyQuote
Share: