From owner-freebsd-net@FreeBSD.ORG Wed Dec 1 21:58:44 2010 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 481C31065697 for ; Wed, 1 Dec 2010 21:58:44 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (muon.cran.org.uk [IPv6:2a01:348:0:15:5d59:5c40:0:1]) by mx1.freebsd.org (Postfix) with ESMTP id 0C7888FC26 for ; Wed, 1 Dec 2010 21:58:44 +0000 (UTC) Received: from muon.cran.org.uk (localhost [127.0.0.1]) by muon.cran.org.uk (Postfix) with ESMTP id 69EDEE7159; Wed, 1 Dec 2010 21:58:43 +0000 (GMT) Received: from core.draftnet (client-86-31-8-12.midd.adsl.virginmedia.com [86.31.8.12]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA; Wed, 1 Dec 2010 21:58:42 +0000 (GMT) Date: Wed, 1 Dec 2010 21:58:29 +0000 From: Bruce Cran To: "Bjoern A. Zeeb" Message-ID: <20101201215829.2c4387e8@core.draftnet> In-Reply-To: <20101201213841.U6126@maildrop.int.zabbadoz.net> References: <20101201213217.19712470@core.draftnet> <20101201213841.U6126@maildrop.int.zabbadoz.net> X-Mailer: Claws Mail 3.7.6 (GTK+ 2.22.1; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: EHOSTUNREACH returned for refused IPv6 connection X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2010 21:58:44 -0000 On Wed, 1 Dec 2010 21:40:16 +0000 (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). What confused me initially was the fact that ssh displays the "No route to host" error instead of "Connection refused" when both IPv4 and IPv6 addresses are available but only IPv4 works. -- Bruce Cran