On 09/09/2016 07:13 AM, James Knott wrote:
On 09/08/2016 12:10 PM, Greg Freemyer wrote:
Method 1: Cheap or not, the router only has one port 22. But most routers can map inbound ports to any random IP:port on the private side of the router. So:
port 2222 => IP1:22 port 2223 => IP2:22 port 2224 => IP3:22 etc.
Then on the client side you just specify the alternate port used on the router (2222, 2223, 2224, ....)
The problem with that is URLs don't support port numbers, so you're stuck with specifying non-standard ports on the command line.
I think that you have worded that in an ambiguous way, James. Firstly, if I'm using SSH then I can configure my .ssh/config to accommodate that I can, for example have Host server1.antonaylward.com User git Port 2233 Cipher blowfish Hostname mainserver.antonaylward.com IdentityFile ~/.ssh/id_rsa TCPKeepAlive yes IdentitiesOnly yes Host server2.antonaylward.com User git Port 3332 Cipher aes128-cbc Hostname mainserver.antonaylward.com and so on for server3, server4. I realise that this is specific, internal to SSH and not general, not something that can be posted on Firefox for an alternative address for the HTTP server. Which leads to the second case to deal with your ambiguity I *CAN* specify on the command line a port and URL firefox website.antonaylward.com:8080 No, the port number not, as in the ssh config example, 'embedded' in the URL. But it is on the command line. PLEASE NOTE: THE ADDRESSES I'VE USED AS EXAMPLES DO NOT EXIT. They are used for illustration purposes only. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org