On Wed, Dec 29, 2010 at 12:44 AM, Zico <[email protected]> wrote: > > > On Mon, Dec 27, 2010 at 10:48 AM, Arun Khan <[email protected]> wrote: >> >> .... What is the objective i.e. what exactly are you monitoring, by >> putting your Nagios setup in the "cloud"? >> > > By the way, this is a little bit messy!!! Say, I am out of office today... > so.. I cannot monitor my server because, all the time I need to use Nagios > with http://localhost/nagios . Is it possible to make it little bit *open* .. > say for my own purpose??
> What do you suggest? Should I roll out the VPN as the next thing or use a > reverse proxy from the apache on dev.abc.co.bd ?? 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. In your place I would go with option (a). -- Arun Khan _______________________________________________ ILUGC Mailing List: http://www.ae.iitm.ac.in/mailman/listinfo/ilugc
