[db-wg] RE: [ipv6-wg at ripe.net] IPV6 Whois

I'm getting Type 1 (Unreachable) Code 1 (Administratively Prohibited)
messages back from 2001:7f8:1::a500:3333:1 - luckily the client falls back
to IPv4 and that works just fine ;-)

Mat.

> -----Original Message-----
> From: Pim van Pelt [mailto:pim at ipng.nl]
> Sent: 23 January 2003 14:17
> To: ripe-dbm at ripe.net
> Cc: db-wg at ripe.net; ipv6-wg at ripe.net
> Subject: Re: [ipv6-wg at ripe.net] IPV6 Whois
> 
> 
> | We are happy to announce the availability of RIPE Whois 
> servers on IPv6
> | network. It is now possible to query whois.ripe.net and 
> test-whois.ripe.net
> | from an IPv6 host, using an IPv6 enabled whois client. If 
> your system doesn't
> | already have one, you can find the latest RIPE Whois client at:
> Hi Can,
> 
> I cannot reach the server from AS12859, nor from AS8954.
> 
> --- whois.ripe.net ping6 statistics ---
> 2 packets transmitted, 0 packets received, 100% packet loss
> 
> A traceroute from me (2001:7b8:3:17:202:b3ff:fe10:d926) to you gives:
>  1  dapje-gw.ipv6.network.bit.nl  0.383 ms  0.286 ms  0.269 ms
>  2  jun1.telecity.ipv6.network.bit.nl  1.537 ms  1.552 ms  1.505 ms
>  3  nikipv6.ripe.net  3.378 ms  3.035 ms  3.111 ms
>  4  nikipv6.ripe.net  4.432 ms !P  3.248 ms !P  3.288 ms !P
> 
> And telnetting to port 43 of whois.ripe.net does not do much:
> $ telnet 2001:610:240:0:193::135 whois
> Trying 2001:610:240:0:193::135...
> ^C
> 
> Please advise.
> -- 
> ---------- - -    - - -+- - -    - - ----------
> Pim van Pelt                 Email: pim at ipng.nl
> http://www.ipng.nl/             IPv6 Deployment
> -----------------------------------------------
> 
>