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 83797D1B8A9 for ; Thu, 27 May 2004 00:36:33 -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 83059-03 for ; Thu, 27 May 2004 00:36:12 -0300 (ADT) Received: from fusion.bennyvision.com (fusion.bennyvision.com [216.161.119.28]) by svr1.postgresql.org (Postfix) with SMTP id 82DB3D1B265 for ; Thu, 27 May 2004 00:36:10 -0300 (ADT) Received: (qmail 22610 invoked from network); 27 May 2004 03:36:09 -0000 Received: from localhost (HELO webmail.stinkweasel.net) (127.0.0.1) by fusion.bennyvision.com with SMTP; 27 May 2004 03:36:09 -0000 Received: from 63.227.74.41 (SquirrelMail authenticated user benny) by webmail.stinkweasel.net with HTTP; Wed, 26 May 2004 22:35:47 -0500 (CDT) Message-ID: <54543.63.227.74.41.1085628969.squirrel@webmail.stinkweasel.net> In-Reply-To: <1085627775.4674.8.camel@localhost.localdomain> References: <2898C2526ECBEB448D434BA1F3027909034D9798@scsdcmail1.ameritrade.com> <1085627775.4674.8.camel@localhost.localdomain> Date: Wed, 26 May 2004 22:35:47 -0500 (CDT) Subject: Re: pg_hba.conf From: "C. Bensend" To: mike@thegodshalls.com Cc: lsanchez@ameritrade.com, pgsql-admin@postgresql.org User-Agent: SquirrelMail/1.4.2 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 Importance: Normal X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.8 tagged_above=0.0 required=5.0 tests=PRIORITY_NO_NAME X-Spam-Level: X-Archive-Number: 200405/285 X-Sequence-Number: 13601 > 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. Yes, when your subnet mask is set for a /24, that's correct. Your first attempt above allowed connections for anything in the 10.15.0/24 subnet (which 10.15.13 is not a part of). Benny -- "Oh, the Jedis are going to feel this one!" -- Professor Farnsworth, "Futurama"