Date: Fri, 28 May 1999 16:19:31 -0700 (PDT) From: Doug White <dwhite@resnet.uoregon.edu> To: wildcardus freakis <wildcard@dax.belen.k12.nm.us> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: wonky behavior with NAT Message-ID: <Pine.BSF.4.03.9905281619040.11808-100000@resnet.uoregon.edu> In-Reply-To: <Pine.BSF.3.96.990528110016.1348A-100000@dax.belen.k12.nm.us>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.03.9905281619040.11808-100000>