On Sat, Jan 12, 2008 at 01:23:15PM +0000, Sean Miller wrote: > I wouldn't waste time on this... as I said, just make the router expose your > port 22 on your local server on another port to the internet through port > forwarding. You'll need to also route whatever other ports you want (eg. > port 80) but this would seem a decent solution. > > Then everything works and life suddenly seems so much less complicated. >
It's inelegant. Having a process running on one port but via another route is accessible on a different port looks messy. All you need to do is get all the machines to know what port is in use. No redirection needed. Cheers, Al. -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.kubuntu.org/UKTeam/
