I am unable to duplicate this issue on my local Ubuntu Intrepid 8.10 (x64) desktop, even before making any of the changes suggested in this message.
For those who are affected by this:
ssh -4 somehost
will use IPv4 only to connect, which would appear to be a viable workaround.
To make IPv4 only a global default for the client, edit /etc/ssh/ssh_config and add a line
AddressFamily inet
to the end of the default file (i.e., in the entry for "Host *).
At the server end of things, one can configure sshd to use IPv4 only by adding a line
ListenAddress 0.0.0.0
to /etc/ssh/sshd_config and restarting sshd.
I am unable to duplicate this issue on my local
Ubuntu Intrepid 8.10 (x64) desktop, even before
making any of the changes suggested in this message.
For those who are affected by this:
ssh -4 somehost
will use IPv4 only to connect, which would appear to
be a viable workaround.
To make IPv4 only a global default for the client,
edit /etc/ssh/ssh_config and add a line
AddressFamily inet
to the end of the default file (i.e., in the entry for "Host *).
At the server end of things, one can configure sshd to
use IPv4 only by adding a line
ListenAddress 0.0.0.0
to /etc/ssh/ sshd_config and restarting sshd.