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 10000
Trying 203.178.141.194...
telnet: connect to address 203.178.141.194: Connection refused
Trying 2001:200:dff:fff1:216:3eff:feb1:44d7...
telnet: connect to address 2001:200:dff:fff1:216:3eff:feb1:44d7: No
route to host
No route to host ... can you ping6/traceroute6 to www.kame.net? Can
you reach it with: telnet -6 www.kame.net 80 ?
Your connectivity to there seems to be foobared if you'd ask me as:
bz:~> telnet -6 www.kame.net 10000
Trying 2001:200:dff:fff1:216:3eff:feb1:44d7...
telnet: connect to address 2001:200:dff:fff1:216:3eff:feb1:44d7: Connection
refused
telnet: Unable to connect to remote host
I get the connection refused.
telnet: Unable to connect to remote host
Though it works locally:
telnet localhost 10000
Trying 127.0.0.1...
telnet: connect to address 127.0.0.1: Connection refused
Trying ::1...
telnet: connect to address ::1: Connection refused
telnet: Unable to connect to remote host
--
Bjoern A. Zeeb Welcome a new stage of life.
<ks> Going to jail sucks -- <bz> All my daemons like it!
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/jails.html
_______________________________________________
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
