Arch Linux

fuwhereisfu

Member

Registered: 2009-08-27

Posts: 6

sshd IPv6 timeout

Hi,

I have an installation of arch running on a VM with bridged adapter and am testing some IPv6 connectivity. I am struggling to ssh to it over IPv6 from my windows box (putty client), however connecting over IPv4 works fine. I'm able to ping6 the VM and also have a webserver (tinyhttpd) up and running accepting connections on IPv6. I'm fairly new to linux and have hit a roadblock.. it could be / most likely is something pretty obvious.. I've looked at putty FAQ and Ipv6 should be supported by default.

I've tried specifying the following in sshd_config:

AddressFamily inet6
ListenAddress ::

and have also tried specifying the address listed on eth0

Any help would be greatly appreciated!!

Thanks,

DenaMorley

Member

Registered: 2012-09-13

Posts: 1

Re: sshd IPv6 timeout

I'm using ipv6 without problems here, you can just comment out all AddressFamily and ListenAddress lines (also those from ipv4).
In that case the ssh daemon will listen to everything it can, which will rule out that listening to the wrong addresses is part of the problem.
Also try logging in from another system (or from the web) that certainly has v6-support to rule out that the client is the problem.

fukawi2

Ex-Administratorino

From: .vic.au

Registered: 2007-09-28

Posts: 6,222

Website

Re: sshd IPv6 timeout

To check that SSH is listening for IPv6:

# netstat -tnlp | grep sshd
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      1507/sshd           
tcp6       0      0 :::22                   :::*                    LISTEN      1507/sshd   

Also check your ip6tables... You haven't said you've got it configured or not, but doesn't hurt to check.

---

Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?

BlueHackers // fscanary // resticctl

fuwhereisfu

Member

Registered: 2009-08-27

Posts: 6

Re: sshd IPv6 timeout

Thanks guys, I tried netstat and it is listening for IPv6. I tried connecting to itself locally and it worked.. so I guess there isn't a problem with the sshd setup. Something on the network instead, i'm on a corporate network so I'll investigate that end.