Can Hobbit talk over an ssh tunnel? 🔗 link

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

user-7738cfcc6ae0@xymon.invalid | www.pioneerinvestments.com

Please consider the environment before printing this e-mail

-----Original Message-----
From: Gar Nelson [mailto:user-28410809031a@xymon.invalid] Sent: 13 January 2009 23:19
To: user-ae9b8668bcde@xymon.invalid
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

-------------- next part --------------


"The information in this e-mail and in any attachments is confidential and intended solely for the attention and use of the named addressee(s). This information may be subject to legal, professional or other privilege and further distribution of it is strictly prohibited without our authority. If you are not the intended recipient, you are not authorised to and must not disclose, copy, distribute, or retain this message or any part of it, and should notify us immediately.

This footnote also confirms that this email has been automatically scanned for the presence of computer viruses, profanities and certain file types."

Pioneer Investment Management Limited.

1 George’s Quay Plaza, George’s Quay, Dublin 2, Ireland. 
Registered in Ireland no. 287793.

It's possible and it's working :

http://en.wikibooks.org/wiki/System_Monitoring_with_Xymon/Other_Docs/HOWTO#Monitor_Hobbit_clients_in_a_DMZ_using_reverse_SSH_tunnels 

Regards, 

Sam

-----Message d'origine-----
De : Gar Nelson [mailto:user-28410809031a@xymon.invalid] 
Envoyé : mercredi 14 janvier 2009 00:19
À : user-ae9b8668bcde@xymon.invalid
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.

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:

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:

In <user-1f9dc718a17d@xymon.invalid> Gar Nelson <user-28410809031a@xymon.invalid> writes:

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