Date: Fri, 19 Jan 2001 02:27:45 -0800 (PST) From: Gordon Tetlow <gordont@bluemtn.net> To: Ian Kallen <spidaman@arachna.com> Cc: <freebsd-hackers@freebsd.org> Subject: Re: accessing an outside IP from inside a NAT net Message-ID: <Pine.BSF.4.31.0101190223190.3187-100000@sdmail0.sd.bmarts.com> In-Reply-To: <Pine.BSF.4.10.10101190014250.50099-100000@along-came-a-spider.arachna.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 19 Jan 2001, Ian Kallen wrote: > Now if the DNS for the web server www.foo.com running on 10.0.0.128 > directs a browser on the 10.0.0.0 net to 206.169.18.10, it doesn't get > routed back to 10.0.0.128; it just hangs (I'm acutally not sure what's > happening there, the connction never succeeds). Is there a nice way to > handle this case without running a dummy DNS just for the 10.0.0.0 > internal net? What's happening is the webserver (10.0.0.128) gets the request but is talking directly back to the requesting machine (assuming they are on the same subnet) when the requesting machine is expecting a reply from your ext_ip. They only easy way I see how to do this is to split your internal net into mulitple subnets so that your client machines are one and your servers are on another. -gordon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" 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.31.0101190223190.3187-100000>