Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 90DCD9F9F08 for ; Fri, 17 Nov 2006 18:55:27 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 92723-02 for ; Fri, 17 Nov 2006 22:55:15 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 013B79F9B3F for ; Fri, 17 Nov 2006 18:55:14 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id kAHMsuEo022005; Fri, 17 Nov 2006 17:54:57 -0500 (EST) To: Jeff Frost cc: Paul Forgey , pgsql-admin@postgresql.org Subject: Re: remote connections to Windows based server In-reply-to: References: Comments: In-reply-to Jeff Frost message dated "Fri, 17 Nov 2006 14:41:49 -0800" Date: Fri, 17 Nov 2006 17:54:56 -0500 Message-ID: <22004.1163804096@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200611/175 X-Sequence-Number: 23702 Jeff Frost writes: > I believe you must list all 4 octets of the subnet. Oh, duh. The comments in inet_aton() show that it is interpreting "10.6" in what most people nowadays would find a surprising way: case 1: /* a -- 32 bits */ case 2: /* a.b -- 8.24 bits */ case 3: /* a.b.c -- 8.8.16 bits */ case 4: /* a.b.c.d -- 8.8.8.8 bits */ ie, it is read as if it were "10.0.0.6" ... hence no match, but also no syntax error. regards, tom lane