Anyone who has used a Motorola K1M “KRZR” phone from Verizon Wireless probably noticed how laggy its UI was, especially when doing alot of texting. It got so bad I had to clear my SMS mailboxes and hard-reboot the phone just to keep it usable. Then, when I got my N810 and paired it with my phone over BlueTooth, I noticed the phone doesn’t expose all the BlueTooth functionality it’s supposed to, for example the FTP profile didn’t expose a complete filesystem.

There’s a typically breathless article on SlashDot today about how Verizon cuts the copper lines to your house when they install FiOS, as part of an evil corporate Zionist neocon conspiracy to lock you in to Verizon’s service at the exclusion of all the other telcos who would otherwise service your telecom needs.

Last time, I noted how my Verizon-supplied ActionTec router seemed to flake out after a week or so of heavy use, such that its DNS requests started to fail. I switched my internal router to use OpenDNS instead of the router’s own internal DNS, thinking that would solve the problem.

Perhaps not surprisingly, it didn’t. However, when I awoke this morning to find my router performance sucking again, this time I poked around the logs on the ActionTek router a bit more. I ran across this gem in the security log:

The problem I reported earlier wherein my Verizon-supplied router stops responding to DNS requests has come up again, only this time it’s intermittent failure, not an outage. A couple days ago my roommate bitched that no DNS queries were resolving; at the time I wrote it off as end-user delusion, but I am beginning to suspect it was another instance of this router problem.

Having had FiOS running for less than a week, I’ve hit my first hiccup. This morning I woke up to find that all of my DNS requests were timing out. I had things like Google and GMail in my DNS cache, so those still worked, but attempts to resolve new hostnames were timing out. WTF?

I poked around the Verizon router for a bit, and the only thing untoward in the log was:

daemon.warn cLink: clink1: ioctl(DRV_GET_MY_NODE_INFO) failed, res=-1: Bad address.

The Verizon techs just left, having installed the 30/5 pipe as promised. Speed tests confirmed download speeds in the high-20Mbit/s range, though upload speeds were stuck at 2.5Mbit/s, not the specified 5Mbit/s. However, I ran two simultaneus speed tests to different servers, and both turned in 2.5Mbit/s, so I’m satisfied my pipe is as big as they say.