This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/db-wg@ripe.net/

[db-wg] Yet another ipv6 bug ;)

Previous message (by thread): [db-wg] Yet another ipv6 bug ;)
Next message (by thread): [db-wg] 2006-03 Policy Proposal Withdrawn (LIR-PARTITIONED status for IPv6)

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Agoston Horvath agoston at ripe.net
Mon Jul 3 16:45:15 CEST 2006

Dear Max,

The limit for the simultaneous connections was 2 for the IPv6 proxy, and
it's been used up for the web server, that's why you see that message.
I've increased this limit now.

As you probably know, we are phasing the IPv6 whois proxy out in favor
of true IPv6 support, so these strange behaviors when using IPv6 will go
away.

Regards,
Agoston Horvath
Software Engineering Department
RIPE NCC

Max Tulyev wrote:

> Hi!
>
> If I go to www.ripe.net right now and ask for ORG-RL14-RIPE in whois
> from IP  2a01:d8:0:99:211:11ff:fe1f:bfc9 - I get
>
> %ERROR:208: connection refused
>
> From IP 195.209.61.241 everything seems to be fine.
>
> What is it?
>

Previous message (by thread): [db-wg] Yet another ipv6 bug ;)
Next message (by thread): [db-wg] 2006-03 Policy Proposal Withdrawn (LIR-PARTITIONED status for IPv6)

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]