cellio | DHCP gone bad

Once upon a time we bought a Linksys router and configured it to hand out IP addresses dynamically. I forget why, but we specified a range of 100-150 for the final byte. (The router itself is 1. Practically speaking we'd never need as many as 50. These might have been defaults; I don't remember.) What this is supposed to mean is that it hands out addresses in order as needed, starting with 100, and if you ever have more than 50 machines on the network you have a problem.

This chugged along fine for a while until it started handing out out-of-range numbers. (No, we have never had so many machines that we exhausted the set range.) We couldn't stop it from giving my machine 192.168.1.2; when it did that my machine couldn't see the internet (presumably because this was out of range). We assigned fixed addresses (in range) to all the resident machines and carried on. I forgot about this until we switched DSL providers recently and found that my network settings were still referring to the old provider. (Once you specify IP address, you also end up specifying DNS servers.) Ok, back to DHCP. We replaced the router a year or two ago, so for all I knew this wasn't even an issue any more.

This morning I couldn't connect to the internet (after a reboot). After the usual diagnostics and quick fixes, I got around to looking at ipconfig. My IP address was, once again, 192.168.1.2. WTF? So this time I decided to change the router; I told it to start handing out addresses with 2 instead of with 100. That didn't fix it. So, finally, I assigned my machine a specific IP address, just like we did before, and it worked.

I still have no idea why this happens. I have a workaround, but the mystery still bugs me.

DHCP gone bad

Re: Got a musical favor to ask you

Re: Got a musical favor to ask you