Re: TCP/IP with 7.4 beta2 broken? - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: TCP/IP with 7.4 beta2 broken?
Date
Msg-id 3F53E4AF.5020000@dunslane.net
Whole thread Raw
In response to Re: TCP/IP with 7.4 beta2 broken?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: TCP/IP with 7.4 beta2 broken?
List pgsql-hackers
Quick fix is probably to turn IPv6 off in the kernel unless it's needed 
- on my RH box that is as simple as removing a line from 
/etc/sysconfig/network and rebooting

Kurt Roeckx knows more about this than I do, but I know when I turned 
IPv6 on I had to do something similar to what is below - I seem to 
recall we had a discussion about this somewhere.  I think we (or at 
least I) assumed that folks who turned on IPv6 would be able to figure 
this stuff out for themselves. If distributions are starting to ship 
with it turned on we may have to revisit that.

There seems to be some IPv6 warts, even though it does work.

cheers

andrew

Tom Lane wrote:

>Tommi Mäkitalo <t.maekitalo@epgmbh.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.
>
>            regards, tom lane
>
>---------------------------(end of broadcast)---------------------------
>TIP 4: Don't 'kill -9' the postmaster
>
>  
>



pgsql-hackers by date:

Previous
From: Andreas Pflug
Date:
Subject: Re: TCP/IP with 7.4 beta2 broken?
Next
From: "Christopher Kings-Lynne"
Date:
Subject: Need for a 'minor patch person'?