Well, the internet connection to my location has been down for the past number of hours. The cause? My ISP (Shaw Cable) decided to change my static IP addresses without telling me. Apparently they missed the fact that my account would be affected when they replaced a router, so I wasn't notified until after the fact.
But wait! It's not that simple. I've spent the past 3 hours working with Tech Support trying to tell them they still have a problem on their end. You see, I can set the new IP addresses, but I cannot access the new gateway at all (via ping). Until that happens, my connection will be down.
The odd thing is that I am getting TCPDump messages to my firewall's console with broadcast messages from the gateway. So for whatever reason, the gateway is rejecting my messages, but knows I'm there. Makes me scratch my head, but also puts the problem squarely on their end of the network.
I'm on hold with another Tier 1 tech who had the good idea to try pinging my addresses. She is getting a response from some IP address that is nowhere near anything I've ever had (and appears to be one of their name servers), with about 30% packet loss. So, again, I think it's safe to say the problem is on their end.
But I know I will be asked at least three or four more times to cycle the power on my cable modem.
This wouldn't be so bad, but I'm eating up my cell phone time on hold. And even once I get all this resolved, I then need to change all the DNS records to point to the new static addresses, and propagate those changes. So, I'm looking at up to 3 days before everyone can access my servers properly. Realistically it'll likely be 3 or 5 hours. But still...
While I can relate to the changes being made on Shaw's end, and even understand them, this is still frustrating. Sometimes I hate technology.