Fixing Wi-Fi upload issues with a Sonic.net ZXV10 W300 modem/router
I have Sonic.net for my ISP here in Oakland, and I’ve been pretty happy with the speed and consistency of the DSL service they provide. After returning from my latest visit to the East Coast, however, I discovered I had little to no upload bandwidth on my MacBook Pro. Trying various test sites yielded download speeds in the 12-14Mbps range, but the upload timed out on all of them. I was unable to send a test email from Apple Mail. If I plugged my MBP directly into the ZXV10 W300 modem/router combo that Sonic.net uses, everything worked fine, including standard upload speeds of 1Mbps (that’s why I’m only pretty happy with Sonic.net, by the way–I could really go for a slightly faster upload speed). I also noticed that in the Status menu of the router configuration page, there were a lot of Rx and Tx errors under the Wireless tab, which just didn’t seem good.
A few different things I tried didn’t help:
- Checked and re-configured the modem according to the Sonic.net wiki (I changed the ‘Bridged’ setting to ‘Enabled’ as it was ‘Disabled’, no effect)
- Restarted the modem
- Restarted the MBP
- Changed the channel on the WLAN from ‘Auto’ to 7, 8, and 11 in case someone had a router hard-coded to channel 1 (my auto-selected channel)
- Put the MBP really, really close to the router
Here’s what did work:
- Log in to the router config page (type 192.168.1.1 into your browser URL bar, default username/password are both admin)
- Go to Interface Setup -> Wireless
- In the Multiple SSIDs Settings section, Authentication Type was set to WPA-PSK/WPA2-PSK
- The menu item directly below that, Encryption, was set to TKIP. When I pulled that menu down, the options available were TKIP and AES.
- I switched the Authentication Type to Disabled. NB: don’t leave your router set this way, unless you’re in the middle of the woods somewhere
- After re-testing the connection, I was able to upload normally.
- When I went to re-enable authentication, I re-chose WPA-PSK/WPA2-PSK.
- To my surprise, the Encryption pull-down now included the TKIP/AES option, which wasn’t there before. When I chose this option, my connection worked perfectly.
So, what could have caused this? I suspect that somehow the modem configuration got corrupted, or alternately TKIP-only encryption was working fine for a while, but stopped working with my MBP after a recent OS X 10.8 software update (I applied one while out of town). Either way, I don’t really care what broke, as long as I know how to fix it. If it happens again, that’ll point to the router as the culprit for sure, though.