Date: Sat, 26 Jul 2003 11:42:39 +0400 From: Yar Tikhiy <yar@comp.chem.msu.su> To: Jim Durham <durham@jcdurham.com> Cc: freebsd-hackers@freebsd.org Subject: Re: NATD and Address Redirection Message-ID: <20030726074239.GB61353@comp.chem.msu.su> In-Reply-To: <200307251349.38413.durham@jcdurham.com> References: <200307251349.38413.durham@jcdurham.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jul 25, 2003 at 01:49:38PM -0400, Jim Durham wrote: > > The procedure we used was to alias a 2nd public address to the outside > interface and use a redirect_address statement in natd.conf to > redirect connections to the new public IP to the inside machine. Just a remark: If this 2nd public IP is already routed to your gateway, you don't need to add it as an alias for your gateway's outside interface. But you really need to if the latter interface is on a broadcast network and must do ARP to attract packets destined to the 2nd public IP specified to natd. > This doesn't seem to be symmetrical. You can ping the inside machine > from outside using the new address and if you connect outwards from > the inside machine, the outside world sees the connection as coming > form the new public IP. However, a test running VNC server on the > inside machine and connecting from outside does not work. You can > connect to the inside machine and it sees mouse and keyboard, but the > virtual screen does not work. It seems that the connection works > properly redirecting inward but not outward. VNC disconnects in about > a minute. Could you check if TELNET, HTTP, or SSH from the outside world to the inside machine works? The problem may have to do with VNC protocol peculiarities preventing it from working through NAT. (However, the VNC FAQ claims VNC will work through NAT.) -- Yar
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030726074239.GB61353>