Can Hobbit talk over an ssh tunnel?
I have a client behind a fairly tight firewall that is controlled at a much higher level than me. Getting port 1984 authorized is something that is not going to happen, but port 22 is open going both ways. As user "bb" on the server, or on the client, I can ssh from one system to the other without a password prompt.
Is there a way to convince Hobbit to talk over an ssh tunnel?
Thanks for any assistance. Gar
http://en.wikibooks.org/wiki/System_Monitoring_with_Xymon/Other_Docs/HOW TO#Monitor_Hobbit_clients_in_a_DMZ_using_reverse_SSH_tunnels
Bit biased cos I wrote the script!! Sorry.. It works though
regards,
Padraig Lennon Senior Systems Integration Engineer
Pioneer Investments Management Ltd 5th Floor | 1 Georges Quay Plaza | Georges Quay | Dublin 2 | Rep. of Ireland. Tel. +353 (0)1 480.2081 | Fax. +353 (0)1 480.1111
padraig.lennon at pioneerinvestments.com | www.pioneerinvestments.com
Please consider the environment before printing this e-mail
-----Original Message----- From: Gar Nelson [mailto:Gar.Nelson at noaa.gov] Sent: 13 January 2009 23:19 To: hobbit at hswn.dk Subject: [hobbit] Can Hobbit talk over an ssh tunnel?
I have a client behind a fairly tight firewall that is controlled at a much higher level than me. Getting port 1984 authorized is something that is not going to happen, but port 22 is open going both ways. As user "bb" on the server, or on the client, I can ssh from one system to the other without a password prompt.
Is there a way to convince Hobbit to talk over an ssh tunnel?
Thanks for any assistance. Gar
Thank you. I've got a green "ssh-tunnel" now but still no other data. I'm much closer now. ;)
I think the next problem is that the system behind the firewall is actually two systems in a high availability configuration. While they each have the same name on the outside, depending on if it's the primary, or failed over, they have different names on the inside. When I was searching around I briefly saw some setting where you could tell the hobbit client 'use this name for yourself' but I didn't bookmark the page, and now I'm back to searching for it.
The files in /usr/local/hobbit/client/tmp have the individual machine short name, and /usr/local/hobbit/server/etc/bb-hosts lists the shared machine long name.
Gar
Lennon, Padraig wrote:
http://en.wikibooks.org/wiki/System_Monitoring_with_Xymon/Other_Docs/HOW TO#Monitor_Hobbit_clients_in_a_DMZ_using_reverse_SSH_tunnels
Bit biased cos I wrote the script!! Sorry.. It works though
regards,
Padraig Lennon Senior Systems Integration Engineer
Pioneer Investments Management Ltd 5th Floor | 1 Georges Quay Plaza | Georges Quay | Dublin 2 | Rep. of Ireland. Tel. +353 (0)1 480.2081 | Fax. +353 (0)1 480.1111
padraig.lennon at pioneerinvestments.com | www.pioneerinvestments.com
Please consider the environment before printing this e-mail
-----Original Message----- From: Gar Nelson [mailto:Gar.Nelson at noaa.gov] Sent: 13 January 2009 23:19 To: hobbit at hswn.dk Subject: [hobbit] Can Hobbit talk over an ssh tunnel?
I have a client behind a fairly tight firewall that is controlled at a much higher level than me. Getting port 1984 authorized is something that is not going to happen, but port 22 is open going both ways. As user "bb" on the server, or on the client, I can ssh from one system to the other without a password prompt.
Is there a way to convince Hobbit to talk over an ssh tunnel?
Thanks for any assistance. Gar
Doh! runclient.sh start --hostname=HOSTNAME Nothing like the obvious. All seems to be working fine, now on to some tweeking.
Thanks for the help with the tunneling.
Gar
Gar Nelson wrote:
Thank you. I've got a green "ssh-tunnel" now but still no other data. I'm much closer now. ;)
It's possible and it's working :
http://en.wikibooks.org/wiki/System_Monitoring_with_Xymon/Other_Docs/HOWTO#M...
Regards,
Sam
-----Message d'origine----- De : Gar Nelson [mailto:Gar.Nelson at noaa.gov] Envoyé : mercredi 14 janvier 2009 00:19 À : hobbit at hswn.dk Objet : [hobbit] Can Hobbit talk over an ssh tunnel?
I have a client behind a fairly tight firewall that is controlled at a much higher level than me. Getting port 1984 authorized is something that is not going to happen, but port 22 is open going both ways. As user "bb" on the server, or on the client, I can ssh from one system to the other without a password prompt.
Is there a way to convince Hobbit to talk over an ssh tunnel?
Thanks for any assistance. Gar
Ce message a ete scanne par l'anti-virus du Conseil General du Finistere.
Ce message a ete scanne par l'anti-virus du Conseil General du Finistere.
In <496D2176.7040705 at noaa.gov> Gar Nelson <Gar.Nelson at noaa.gov> writes:
I have a client behind a fairly tight firewall that is controlled at a much higher level than me. Getting port 1984 authorized is something that is not going to happen, but port 22 is open going both ways. As user "bb" on the server, or on the client, I can ssh from one system to the other without a password prompt.
Is there a way to convince Hobbit to talk over an ssh tunnel?
A tunnel with port forwarding would be simple to do. On the client you'd do ssh -L 1984:localhost:1984 MYHOBBITSERVER and then your client should be configured with "BBDISP=127.0.0.1" in hobbitclient.cfg
Regards, Henrik
participants (4)
-
Gar.Nelson@noaa.gov
-
henrik@hswn.dk
-
Padraig.Lennon@pioneerinvestments.com
-
Samuel.RENARD@cg29.fr