|
From: Bruno C. <te...@co...> - 2011-07-08 14:31:27
|
> You could configure your munin-node on the home server to create a > SSH reverse port tunneling to the master every time the IP Adress > changes. You would have to use the -R option of the ssh client program > so that the ssh client sets up a remote port forwarding for some port > and configure the munin-master to connect the node through localhost and > that ssh forwared port. > > When the IP Adress changes, the munin-node would have to kill the still > running but now dead ssh-client and start a new one. This can be > accomplished with the autossh program. SSH would have to use private > key/public key authentication without a passphrase (or use ssh-agent to > store the passphrase) for automated connects. > > I am not sure I made my point clear. I have a similar solution, but my > master is at home and my munin-node is the one outside my security > realm. I don't see a reason why it would not work the other way round. > > Hope that helps. > > Bye, > Philipp Dear Philipp many thanks for help and advice. Indeed it works. So briefly, I open on the munin-node a ssh tunnel in reverse mode to the munin-master (see 'man SSH' and option -R for mode details). I completed the config on both to add this new munin-node (here it's a classical Munin configuration). And voila ! Got the data on the munin-master. (note : here indeed it's the munin-master to grab data from the munin-node, not the reverse) Bye, Bruno |