<div class="gmail_quote">On Mon, Mar 8, 2010 at 2:56 PM, Stuart Browne <span dir="ltr"><<a href="mailto:stuart.browne@ausregistry.com.au">stuart.browne@ausregistry.com.au</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">> -----Original Message-----<br>
> From: <a href="mailto:ravishankar.gundlapali@wipro.com">ravishankar.gundlapali@wipro.com</a><br>
<br>
> I have approached my security team and they have suggested me that they<br>
> can change the IP address of this Linux box and move it to a different<br>
> VLan for some time period where we have internet access, so that I can<br>
> install the required packages and Nagios.<br>
><br>
> After I am done with my work they said that they will move it back and<br>
> change the IP.<br>
><br>
> Can anyone please guide me whether I can follow the above procedure.<br>
<br>
</div>Nagios its self doesn't care what the IP address of the box it's installed on is.<br>
</blockquote></div><br>Indeed. If it makes it easier for everyone and acceptable to your security team, you can even download all your required packages to some other machine already on the Internet (does your company have those?), copy them onto USB or other device, and then copy them to your Nagios box for installation.<br>
<br>If it's this much hassle to get your Nagios box onto the Internet, then doing this "sneaker net" install will be a good practice run for how you'll eventually apply upgrades and install additional packages.<br>
<br>-Mike<br>