From: Tom Lane <tgl@sss.pgh.pa.us>
To: Geoffrey Knauth <geoff@knauth.org>
Cc: pgsql-sql@postgresql.org
Subject: Re: listen_addresses = '*' ok, specific address(es) no
Date: Thu, 15 Jun 2006 22:46:48 -0400
Message-ID: <12217.1150426008@sss.pgh.pa.us> (raw)
In-Reply-To: <49DF5CA8-5E4D-415E-9A9A-DA412B213DE0@knauth.org>
References: <7F9DD4F9-A334-4A52-8501-1DA780CD4D2E@knauth.org>
<27882.1150382418@sss.pgh.pa.us>
<49DF5CA8-5E4D-415E-9A9A-DA412B213DE0@knauth.org>
Geoffrey Knauth <geoff@knauth.org> writes:
> Andrew Sullivan wrote:
>> Well, do you actually have an interface with that address?
> I think I do, in that the machine's wireless interface is set up with
> a 192.168.1.x/24 address and 1.33 is on the same subnet. Or maybe
> I'm misunderstanding. I thought the purpose of listen_addresses was
> to allowing incoming connections only from listed addresses.
You're misunderstanding then. What listen_addresses can bind to is IP
addresses of *your own machine*. For example, if you bind to only
127.0.0.1 then only local loopback connections will work. Binding to
just one external IP address is only interesting if your machine has
more than one such address; then it prevents connections that're coming
in through one of the other addresses.
The right way to limit incoming connections to only come *from*
particular IP addresses is to use pg_hba.conf.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, geoff@knauth.org
Subject: Re: listen_addresses = '*' ok, specific address(es) no
In-Reply-To: <12217.1150426008@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox