Psql wants to use IP6 when connecting to self using tcp...

From: Jerry Levan <jerry(dot)levan(at)gmail(dot)com>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Psql wants to use IP6 when connecting to self using tcp...
Date: 2021-06-22 00:44:16
Message-ID: E2F44383-6C51-4B0E-B26B-759ED4252BEF@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Today I upgraded my Fedora system to Fedora 35 which included an upgrade to
PostgreSQL 13.x.x.
I did an initdb and restored my existing db from a dump.

I modified pg_hba.conf to allow access machines on my local network
host all all 192.168.1.0/24 trust
I modified postgresql.conf to listen to all interfaces.

Localhost works...
[jerry(at)bigbox ~]$ psql
psql (13.3)
Type "help" for help.

levan=# \q
The below fails... the 'fe80....' is the ip6 address of big box.
[jerry(at)bigbox ~]$ psql -h bigbox
psql: error: FATAL: no pg_hba.conf entry for host "fe80::fe3f:dbff:fed1:f62e%enp7s0", user "lxxx", database "lxxx", SSL off

Using the ip4 address of bigbox works
[jerry(at)bigbox ~]$ psql -h 192.168.1.75
psql (13.3)
Type "help" for help.

lxxx=#

I can connect to/from the other machines in my local network...
Netstat shows that Postgres is listening on a ip6 interface.

What did I have to do get the 'fatal' above case to work?

Trapped in Steve Jobs Reality Distortion Field

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Yu Watanabe 2021-06-22 01:08:19 Re: How to automatically delete idle client connections?
Previous Message Venkat Pathi 2021-06-21 23:11:52 Highly Available Postgres on Kubernetes