On Mon, 6 Dec 2010, Terry Kennedy wrote:
Hi,
Sorry, you're right: I forgot I don't have my tunnel setup so there's no
external IPv6 connectivity (I don't have an IPv6 network configured at
the moment at all). What confused me initially was the fact that ssh
displays the "No route to host" error
> Sorry, you're right: I forgot I don't have my tunnel setup so there's no
> external IPv6 connectivity (I don't have an IPv6 network configured at
> the moment at all). What confused me initially was the fact that ssh
> displays the "No route to host" error instead of "Connection refused"
> when b
On Wed, 1 Dec 2010 21:40:16 + (UTC)
"Bjoern A. Zeeb" wrote:
> Your connectivity to there seems to be foobared if you'd ask me as:
Sorry, you're right: I forgot I don't have my tunnel setup so there's no
external IPv6 connectivity (I don't have an IPv6 network configured at
the moment at all)
On Wed, 1 Dec 2010, Bruce Cran wrote:
It appears that the network stack on -CURRENT is returning EHOSTUNREACH
instead of ECONNREFUSED when trying to connect to a closed port over
IPv6. e.g.:
telnet www.kame.net 1
Trying 203.178.141.194...
telnet: connect to address 203.178.141.194: Connec
It appears that the network stack on -CURRENT is returning EHOSTUNREACH
instead of ECONNREFUSED when trying to connect to a closed port over
IPv6. e.g.:
> telnet www.kame.net 1
Trying 203.178.141.194...
telnet: connect to address 203.178.141.194: Connection refused
Trying 2001:200:dff:fff1:216
