From owner-freebsd-questions@FreeBSD.ORG Wed Jul 28 15:53:01 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 50CAE16A4CE for ; Wed, 28 Jul 2004 15:53:01 +0000 (GMT) Received: from pearl.ibctech.ca (dev.eagle.ca [209.167.58.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D77E43D66 for ; Wed, 28 Jul 2004 15:53:00 +0000 (GMT) (envelope-from iaccounts@ibctech.ca) Received: (qmail 75550 invoked by uid 1002); 28 Jul 2004 15:53:11 -0000 Received: from iaccounts@ibctech.ca by pearl.ibctech.ca by uid 89 with qmail-scanner-1.22 (clamscan: 0.73. spamassassin: 2.63. Clear:RC:1(127.0.0.1):. Processed in 1.245294 secs); 28 Jul 2004 15:53:11 -0000 Received: from unknown (HELO webmail.ibctech.ca) (127.0.0.1) by localhost.ibctech.ca with SMTP; 28 Jul 2004 15:53:09 -0000 Received: from 209.167.16.15 (SquirrelMail authenticated user steve@ibctech.ca); by webmail.ibctech.ca with HTTP; Wed, 28 Jul 2004 11:53:09 -0400 (EDT) Message-ID: <3816.209.167.16.15.1091029989.squirrel@209.167.16.15> In-Reply-To: <200407281637.23563.dgw@liwest.at> References: <200407281452.00859.dgw@liwest.at> <200407281611.09200.dgw@liwest.at> <3652.209.167.16.15.1091028200.squirrel@209.167.16.15> <200407281637.23563.dgw@liwest.at> Date: Wed, 28 Jul 2004 11:53:09 -0400 (EDT) From: "Steve Bertrand" To: dgw@liwest.at User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal cc: questions@freebsd.org Subject: Re: Problems after IP change X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jul 2004 15:53:01 -0000 > On Wednesday 28 July 2004 15:23, Steve Bertrand wrote: >> > Yes, it works, but of course I can't leave this rule in all the time. >> >> The SYN/ACK packet that comes back from the remote server is denied by >> rule >> >> > 01900. But it should be allowed by the check-state rule. >> > >> >> Also, I know you haven't changed anything, but what does the output >> >> from >> >> >> this command state?: >> >> # sysctl net.inet.ip.forwarding >> > >> > It is set to 1. I changed this a long time ago. >> >> I figured so...what happens if you add 'keep-state' to rules 20000, >> 20002 >> and 20003? > > Nothing. > BTW, here we have the problem: The initial SYN packet isn't matched by > rule > 11700 (setup keep-state). Setup means the SYN flag is set, right? AFAIK, setup means the SYN bit MUST be set. Try these rules: > add 01900 deny log tcp from any to any in established add 2000 allow log all from any to any in via rl1 keep-state add 2002 allow log all from any to any out via rl0 keep-state > So why > is > it not matched? If I remove the "setup" keyword to match all outgoing > packets, the SYN/ACK from the server is still denied by rule 01900. I'll go over the ruleset again here and see if I can find a misplaced 'out' or 'in'. Steve > >