Hi Mike,
That's exactly how I had mine setup all along:
host all all 10.29.15.0 255.255.255.0 trust
and it just doesn't work via VPN.
Thanks,
- Lily Anne
-----Original Message-----
From: mike g [mailto:mike@thegodshalls.com]
Sent: Wednesday, May 26, 2004 11:16 PM
To: LSanchez@ameritrade.com
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] pg_hba.conf
Hello,
I finally got it to work and as some have mentioned it was not the
encryption level.
I had setup my pg_hba.conf originally like this:
host all all 10.15.0.0 255.255.255.0 trust
I was under the impression that the .0 was supposed to be equivalent to
a wildcard entry so that any connection from 10.15 would be able to
connect. This was not so. By changing my pg_hba.conf to this:
host all all 10.15.13.0 255.255.255.0 trust
I was able to connect successfully. The .0 works as a wildcard entry
for the last part but not the one prior.
Hope that helps you.
Mike
On Wed, 2004-05-26 at 10:25, LSanchez@ameritrade.com wrote:
> Thanks so much! :)
>
> -----Original Message-----
> From: Bruce Momjian [mailto:pgman@candle.pha.pa.us]
> Sent: Wednesday, May 26, 2004 10:56 AM
> To: LSanchez@ameritrade.com
> Cc: mike@thegodshalls.com; xzilla@users.sourceforge.net;
> pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] pg_hba.conf
>
> LSanchez@ameritrade.com wrote:
> > Thanks Mike!
> >
> > Do you know if pgSQL will be supporting higher level of encryption
in
> > the near future? Most of us here at Ameritrade work from home via
VPN.
>
>
> We support SSL so you don't need VPN encryption. However, we should
> work with whatever VPN encryption you are already using too.
