Am 24.10.2015 um 16:58 schrieb Andy Pieters:
Exactly so for Reindl's use scenario, considering 5 hosts all on the same ip address but with different ports, called host1,host2,host3,host4, and host5:Either system-wide in ssh_config, or per user in ~/.ssh/config: # define common settings for all five hosts Host host1 host2 host3 host4 host5 HostName mynatedhost.com <http://mynatedhost.com> # Then match each individually to set the correct port Host host1 Port 8822 Host host2 Port 8823 Host host3 Port 8824 Host host4 Port 8825 Host host5 Port 8826 On 24 October 2015 at 15:17, Andrei Borzenkov <arvidj...@gmail.com <mailto:arvidj...@gmail.com>> wrote: 24.10.2015 16:57, Reindl Harald пишет: Am 24.10.2015 um 15:04 schrieb Lennart Poettering: Well, I am pretty sure using "#" as separator for that is a really untypical syntax. I am not sure it's really such a big improvement supporting such a syntax over simply asking people to put the right statement in ~/.ssh/config... Note thta the stuff in ~/.ssh/config is really powerful as you can actually define wildcards and stuff... but it's pretty useless in cases where you have a dozen virtual machines inside a NAT port forwarded on a router because only a single public IP - in that case you need to define a port for the connection Host in ssh.config is matched against host on command line; inside you can set HostName and Port which define real connection end point. So you may have multiple virtual hosts with different port each referring to the same real IP. i had such a standard VMware NAT with single ports forwarded for many years before i gave up with notebooks and changed my whole IT to two machines connected via VPN's and static routes
signature.asc
Description: OpenPGP digital signature
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
