From: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Tommi Mäkitalo <t(dot)maekitalo(at)epgmbh(dot)de>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: TCP/IP with 7.4 beta2 broken? |
Date: | 2003-09-02 00:21:04 |
Message-ID: | 3F53E270.7090205@pse-consulting.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
>Tommi =?iso-8859-15?q?M=E4kitalo?= <t(dot)maekitalo(at)epgmbh(dot)de> writes:
>
>
>>For remote connections I added:
>>host all all ::ffff:192.168.41.0/120 trust
>>and it worked also (I guessed it - I don't know much about IPv6). Is
>>there any chance to get it work like 7.3? It is no nice experience for
>>new users.
>>
>>
>
>Are you saying it does not work with just 192.168.41.0/24 ? That would
>be really unfortunate --- it suggests that your kernel pretends that
>IPv4 connections are IPv6.
>
>
Tom,
we discussed this problem some months ago when I started using 7.4 on
SuSE 8.1. Since 7.4 accepts IPV6, the kernel will always deliver IPV6
addresses, that's why I find most IPV6 problems. While this behaviour
might be irritating, it shouldn't be much of a problem if known.
How about silently creating a IPV6 style host internally for every IPV4
pg_hba.conf entry? It won't make any sense to handle a real IPV4 address
different from an IPV4 address converted to IPV6 address space.
Regards,
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2003-09-02 00:30:39 | Re: TCP/IP with 7.4 beta2 broken? |
Previous Message | Andrew Dunstan | 2003-09-02 00:15:42 | Re: massive quotes? |