Secure* address family option

[Maureen]

We recently made a change so that SecureCRT uses the IP address that is first in the list sent by the remote server, which may make an option to force the IP address type unnecessary. This change has been made in a pre-beta version of SecureCRT. If you'd like to try it, please send email to me at Maureen.Jett@vandyke.com.

Maureen

[jnagler]

I can't believe there was no progress in 10 years when OpenSSH had this already available back then.

This may be Germany/European specific but is crucial:

• public dynamic (changing daily) IPv4 + public (most often static but could also be dynamic) IPv6 addresses
• DynDNS service propagating both IPv4 and IPv6 addresses for one DNS entry
• legacy IPv4 only devices behind this addresses

Generally preferring IPv4 over IPv6 is not a good solution as connecting to legacy servers should not determine your preferred way. With CGN at some ISPs there is an even worse scenario where the IPv4 only devices are no more directly to connect from the internet. But as long as we still have public IPv4 addresses I'm reluctant to accept you guys ignored this for so long...

[Maureen]

Hi jnagler,

SecureCRT does not prefer IPv4 addresses. In 2016, I posted the following in this thread:

We recently made a change so that SecureCRT uses the IP address that is first in the list sent by the remote server, which may make an option to force the IP address type unnecessary. This change has been made in a pre-beta version of SecureCRT. If you'd like to try it, please send email to me at Maureen.Jett@vandyke.com.

This change was released officially in version 8.1. If it's not working in your environment, please email me at Maureen.Jett@vandyke.com so that we can discuss possible solutions.

Maureen

[ddx]

Any news on this ?

[ekoranyi]

Hi ddx,

It sounds like you're interested in the ability to manually select if an IPv4/6 address is used, is that the case?

Currently SecureCRT will use the first IP address returned by a DNS lookup, perhaps working with DNS settings to return IPv4/6 first would help resolve the issue.