Date: Fri, 14 Mar 2003 18:52:19 -0500 From: Bill Moran <wmoran@potentialtech.com> To: Matthew Ryan <matt@overdose.com> Cc: dan@slightlystrange.org, freebsd-questions@FreeBSD.ORG Subject: Re: Port Forwarding FreeBSD 4.7_Release Message-ID: <3E726B33.2050807@potentialtech.com> In-Reply-To: <95C9542C-5676-11D7-8E90-0030654886A6@overdose.com> References: <95C9542C-5676-11D7-8E90-0030654886A6@overdose.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Matthew Ryan wrote: > The /etc/rc.conf entry: > > natd_flags="-redirect_port tcp 192.168.1.241:xxxx xxxx" > > was fine since: > > natd_interface="ep0" > > specified the interface. > > All in all I just should have posted the whole of my /etc/rc.conf in the > first place. > > Sorry about that. > > The real irony is that it was working all along!! > > I just didn't know because i was trying to access the service on the > external IP address of my router from an internal IP address. > > When I tried to access it via. my other connection (in effect from > outside) everything worked fine. > > I'm sure that there is some reasonable explanation for this to do with > the way that NAT operates but I can't figure it out. Fact is, natd _only_ redirects from the interface is was told to bind to. I'm not exactly sure why the packets don't route out and back in when you try it from inside, but they don't ;( so you always need to test it from the external interface. -- Bill Moran Potential Technologies http://www.potentialtech.com 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?3E726B33.2050807>