From: | Ron Chmara <ron(at)opus1(dot)com> |
---|---|
To: | Ron Atkins <theotiwii(at)earthlink(dot)net> |
Cc: | Postgres <pgsql-general(at)postgreSQL(dot)org> |
Subject: | Re: [GENERAL] DHCP and pg_hba.conf |
Date: | 2000-03-06 20:52:20 |
Message-ID: | 38C41A84.C5857C3C@opus1.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Ron Atkins wrote:
> This is my first day here. I'm writing a HowTo for a GPL'ed accounting
> system (Kontor) that uses PostgreSQL.
> I don't use DHCP (Dynamic Host Configuration Protocol). Those
> that do know the client IP address is assigned dynamically.
...based on a few things. It can assign random from a pool. It can
assign *specific* IP numbers to *specific* machines, as well.
> That being the case, how does one set up access / security in the
> pg_hba.conf file (since it requires ip addresses)?
I havn't poked into hba.conf for a while, but DHCP is about
dynamic *assignment*. It doesn't mean that machines can't always
get the same IP, it just means that the IP is dynamically assigned
to the host...
*However*, if you look at the last example on this page:
http://www.postgresql.org/docs/admin/security.htm#AEN1240
You can see that an entire block can be considered valid, trusted,
or non-trusted. This means your can set an entire DHCP pool
range to be trusted, if you wish.
-Ronabop
--
Brought to you from boop!, the dual boot Linux/Win95 Compaq Presario 1625
laptop, currently running RedHat 6.1. Your bopping may vary...and winmodems
suck big smelly rocks.
From | Date | Subject | |
---|---|---|---|
Next Message | JB | 2000-03-06 22:09:51 | 50 MB Table |
Previous Message | Ed Loehr | 2000-03-06 20:39:54 | Re: [GENERAL] sum() bug? |