On 08/09/16 20:15, Greg Freemyer wrote:
On Thu, Sep 8, 2016 at 1:44 PM, gumb
wrote: On 08/09/16 19:27, Patrick Shanahan wrote:
Whilst I can't say for certain without logging into the remote router, from what I recall, it was only possible to assign ONE device on the local network to the SSH service. If you try to add another configuration it says you've already set it, and I didn't see a way to add multiple devices under the SSH service.
so either pick another "service" and change the port assigned or make a new service and use the port you want to assign the particular machine.
the "services" the router provides are only name tags for particular ports.
Sorry, I shouldn't be pursuing this particular aspect since it will probably be irrelevant. I hadn't thought about doing it via your 'trick' method. But what a moronic router config if that's what's required.
It's not the routers fault. NAT is the villian. Unfortunately most of us are forced to use NAT on our routers.
If you don't know there are only 4 billion IP4 IP addresses, and that simply isn't enough to satisfy the needs.
NAT was introduced decades ago as a way to make the IPs go further. I don't think anyone actually likes NAT. It is simply a necessary evil.
== how NAT works ==
There are 10's of thousands of ports per IP address. ( 1 - 65535).
But with NAT there is only one public IP address for the site. Think of it like an company phone system from 70 years ago. You had to call the company operator and ask to be connected. In a small company you could ask for "Joe" and get connected. As the company grew, you started having to ask for "Extension 4045", etc.
NAT is the same.
Some small number of the ports have been given well known names (Joe), but most haven't.
One of the well known names is SSHD for port 22.
But there is only one public port 22 for the site (router).
If YOU want to offer 5 different SSH connections into the remote site, then it is YOUR job to decide which 5 port numbers you want to use on the router and add them to the routers services list.
It doesn't matter if your using a basic router or not, that's the way it is (with NAT).
If you were working at a location that didn't use NAT, then each device could have its own IP address. That is like having direct dial to someone's office desk phone.
fyi: NAT is so common that I get confused when I go to a client site that doesn't have it. I can think of 2 of my customers in the last 10 years that didn't use NAT for their office machines.
Greg
Thanks for the explanation. A great analogy! Does that mean that IPv6 solves all these woes, or does it still have to work around some of them for backwards compatibility? I'd been wondering if trying to do all this with IPv6 would be more simple or more complicated. But I think again the remote router throws a rock into the road there because it appears to not support IPv6. At least, there is nothing in the printed manual or configuration that mentions it. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org