Date: Tue, 12 Dec 2000 10:26:07 -0800 (PST) From: Sean Peck <speck@newsindex.com> To: cjclark@alum.mit.edu Cc: David Raistrick <keen@damoe.wireless-isp.net>, Chris Hill <chris@monochrome.org>, freebsd-questions@FreeBSD.ORG Subject: Re: Configuring Gateway/NAT on Freebsd Message-ID: <Pine.BSF.4.10.10012121022470.24582-100000@www.newsindex.com> In-Reply-To: <20001212011217.B96105@149.211.6.64.reflexcom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Yes, I fixed the netmask yesterday and now machines can all see each other.. (172.16.0.1 netmask 0xffffff00) however I still am unable to successfully get OUT from machines behind the gateway/natd box. I want to use the 172.16.0.x space as my network, and have a machine running natd which is at 172.16.0.1 and also at the public IP space be the gateway/natd... The interesting thing I have noticed is traceroutes from machines behind the natd/gateway don't seem to go anywhere when I try to reach public space... just 1 * * * etc... So I am wondering if it is a natd config problem now... what flags etc should I be sending natd on bootup to understand this? Or do I have something else in the network configs mucked? Sean On Tue, 12 Dec 2000, Crist J. Clark wrote: > On Mon, Dec 11, 2000 at 10:37:29AM -0800, Sean Peck wrote: > > This is what netstat -rn returns, can't run ifconfig, not at the box and > > can't root remotely. But this is the entries for the 172 space on this > > box. > > > > 172.16.0.1 0:1:2:34:b:61 UHLW 0 112 lo0 > > 172.16.0.1/32 link#1 UC 0 0 xl0 > ^^ > > Interesting netmask. You just told this host it can only reach its own > address on this interface. What network do you really want to use? > -- > Crist J. Clark cjclark@alum.mit.edu > 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.10.10012121022470.24582-100000>