On Wed, Dec 29, 2010 at 12:36 PM, Arun Khan <[email protected]> wrote:
> Your OP described the Nagios server with IP number as 120.x.x.x, I > presumed it was in the cloud. However, from above post it appears you > have these systems in some kind of a DMZ which has a "public" IP > subnet and that you have a functional Nagios setup i.e. you have > figured out your specific problem in your OP. > > http://localhost/nagios will work only when you are logged into > desktop running the Nagios system. From any other desktop you will > have to give the IP/hostname. > > A clear picture of your network topology is extremely essential to > make any suggestion. > > >From the possible solutions you have mentioned: > > (a) Reverse Proxy rule is the quickest solution. > > (b) VPN will give you a lot more flexibility but also require time to > setup and test. > > [ .. ] Thanks Arun for your nice reply. I have tried your option, but now a new problem arises. Though my nagios is running, it`s not listening. here is my output: If it's running it's not listening - z...@monitoring:~$ netstat -atpn | grep LISTEN (No info could be read for "-p": geteuid()=1000 but you should be root.) tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN - tcp 0 0 0.0.0.0:8024 0.0.0.0:* LISTEN - tcp6 0 0 :::22 :::* LISTEN - tcp6 0 0 :::8024 :::* LISTEN - -- Best, Zico _______________________________________________ ILUGC Mailing List: http://www.ae.iitm.ac.in/mailman/listinfo/ilugc
