From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Chong Yidong" Newsgroups: gmane.emacs.devel Subject: ange-ftp and ipv6 Date: Fri, 8 Apr 2005 09:23:20 -0400 (EDT) Message-ID: <1051.220.255.169.33.1112966600.squirrel@220.255.169.33> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: sea.gmane.org 1112966666 7964 80.91.229.2 (8 Apr 2005 13:24:26 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 8 Apr 2005 13:24:26 +0000 (UTC) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Apr 08 15:24:22 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1DJtSC-0003kp-Fx for ged-emacs-devel@m.gmane.org; Fri, 08 Apr 2005 15:23:21 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DJt1i-0001WQ-4l for ged-emacs-devel@m.gmane.org; Fri, 08 Apr 2005 08:55:58 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DJt1X-0001Uh-Jw for emacs-devel@gnu.org; Fri, 08 Apr 2005 08:55:47 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DJt1U-0001Tq-UI for emacs-devel@gnu.org; Fri, 08 Apr 2005 08:55:45 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DJt1U-0001T3-Oh for emacs-devel@gnu.org; Fri, 08 Apr 2005 08:55:44 -0400 Original-Received: from [64.21.80.18] (helo=shark.dnsvelocity.com) by monty-python.gnu.org with esmtp (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA:24) (Exim 4.34) id 1DJtT6-0005o3-SW for emacs-devel@gnu.org; Fri, 08 Apr 2005 09:24:17 -0400 Original-Received: from stupidch by shark.dnsvelocity.com with local (Exim 4.44) id 1DJtSC-0001kA-3p for emacs-devel@gnu.org; Fri, 08 Apr 2005 09:23:20 -0400 Original-Received: from 220.255.169.33 ([220.255.169.33]) (SquirrelMail authenticated user cyd@stupidchicken.com); by www.stupidchicken.com with HTTP; Fri, 8 Apr 2005 09:23:20 -0400 (EDT) Original-To: emacs-devel@gnu.org User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a X-Priority: 3 (Normal) Importance: Normal X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - shark.dnsvelocity.com X-AntiAbuse: Original Domain - gnu.org X-AntiAbuse: Originator/Caller UID/GID - [32675 33085] / [47 12] X-AntiAbuse: Sender Address Domain - stupidchicken.com X-Source: /usr/local/cpanel/3rdparty/bin/php X-Source-Args: /usr/local/cpanel/3rdparty/bin/php /usr/local/cpanel/base/3rdparty/squirrelmail/src/compose.php X-Source-Dir: :/base/3rdparty/squirrelmail/src X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:35759 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:35759 I've been trying to reproduce the following bug from FOR-RELEASE: > ** Ange-ftp should ignore irrelevant IPv6 errors: > ... > The problem is that the DNS first gives an IPV6 address. However our > router doesn't do IPV6. Ftp then falls back to IPV4: > > ftp> open ftp.nluug.nl > Trying 2001:610:1:80aa:192:87:102:36... > ftp: connect to address 2001:610:1:80aa:192:87:102:36: No route to host > Trying 192.87.102.36... > Connected to ftp.nluug.nl. > > Ange-ftp chokes on the `No route to host' message and doesn't look any > further. My DNS also issues an IPV6 address, but the ftp program I use (BSD ftp on a Red Hat box) fails silently on IPV6 without issuing a "No route to host" message: ftp> open ftp.nluug.nl Trying 2001:610:1:80aa:192:87:102:36... Trying 192.87.102.36... Connected to ftp.nluug.nl (192.87.102.36). Does anyone know a simple way to reproduce this bug? In any case, could it be fixed by replacing "No route to host" with "No route to host\n[^T]" in ange-ftp-gateway-fatal-msgs, to distinguish between "No route to host\nTrying..." and a real error?