X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id B9961D1B587 for ; Thu, 27 May 2004 00:17:08 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 77285-02 for ; Thu, 27 May 2004 00:16:48 -0300 (ADT) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by svr1.postgresql.org (Postfix) with ESMTP id 4E2D3D1B194 for ; Thu, 27 May 2004 00:16:47 -0300 (ADT) Received: from localhost.localdomain (c-67-162-79-220.client.comcast.net[67.162.79.220]) by comcast.net (sccrmhc12) with ESMTP id <20040527031645012007g6n4e>; Thu, 27 May 2004 03:16:46 +0000 Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by localhost.localdomain (8.12.11/8.12.11) with ESMTP id i4R3GGve004757; Wed, 26 May 2004 22:16:16 -0500 Received: (from spike@localhost) by localhost.localdomain (8.12.11/8.12.11/Submit) id i4R3GGht004754; Wed, 26 May 2004 22:16:16 -0500 X-Authentication-Warning: localhost.localdomain: spike set sender to mike@thegodshalls.com using -f Subject: Re: pg_hba.conf From: mike g Reply-To: mike@thegodshalls.com To: LSanchez@ameritrade.com Cc: pgsql-admin@postgresql.org In-Reply-To: <2898C2526ECBEB448D434BA1F3027909034D9798@scsdcmail1.ameritrade.com> References: <2898C2526ECBEB448D434BA1F3027909034D9798@scsdcmail1.ameritrade.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1085627775.4674.8.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 (1.4.5-7) Date: Wed, 26 May 2004 22:16:15 -0500 X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=1.4 tagged_above=0.0 required=5.0 tests=RCVD_IN_SORBS, WORK_AT_HOME X-Spam-Level: * X-Archive-Number: 200405/284 X-Sequence-Number: 13600 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.