Date: 25 Feb 2003 16:50:03 -0500 From: Lowell Gilbert <freebsd-questions-local@be-well.no-ip.com> To: freebsd-questions@FreeBSD.ORG Subject: Re: Input on solution to temporary routing Message-ID: <4465r8hvxw.fsf@be-well.ilk.org> In-Reply-To: <20030223235029.GB9202@deter.dk> References: <20030223235029.GB9202@deter.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
Morten Grunnet Buhl <no-spam@deter.dk> writes: > > opensesamy 192.168.0.2 ftp > > which would then temporary route outside ftp connections to 192.168.0.2. You could do something like this, but it wouldn't work for more than one inside box at a time. As far as the rest of the world is concerned, there is only one machine in your network (assuming you only have one global IP address). FTP is particularly hard, because it uses multiple TCP connections, and passes the port number for the data connection *inside* the control connection, so it doesn't mix well with packet-filtering firewalls anyway. Unless you really know what you're doing, I'd advise staying away from FTP with this sort of thing. For protocols that stick to a single port, it's easier. For protocols that can use any port, it's easier yet -- but whoever's connecting from the outside needs to know what it is. For example, you could use natd to redirect external port 8001 to the web server of inside host number 1, 8002 to the web server of inside host number 2, and so on. 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?4465r8hvxw.fsf>