Is it possible to used dimitriK with a tunnel
tonimenen
I have problems to have my diitriK server in same network of my
servers to monitorize, can dimitri work with tunnelling ?
Dimitri
may you, please, give any more details about "tunnelling" ?..
what exactly do you mean?.. - if you suppose to remap any used IP
ports to any other - there is no problem! :-) if you mean to access
via web browser via SSH tunnel - there is no problem either.
But, I have no idea about your "tunnelling" without more details :-)
so, what exactly do you mean?..
Rgds,
-Dimitri
> --
> You received this message because you are subscribed to the Google Groups
> "dim_STAT" group.
> To post to this group, send email to dim...@googlegroups.com.
> To unsubscribe from this group, send email to
> dimstat+u...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/dimstat?hl=en.
>
>
tonimenen
I have dimitrik server in on LAN and my servers to monitor in other
LAN. I suppose client in my servers send the info to my dimitriK
server, but I don´t know which protocol is used to send this stats ?
Is it possible to configure the client to send the info via an tunnel.
I mean monitorized servers and dimiriK server are not visible, thay
need a tunnel to interconnet.
Toni.
On 3 mayo, 20:02, Dimitri <dimitrik...@gmail.com> wrote:
> Hi Toni,
>
> may you, please, give any more details about "tunnelling" ?..
>
> what exactly do you mean?.. - if you suppose to remap any used IP
> ports to any other - there is no problem! :-) if you mean to access
> via web browser via SSH tunnel - there is no problem either.
>
> But, I have no idea about your "tunnelling" without more details :-)
>
> so, what exactly do you mean?..
>
> Rgds,
> -Dimitri
>
Alan Impink
From: tonimenen <toni...@gmail.com>
To: dim_STAT <dim...@googlegroups.com>
Sent: Wed, May 4, 2011 3:25:43 AM
Subject: [dim_STAT] Re: Is it possible to used dimitriK with a tunnel
You received this message because you are subscribed to the Google Groups "dim_STAT" group.
To post to this group, send email to dim...@googlegroups.com.
tonimenen
On 4 mayo, 15:30, Alan Impink <aimp...@yahoo.com> wrote:
> I think I might understand what Toni is asking for. FWIW, here's my $0.02.
>
> The dim_STAT client/server communicates over port 5000 (by default). You can
> setup a tunnel to a remote system with this command (on the dim_STAT server):
>
> ssh -f -N -L 5001:{remoteIP}:5000 user@{middleIP}
>
> {remoteIP} is the server with the dim_STAT client software
> {middleIP} is a server that is visible on both networks
>
> When you configure the collect on the dim_STAT server, use localhost:5001 to get
> data from {remoteIP}. You could do the same for multiple servers, each on a
> different port (5002, 5003, ...)
>
> Alan
>
> ________________________________
> > >http://groups.google.com/group/dimstat?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups
> "dim_STAT" group.
> To post to this group, send email to dim...@googlegroups.com.
> To unsubscribe from this group, send email to
tonimenen
In which file I have to do this configuration ?
>
> The dim_STAT client/server communicates over port 5000 (by default). You can
> setup a tunnel to a remote system with this command (on the dim_STAT server):
>
> ssh -f -N -L 5001:{remoteIP}:5000 user@{middleIP}
>
> {remoteIP} is the server with the dim_STAT client software
> {middleIP} is a server that is visible on both networks
>
> When you configure the collect on the dim_STAT server, use localhost:5001 to get
> data from {remoteIP}. You could do the same for multiple servers, each on a
> different port (5002, 5003, ...)
>
> Alan
>
> ________________________________
> > >http://groups.google.com/group/dimstat?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups
> "dim_STAT" group.
> To post to this group, send email to dim...@googlegroups.com.
> To unsubscribe from this group, send email to
aim...@yahoo.com
Sent via DROID on Verizon Wireless
-----Original message-----
From: tonimenen <toni...@gmail.com>
To: dim_STAT <dim...@googlegroups.com>
Sent: Wed, May 4, 2011 15:15:45 GMT+00:00
Subject: [dim_STAT] Re: Is it possible to used dimitriK with a tunnel
Alan,
In which file I have to do this configuration ?
On 4 mayo, 15:30, Alan Impink wrote:
> I think I might understand what Toni is asking for. FWIW, here's my $0.02.
>
> The dim_STAT client/server communicates over port 5000 (by default). You can
> setup a tunnel to a remote system with this command (on the dim_STAT server):
>
> ssh -f -N -L 5001:{remoteIP}:5000 user@{middleIP}
>
> {remoteIP} is the server with the dim_STAT client software
> {middleIP} is a server that is visible on both networks
>
> When you configure the collect on the dim_STAT server, use localhost:5001 to get
> data from {remoteIP}. You could do the same for multiple servers, each on a
> different port (5002, 5003, ...)
>
> Alan
>
> ________________________________
> From: tonimenen
> To: dim_STAT
> Sent: Wed, May 4, 2011 3:25:43 AM
> Subject: [dim_STAT] Re: Is it possible to used dimitriK with a tunnel
>
> I mean the following ...
>
> I have dimitrik server in on LAN and my servers to monitor in other
> LAN. I suppose client in my servers send the info to my dimitriK
> server, but I don´t know which protocol is used to send this stats ?
> Is it possible to configure the client to send the info via an tunnel.
>
> I mean monitorized servers and dimiriK server are not visible, thay
> need a tunnel to interconnet.
>
> Toni.
>
> On 3 mayo, 20:02, Dimitri wrote:
>
>
>
> > Hi Toni,
>
> > may you, please, give any more details about "tunnelling" ?..
>
> > what exactly do you mean?.. - if you suppose to remap any used IP
> > ports to any other - there is no problem! :-) if you mean to access
> > via web browser via SSH tunnel - there is no problem either.
>
> > But, I have no idea about your "tunnelling" without more details :-)
>
> > so, what exactly do you mean?..
>
> > Rgds,
> > -Dimitri
>
Dimitri
to summarize now what Alan is trying to explain (we're still supposing
you're wanting to use SSH tunnel):
1.) SSH tunnel is possible when you need to access hostA from hostB
via hostC, while hostB cannot "see" hostA directly (different
networks), but from hostC you can "see" both hosts (hostC is connected
to both networks).
if it's so, then continue:
2.) on the hostC you should have SSH "port forwarding" and "gateways"
enabled (otherwise it'll not work), and SSH port open at least for an
access from the hostB
3.) then you have to start a tunnel on hostB via SSH:
$ ssh -g hostC -l username -L portB:hostA:portA cat -
-g --> is enabling an access to this tunnel from hosts other than hostB
-l username --> is the user login name you'll use to connect to hostC
portB --> port number to use on hostB to be forwarder to the portA
on the hostA
"cat -" --> is an infinitive command just to keep tunnel open (I
always do that, others not)
until "ssh" command is not finished the tunnel is remaining alive.
for ex: supposing on the hostA you have a web server running and
listening on the standard port 80, and now you need to access it from
hostB:88 via hostC.
shortly: when in your browser you'll type http://hostB:88 it'll
forward you to the http://hostA:80
all you need is to start a command
$ ssh -g hostC -l logname -L 88:hostA:80 cat -
and then try with your browser ;-))
NOW, come back to dim_STAT (don't know why time to time people are
calling it "dimitrik" - seems because of the hostname :-))
Supposing you have to collect stats from the servers: host1, host2, host3, ...
and your dim_STAT server is not on the same network, but may access
hostB which is having a tunnel to these hosts via hostC (hostB may be
the same host which is running dim_STAT Server as well, but it's
optional).
So far:
1.) check on which port host1, host2, etc. are running their
STAT-service daemon (just check the contents of the
/etc/STATsrv/STAT-service script, and seek for "port") - by default
it's 5000
2.) activate a tunnel to host1, host2, host3, ... from hostB via hostC:
$ ssh -g hostC -l logname -L 5001:host1:5000 -L 5002:host2:5000 -L
5003:host3:5000 ... cat -
in this case it'll keep the following port forwarding:
- hostB:5001 ==> host1:5000
- hostB:5002 ==> host2:5000
- hostB:5003 ==> host3:5000
and so on..
3.) via Web interface on your dim_STAT server declare the new hosts in
the Host List as following:
host1/hostB:5001
host2/hostB:5002
host3/hostB:5003
and so on..
4.) try to start a new collect and see host1, host2, etc. accessible :-))
(well, of course if your tunnel is really working :-))
Rgds,
-Dimitri
tonimenen
All very, very clear !
I am doing to start to work on it !
Toni.