From: | "Armstrong, Marc" <marmstrong(at)danly(dot)com> |
---|---|
To: | "'mike(at)thegodshalls(dot)com'" <mike(at)thegodshalls(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: pg_hba.conf |
Date: | 2004-05-27 14:11:05 |
Message-ID: | 0ACA2EE4176CD411B4F90008C709C783063A391C@ACME |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Mike,
I think if you set it up like this it would have worked as well:
host all all 10.15.0.0 255.255.0.0 trust
Your netmask was telling it that the first three octets of the IP address
were significant.
Marc Armstrong - Webmaster - Danly IEM - 440-239-7607
marmstrong(at)danly(dot)com - webmaster(at)danly(dot)com
AIM: marmstro2 - Jabber: marmstro(at)amessage(dot)de
-----Original Message-----
From: mike g [mailto:mike(at)thegodshalls(dot)com]
Sent: Wednesday, May 26, 2004 11:16 PM
To: LSanchez(at)ameritrade(dot)com
Cc: pgsql-admin(at)postgresql(dot)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(at)ameritrade(dot)com wrote:
> Thanks so much! :)
>
> -----Original Message-----
> From: Bruce Momjian [mailto:pgman(at)candle(dot)pha(dot)pa(dot)us]
> Sent: Wednesday, May 26, 2004 10:56 AM
> To: LSanchez(at)ameritrade(dot)com
> Cc: mike(at)thegodshalls(dot)com; xzilla(at)users(dot)sourceforge(dot)net;
> pgsql-admin(at)postgresql(dot)org
> Subject: Re: [ADMIN] pg_hba.conf
>
> LSanchez(at)ameritrade(dot)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.
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you received
this in error, please contact the sender and delete the material from any
computer.
From | Date | Subject | |
---|---|---|---|
Next Message | LSanchez | 2004-05-27 14:12:27 | Re: pg_hba.conf |
Previous Message | Jim Seymour | 2004-05-27 14:02:56 | Re: pg_hba.conf |