all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Chong Yidong" <cyd@stupidchicken.com>
Subject: ange-ftp and ipv6
Date: Fri, 8 Apr 2005 09:23:20 -0400 (EDT)	[thread overview]
Message-ID: <1051.220.255.169.33.1112966600.squirrel@220.255.169.33> (raw)

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?

             reply	other threads:[~2005-04-08 13:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-08 13:23 Chong Yidong [this message]
2005-04-09  3:38 ` ange-ftp and ipv6 Richard Stallman
2005-04-15 11:10   ` Chong Yidong
2005-04-16  2:58     ` Richard Stallman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1051.220.255.169.33.1112966600.squirrel@220.255.169.33 \
    --to=cyd@stupidchicken.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.