Date: Sat, 20 Jan 2001 00:04:29 -0700 (MST) From: Nick Rogness <nick@rapidnet.com> 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.21.0101192358210.45596-100000@rapidnet.com> In-Reply-To: <Pine.BSF.4.10.10101192125530.11924-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: > Well, I've been fiddling with the ipfw syntax, I thought this would do it > /sbin/ipfw add divert 80 all from 10.0.0.128/25 to 206.169.18.10 via ep0 > but that ain't it. > > 10.0.0.128/25 has servers, 10.0.0.0/25 has clients, both gateways > 10.0.0.1 and 10.0.0.129 run off ep0... yes, I've been reading the ipfw man > page and the archives, yet even though the two nets can access each other > directly, I haven't been able to get the clients to access any server > resources via the 206.169.18.10 nat. Further suggestions? I have had this same problem before and have solved it when dealing with setup of a DMZ using FreeBSD. This is actually a pretty tricky ipfw setup to get it to work right (depending on network layout). Let me see if I can give you the details. But first I need a tad more details on how your network is laid out. Are 10.0.0.129 & 10.0.0.1 bound to the same ethernet card? Nick Rogness - Drive defensively. Buy a tank. 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.21.0101192358210.45596-100000>