From owner-freebsd-questions Fri May 28 16:19:50 1999 Delivered-To: freebsd-questions@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 156BB15077 for ; Fri, 28 May 1999 16:19:43 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id QAA23486; Fri, 28 May 1999 16:19:31 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Fri, 28 May 1999 16:19:31 -0700 (PDT) From: Doug White To: wildcardus freakis Cc: freebsd-questions@FreeBSD.ORG Subject: Re: wonky behavior with NAT In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 28 May 1999, wildcardus freakis wrote: > > Greetz... > > I decided to set up a new NAT machine using 3.1-R, I have two ethernet > cards spaning my inside and outside networks. > xl0 = 206.206.121.3 255.255.255.0 > ep0 = 192.168.241.1 255.255.0.0 > now the wierd thing that seems to be happening is that I can setup tcp > connections to inside machines ( i.e. ping/telnet 192.168.1.1, > 192.168.110.40, etc.) as erll as outside machines (i.e. ping/telnet > 206.206.121.1, 206.206.121.42, etc.) but traffic from inside machines is > not passed to the outside (i.e. 192.168.241.2 cannot reach 206.206.121.1 > when using 192.168.241.1 as a gateway) > > I have not run into this problem before, usually nat works > beautifully...anyone have any clues? We have this neat tool, it's called tcpdump, it tends to make problems like this painfully obvious :-) You probably have a busted firewall rule. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message