Hi Stephan, I'm using Amazon EC2 instances as slaves and want to connect to these slaves via ssh but do not want the world to see port 22 is accessible. So the world just sees port 80. On the internal network I want an ssh-gateway to which I can connect. On the ssh-gateway I just want to issue 'ssh user@hostname_alias' to connect to slave 'hostname_alias'.
Amazons DHCP and hostnaming is unpredictable and not human-readable, that's why I'm jumping through these hoops. Greetings EC2 instances get a different IP and hostname On Sat, Jan 29, 2011 at 12:18 PM, Stefan Schlesinger <s...@ono.at> wrote: > Hey, > >> I'm figuring out a way to build a ssh-gateway. For that to work I want >> access to the internal ipaddresses that are used by my slaves > > What are you trying to do? Are you trying to cluster SSH? > >> (which >> get assigned by dhcp and thus are not predictable). > > You know that DHCP also provides options to make it less random? > You could use dynamic DNS entries, or fixed IPs per MAC address.... > > Regards, Stefan. > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
