<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Pierre,<div class=""><br class=""></div><div class="">does a `xymon 127.0.0.1 “ping”` on the client return the version-number of your xymon server? If it does your client should simply report to 127.0.0.1 and you should be ready to go.</div><div class=""><br class=""></div><div class="">`pulldata` is for situations where the _server_ can reach the client (on port 1984) — “normal” communication is the other way around: the client contacts the server on tcp/1984. The “daemon" for `pulldata` from the server on the client is `msgcache`: That has to be enabled in `clientlaunch.cg`. If the security-policy applies to the client as well.</div><div class="">This does not seem to be the case in your setup.</div><div class=""><br class=""></div><div class="">If you are not already using it: have a look at the excellent `ssh-tunnel`-extension <<a href="https://wiki.xymonton.org/doku.php/addons:ssh_tunnel" class="">https://wiki.xymonton.org/doku.php/addons:ssh_tunnel</a>> for automatic establishing (and monitoring) the ssh-tunnel.</div><div class="">I have an article on ssh-tunnel <<a href="http://www.it-eckert.com/blog/2014/remote-site-monitoring-with-ssh-tunnel/" class="">http://www.it-eckert.com/blog/2014/remote-site-monitoring-with-ssh-tunnel/</a>> and also provide an improved/patched version <<a href="http://www.it-eckert.com/software/patches/ssh-tunnel/" class="">http://www.it-eckert.com/software/patches/ssh-tunnel/</a>>.</div><div class=""><br class=""></div><div class="">If you have more than one client that has to be monitored in a remote location have a look at `xymonproxy` too, more details here <<a href="http://www.it-eckert.com/blog/2014/combine-ssh-tunnel-with-xymonproxy/" class="">http://www.it-eckert.com/blog/2014/combine-ssh-tunnel-with-xymonproxy/</a>>.</div><div class=""><br class=""></div><div class="">Cheers</div><div class="">Thomas</div><div class=""><div><blockquote type="cite" class=""><div class="">On 31 Oct 2017, at 17:37, Pierre L <<a href="mailto:pierre.lapha@gmail.com" class="">pierre.lapha@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Hello,<div class=""><br class=""></div><div class="">I am trying to set up xymonfetch/msgcache with ssh tunnelling (because security does not want to open flows on port 1984).<br class=""><br class=""></div><div class="">I have enabled xymonfetch (in tasks.cfg) and added pulldata (in hosts.cfg) on server side and also msgcache (in clientlaunch.cfg) and <span style="font-size:11pt;line-height:107%;font-family:Calibri,sans-serif" class="">XYMSRV=127.0.0.1</span><span style="font-size:11pt;line-height:107%;font-family:Calibri,sans-serif" class=""> </span><span style="font-style:italic;font-size:11pt;line-height:107%;font-family:Calibri,sans-serif" class="">(</span><span style="line-height:107%;font-family:Calibri,sans-serif" class="">in </span>xymonclient.cfg).</div><div class=""><br class=""></div><div class="">I have done a ssh tunnel (ssh -L 1234:<a href="http://127.0.0.1:1984/" class="">127.0.0.1:1984</a> IP_of_the_client) from the xymon server. My tunnel is ok but xymon logs still show that nothing happens, no pulldata.</div><div class=""><br class=""></div><div class="">Is there something else I should do to enable this function?</div><div class=""><br class=""></div><div class="">Any help would be appreciated. Thank you!</div><div class=""><br class=""></div><div class="">Pierre</div></div>
_______________________________________________<br class="">Xymon mailing list<br class=""><a href="mailto:Xymon@xymon.com" class="">Xymon@xymon.com</a><br class="">http://lists.xymon.com/mailman/listinfo/xymon<br class=""></div></blockquote></div><br class=""></div></body></html>