From owner-freebsd-isp Sat Jun 26 14:29:21 1999 Delivered-To: freebsd-isp@freebsd.org Received: from snake.supranet.net (snake.supranet.net [205.164.160.19]) by hub.freebsd.org (Postfix) with ESMTP id EDFD814FAE for ; Sat, 26 Jun 1999 14:29:19 -0700 (PDT) (envelope-from john@arnie.jfive.com) Received: from snake.supranet.net (snake.supranet.net [205.164.160.19]) by snake.supranet.net (8.8.8/8.8.8) with SMTP id QAA29572 for ; Sat, 26 Jun 1999 16:34:32 -0500 (CDT) (envelope-from john@arnie.jfive.com) Date: Sat, 26 Jun 1999 16:34:32 -0500 (CDT) From: John Heyer X-Sender: john@snake.supranet.net To: freebsd-isp@freebsd.org Subject: Trouble with routes and natd Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Here's the situation: we have a FreeBSD 3.2 machine running natd and ipfw with one external interface (205.164.160.26, 27-29 aliases), and one internal interface. To get to the entire internal network, we go through a compatible 2600 router with "route add 10.1.0.0 -netmask 255.255.252.0 10.1.3.20". While the internal network gets out fine, we're having trouble with natd re-directing from external to internal so outside people can get to the servers. Using tcpdump on the internal ethernet card, I see packets being sent to the correct internal machine then returning, however the client never gets anything back. While this would appear a firewall situation, the correct ports are opened up and quiet mode is off, showing no packets denied. We've setup several proxy servers running natd/ipfw where port-re-direction was used, and this is the first time there's been trouble. I was wondering if perhaps the static route command could mess things up? Any ideas greatly appreciated. -- "Your illogical approach ... does have its advantages." -- Spock, after being Checkmated by Kirk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message