<body><script type="text/javascript"> function setAttributeOnload(object, attribute, val) { if(window.addEventListener) { window.addEventListener('load', function(){ object[attribute] = val; }, false); } else { window.attachEvent('onload', function(){ object[attribute] = val; }); } } </script> <div id="navbar-iframe-container"></div> <script type="text/javascript" src="https://apis.google.com/js/platform.js"></script> <script type="text/javascript"> gapi.load("gapi.iframes:gapi.iframes.style.bubble", function() { if (gapi.iframes && gapi.iframes.getContext) { gapi.iframes.getContext().openChild({ url: 'https://www.blogger.com/navbar.g?targetBlogID\x3d16851663\x26blogName\x3dBurton+Speaks\x26publishMode\x3dPUBLISH_MODE_HOSTED\x26navbarType\x3dBLUE\x26layoutType\x3dCLASSIC\x26searchRoot\x3dhttp://www.walkingsaint.com/search\x26blogLocale\x3den_US\x26v\x3d2\x26homepageUrl\x3dhttp://www.walkingsaint.com/\x26vt\x3d-1892815651864643552', where: document.getElementById("navbar-iframe-container"), id: "navbar-iframe" }); } }); </script>

Server Outages and DHCP Woes

Saturday, October 27, 2007
So this humble blog experienced some unintentional downtime yesterday. I woke up and was rather displeased to note an absolute inability to contact my server. Tragically curious. I tried to figure out what happened, which wasn't easy with no feedback from the computer, but eventually realized that I'd been emailed the results of a system update.

First guess? The server is actually running inside VMware virtual machine on top of a host server. I figured the system update had been for the host and had updated the kernel, something VMware doesn't always take kindly to.

However, I finally managed to get my hands on the machine and found the reason for the downtime to be quite simple. Yes, everything was working when I got to it, but for one thing...

So a week or so ago I switched out the wireless router that my server was hiding behind - from a crappy Netgear that would bomb out about once an hour when using the wireless from my MacBook Pro to a used but stable Linksys. The downside of this particular Linksys is that it doesn't do DHCP reservations (thought the Netgear did). Not a big deal, I thought... I figured my computers would request and get the same addresses and it wouldn't be an issue for port fowarding.

I was wrong.

I let them keep their current DHCP addresses but, loathe though I am to do it, I may switch over to static IP addresses should this problem crop up again. We'll see.


Blogger Jake said...

How old is the Linksys? If old enough, you might be able to install dd-wrt on it, which supports DHCP reservations.

4:32 PM, October 28, 2007  
Anonymous Anonymous said...

I ran static IP's for ages on my linksys. Not really a real issue.

4:39 PM, October 29, 2007  

Post a Comment

<< Home



Twitter Updates

My Other Sites

Site Information

Friend Blogs

Awesome Links

Favorite Webcomics

Previous Posts


Powered by Blogger