Right Now, I’m Dial-Up Boy

Last night, around 17:30, my DSL died. I had been using it up until 16:30, and everything was fine. But later, while I had gone out for a bit, it went Tango Uniform. I tried to get it back up before I had to go bowling, but nothing worked. I hoped it would come back up by itself while I was gone, but when I got home around 22:30, it was still dead.

I tried some diagnostics, but couldn’t get it going again. So I called BellSouth to see what was up. I ended up speaking to a guy called “Dave” (I doubt that was his real name, given his accent), until 01:30 this morning. It was not a fun discussion. I was getting a solid DSL light on the DSL modem, which meant that there was a hardware connection between me and the BellSouth network, but the failure was happening when the PPPoE handler in my router tried to login. It just didn’t work. I explained this to “Dave” and then the fun began.

When I mentioned that I had a router, “Dave” asked me the manufacturer. I told him it was a SonicWall, and he immediately told me that I would have to contact SonicWall for support. I told him there was no way this was a problem with the router. This setup had been working flawlessly for over a year. All signs pointed to a problem on their end, but he adamantly denied there was anything wrong over there. I humored him and hooked the DSL modem directly to my Mac, to take the router completely out of the picture. Same results. He did say that he had “reset a few ports” on his end (whatever that meant), but it still didn’t work. “Dave” finally “concluded” that the modem was malfunctioning, and they would have to send me another. Never-mind the fact that the modem’s self-test showed it was OK, that both ports were working, that I had hardware sync to the CO. No, the problem must be the modem. And so, I will be stuck without DSL for 2 or 3 days.

Now, here’s what’s interesting about this whole absurd affair. Three days ago, I put in an order with BellSouth (part of the “New” AT&T) to upgrade my DSL from 3Mbps to 6Mbps. The conversion was supposed to be complete on 01/24, but according to “Dave” it was complete on 01/22. Gee, why does that date sound familiar? Oh, yeah. It’s the same date that my DSL died. I put this question to “Dave”: Doesn’t it seem a bit suspicious to you that my modem up and died on the very same day that you say changes were made to my service on your end? He stumbled over that for a second, and then “confirmed” that the modem was the cause of the problem, and did I want them to ship me a new modem? When I placed the order for the speed upgrade, I asked the person directly: Do I need to switch out the modem and/or will there be any sort of outage for the upgrade? She told me specifically: No, the modem is fine, and you won’t see any outage.

So, where do we stand? I suspect that the modem I had was not capable of handling the increased speed. I can’t verify that, but that’s what I think. Rather than admit that they screwed me by not telling me there would be an outage until I swapped out modems, they cover it up with a story that my modem has just mysteriously died, and they would send me another. For free. Yes, for free. I could be completely wrong on this one. Perhaps when the new one gets here, I’ll hook it up and be back in DSL bliss, but my gut tells me that won’t be the case. I had hoped to test my theory today, by going to Best Buy and buying a 3rd-party DSL modem, but guess what. You can’t. You can buy cable modems all day long, but no DSL modems.

So, here I sit, dressed as Dial-Up Boy, the inferior sidekick to High-Speed DSL Man. My shiny Mac Pro doesn’t have a modem… but my iBook does. So I ran a phone line to the iBook and got a regular PPP dial-up connection to BellSouth established. I then shared the connection, and after figuring out what I needed to do to get routing working, I now have full Internet access from my Mac Pro, via the iBook’s modem connection. I did have some routing problems, but my friend reminded me that I have two Ethernet ports on the Mac Pro, so I hooked one cable directly between the Pro and the iBook, and the other from the Pro to the router. Now packets bound for my LAN go out en1 and packets bound for the Internet go out en0 and get routed through the iBook, to it’s modem, then to BellSouth-land, and then out into the wild. Slowly. But they do get there. Very, very, slowly.

01/24/2007 17:14 Update: The replacement modem arrived today around 16:00. I quickly unpacked it and hooked it directly to my Mac, just to leave the router out of the equation for the moment. As I (mostly) expected, the new modem did exactly what the old one did: not connect. So, I called tech support, this time getting a very friendly woman, supposedly called “Deborah.” Within about 2 minutes, she had determined that there was a problem on their end. She then gasp! consulted a line engineer. Between the two of them, within about 4 minutes they had determined that my line had not been provisioned properly when they “upgraded” me to 6Mbps. They flipped some switches on their said and then BLAMMO! full-speed, 6Mbps DSL, baby!

I knew that I needed to put the modem into “bridge” mode, so that my router could handle the PPPoE stuff, but I wasn’t sure how to bridge it. She walked me through it and after a restart of the modem, I moved my cables around and now all is right with the world.

What this means, of course, is if “Dave” had consulted a line engineer two nights ago, I might not have had to endure two days of dial-up hell. Thus, “Deborah” gets an A+ for support, while “Dave” gets a D.

Mii on Wii

Thanks to my sister and brother-in-law, wii are now the proud owners of a brand new Nintendo Wii system. Shiny! We just got it last night, so I haven’t had too much time to fiddle with it. Thomas and I created a couple of Mii’s and did a bit of bowling.

I also downloaded the Internet Channel, which is a special version of the Opera browser. Of course, the first site I visited with the Wii was my own…

I’ve only played with the unit for a short time, but I’m very impressed. The Wiimote is a very neat controller that makes the games more engaging, especially games like bowling and boxing.

First Mac “Exploit” from MOAB — Yawn…

Yesterday was the start of the Month of Apple Bugs, and I have to say it was a big snooze. The “exploit” supposedly allows a malicious QuickTime “movie” file to run arbitrary code on your Mac. Sounds scary, doesn’t it? Yep. The only problem is you have to really work at it to get the exploit to actually do anything. Supposedly, following this link will demonstrate the exploit and will speak the oh-so-classy message “Happy new year shit bag” using the Mac’s speech synthesizer. Unfortunately, I couldn’t get the exploit to work.

I tried following the link with Firefox and two versions of Safari. In all three cases I got a page with some garbled text on it, but nothing exciting. It’s always funny when someone reveals a supposed “exploit” and includes instructions for “if it doesn’t work for you, then try this.” And that’s what we have here. They have included a Ruby program to generate a file that is just like what you can download, and after running it, you should then “open pwnage.qtl”. I did this, and while QuickTime did open and crash, I didn’t hear the message. To be fair, and to ensure that I didn’t just miss hearing the message, I changed what the “exploit” should try to do. Instead of speaking the message, I changed it to open a terminal window, using “/Applications/Utilities/Terminal.app/Contents/MacOS/Terminal”. Guess what happened. Nothing.

All of this tells me this “exploit” is nothing more than a Mac-hater trying to make people think that Mac’s are “just as vulnerable” as crappy Windows machines.

Let’s see if the rest of the month is as scary and exploitable as yesterday was…