Hi Grigory, all,

The problems you might observe right now are in fact caused by 
a 'no route to host' error. We are running IBGP to 
UNI-LEIPZIG, but this peering is down in this very moment.
I am aware of this problem and hope to solve it soon, please be 
patient for while.

Thanx,
   Christian

On 17-Oct-2000 Grigory Kljuchnikov wrote:
> Hello,
> 
> I've tried to get a file with wget and have got a trouble. The host
> 6bone.informatik.uni-leipzig.de has got both ipv6 and ipv4 RRs in DNS:
> 
> IN AAAA               3ffe:400:280::1
> IN A          139.18.38.71
> 
> But wget try ipv6 and if it's a problem exit with error. If I use explicit
> ipv4 address wget work properly:
> 
> 1)
> $ wget ftp://6bone.informatik.uni-leipzig.de/pub/wget.tar.gz
> --15:49:15--  ftp://6bone.informatik.uni-leipzig.de:21/pub/wget.tar.gz
>            => `wget.tar.gz'
> Connecting to 6bone.informatik.uni-leipzig.de:21... 
> connect: No route to host
> Retrying.
> 
> ...
> 
> --15:49:19--  ftp://6bone.informatik.uni-leipzig.de:21/pub/wget.tar.gz
>   (try:20) => `wget.tar.gz'
> Connecting to 6bone.informatik.uni-leipzig.de:21... 
> connect: No route to host
> Giving up.
> 
> 2)
> $ wget ftp://139.18.38.71/pub/wget.tar.gz
> --17:00:39--  ftp://139.18.38.71:21/pub/wget.tar.gz
>            => `wget.tar.gz'
> Connecting to 139.18.38.71:21... connected!
> Logging in as anonymous ... Logged in!
> ==> TYPE I ... done.  ==> CWD pub ... done.
> ==> PORT ... done.    ==> RETR wget.tar.gz ...
> 
> 3)
> Then I've tried to use ftp and it's OK:
> 
> $ ftp 6bone.informatik.uni-leipzig.de
> ftp: connect to address 3ffe:400:280::1: No route to host
> Trying 139.18.38.71...
> Connected to 6bone.informatik.uni-leipzig.de.
> 220 6bone FTP server (Version 6.00) ready.
> Name (6bone.informatik.uni-leipzig.de:grn): ftp
> 331 Guest login ok, type your name as password.
> Password:
> 
> Is it a bug? Or it's a specific implementation of wget.

---------------------------------------------------------------------
The IPv6 Users Mailing List
Unsubscribe by sending "unsubscribe users" to [EMAIL PROTECTED]

Reply via email to