Re: No entry to pg_hba.conf 10.17.11.16 - Mailing list pgadmin-support

From Dave Page
Subject Re: No entry to pg_hba.conf 10.17.11.16
Date
Msg-id 03AF4E498C591348A42FC93DEA9661B8259D95@mail.vale-housing.co.uk
Whole thread Raw
In response to No entry to pg_hba.conf 10.17.11.16  (Fabiano <fcostola@osite.com.br>)
List pgadmin-support

> -----Original Message-----
> From: Roman Fail [mailto:rfail@posportal.com]
> Sent: 12 March 2003 16:01
> To: Fabiano; pgadmin-support@postgresql.org
> Subject: Re: [pgadmin-support] No entry to pg_hba.conf 10.17.11.16
>
>
> I'm not a TCP/IP networking expert, but I'm pretty certain
> that 10.x.x.x addresses are the very definition of a private
> non-routable Class A network.  Which means the subnet mask
> should be 255.0.0.0.
>

Yes and no. In this case, the mask is used to determine the number of
bits in the address that are relevant to the rule, so:

192.168.1.1 255.255.255.255 - All bits are relevant, so the entry
applies only to that exact address.
192.168.1.1 255.255.255.0 - The first 24 bits are relevant, so the entry
applies to 192.168.1.x
192.168.1.1 255.255.0.0 - The first 16 bits are relevant, so the entry
applies to 192.168.x.x

I think in this case, the problem is that 'local' is specified, which
generally applies to Unix domain sockets, and that one column is missing
as Keith suggested:

> local    all    10.17.11.0    255.255.255.0    trust

To let hosts with an address of 10.17.11.x in, the entry should probably
be:

host         all           all       10.17.11.0     255.255.255.0
trust

Regards, Dave.

Attachment

pgadmin-support by date:

Previous
From: "Roman Fail"
Date:
Subject: Re: No entry to pg_hba.conf 10.17.11.16
Next
From: Lamar Owen
Date:
Subject: Re: No entry to pg_hba.conf 10.17.11.16