Re: TCP/IP with 7.4 beta2 broken?

From: Kurt Roeckx <Q(at)ping(dot)be>
To: Tommi Mäkitalo <t(dot)maekitalo(at)epgmbh(dot)de>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: TCP/IP with 7.4 beta2 broken?
Date: 2003-09-03 17:14:08
Message-ID: 20030903171408.GA7907@ping.be
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Sep 01, 2003 at 09:59:17PM +0200, Tommi Mäkitalo wrote:
>
> psql: FATAL: no pg_hba.conf entry for host "::ffff:127.0.0.1", user
> "postgres", database "template1"

This is a Linux system that does not have the IPV6_V6ONLY
setsockopt() option. Linux only has this option since 2.4.21
(pre3).

This means that an IPv6 socket bound to "::" (all addresses) will
listen for both all IPv4 and IPv6 addresses.
If that option exists, it will only listen to all IPv6 addresses.
If the option doesn't exist, it can't bind to the 0.0.0.0 ipv4
socket, because the IPv6 socket already is bound to it.

So all connections you get are, from the application's point of
view, IPv6 connections.

IPv4 connections on an AF_INET6 socket are called IPv4-mapped
IPv6. It was something they created to make it easier to port
applications to IPv6, but it only makes things worse.

Kurt

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2003-09-03 17:25:48 Re: testing for usable C compiler
Previous Message Andreas Pflug 2003-09-03 17:12:56 Re: TCP/IP with 7.4 beta2 broken?