On 09/08/2016 12:05 PM, gumb wrote:
See my reply to jdd. Unfortunately this is a lightweight router provided by the ISP. The model is a Thomson 2704n (apparently it is also known as a Sagemcom 2704N).
You mean this http://setuprouter.com/router/sagemcom/2704n-plusnet/port-forwarding-76546-l... It is, it seems, a very basic NAT'ing router. As I say, low cost for ISPs to provide to basic users. You might want to follow the link and read this http://setuprouter.com/what-is-port-forwarding/
It was a few weeks ago I had a first look at its configuration options, which aren't very extensive. I don't know if it's even possible to change the router's default SSHD port.
You don't need to. You can define any port on the Big-I internet facing side to forward to any static address and port on the inside. As Greg says, you can set up some ports:
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, ....)
It only provides the possibility to select a service such as SSH that I want to allow, then select the (only?) device on the network to which that service is forwarded, along with the port number, which I assumed to mean only the port number on the destination device.
See above. It seems you've just done port 22 => IP1:2222
I have already configured a non-default port number on the sender and receiver devices.
Having the SSH internal devices behind a firewall listening on non standard ports affects local communication. Yes there are ways round that, but lets KISS. I recommend leaving the SSHD of all internal hosts listening on port 22. Its less confusing that way; simplifies maintenance. Do the pokery that Greg suggests. -- 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