Date: Sat, 18 Jan 2003 14:46:41 -0600 From: listmail@brightstar.ath.cx To: Bill Moran <wmoran@potentialtech.com> Cc: freebsd-questions@FreeBSD.org Subject: Re: Access to internal systems Message-ID: <3E2968D1.16987.814E232B@localhost> In-Reply-To: <3E29AA70.3020504@potentialtech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 18 Jan 2003 at 14:26, Bill Moran wrote: > listmail@brightstar.ath.cx wrote: > > What I'd like to do is be able to get to the internal machine (named > > winmachine1) from the Internet using a construct such as: > > winmachine.bstar.ath.cx. > > > > Any advice? > > You probably have ipfw running on your firewall. You can use ipfw's > port forwarding feature to allow certain ports to appear to be on > bstar.ath.cx, while they are actually connecting to winmachine1. > You simply make a DNS entry that says that winmachine.bstar.ath.cs > is the same as bstar.ath.cs This method (minus the dns server) is what I'm doing now. And you are correct, I want to use similar ports on multiple machines. For the time being, Xinetd's ability to translate port numbers to another machine (ie. bstar port 58 forwards to winmachine as port 80, leaving port 80 free for bstar) works, but will eventually become amazingly cumbersome. I own a domain name and Dyndns will act as domain name servers. Maybe that's the way to go. Thanks, Gene 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?3E2968D1.16987.814E232B>