Helping Daddy Change the Static IPs
Shaw notified us a while ago that we were getting new static IP addresses. This is part of their, “ongoing commitment to proactively manage and upgrade” their internet network. Whatever that means. The old IPs (22.214.171.124 and 126.96.36.199) became inactive around 1AM today. The new IPs (188.8.131.52 and 184.108.40.206) were to become active at 6AM today. This is where Nathaniel became involved. At 5AM our Number One Son and Heir awoke. As happens most early mornings, he wakes up very cheerful. And why wouldn’t he be today? After all, he was going to get to help daddy work on the dmurray.ca network infrastructure. Having received my 5AM wake-up call, I gave him a bottle. I then made myself a cappuccino to kickstart my sleep-deprived brain. We then headed down to the doffice to see whether Shaw was on time. So far, not so good. Forward and reverse DNS are working correctly for wart.dmurray.ca:
dmurray@euler:/home/dmurray 0> dig +short wart.dmurray.ca 220.127.116.11 dmurray@euler:/home/dmurray 0> dig +short -x 18.104.22.168 wart.dmurray.ca. But I’m able to do nothing more than ping the gateway IP (22.214.171.124). I’m able to resolve external hosts, but unable to reach any of them. Hmm. I tried a traceroute on wart.dmurray.ca:
root@wart:~# traceroute shaw.ca traceroute to shaw.ca (126.96.36.199), 30 hops max, 40 byte packets 1 * * * 2 rd1no-ge7-0-0-2.cg.shawcable.net (188.8.131.52) 9.615 ms 9.261 ms 8.978 ms 3 * * * 4 * * * ... 30 * * * Right. The only host that responded was rd1no-ge7-0-0-2.cg.shawcable.net. Time to make a call to tech support. Yuck. Since there wasn’t much else Nathaniel could do, he decided to roll around on the floor. Back to front, front to back, play with toys, play with toes, back to front. He’s getting really good at rolling over. But he’s still not sleeping through the night – up at least once, if not twice.