Moving at 128kbps
During my last AT&T billing cycle, I exceeded my shared data plan limit and got this warning.

Luckily, my plan has no overage costs (like before), but mobility at 128kbps (G2-speeds) would be unbearable right?
Well, it wasn’t that bad. It was sufferable but tolerable. Of course, jumping onto available wifi was the first priority but otherwise data at 128kbps was doable for a short duration. Instead of upping my data plan up a tier, I’m gonna try another month and see what happens. I’ve tuned my phone to perform less checks and updates while using mobile data, and personally, I’ve been cutting back on frivolous use of my phone when bored.

Next up, a coworker had a TP-Link Nanorouter, the TL-WR802N. This inexpensive, tiny white box is very flexible can can function in many networking scenarios like a traditional wireless router, a hotspot router, a range extender, and as a client (client mode is essentially a wifi bridge). The web interface of the WR802N is very thorough with all the options exposed. It took me an extra try to set up Client mode with a static IP, not the default DHCP setting. But then the WR802N didn’t bridge. I could ping the static IP given to the bridge but could not ping or connect to the bridged device. I tried and tried. I even saw posts online describing similar issues but with a fix in the form of beta firmware. After contacting technical support, I was sent an updated beta firmware the next day. Sadly, this didn’t fix my problem. I’m pretty sure I’m configuring the WR802N correctly also testing DHCP settings and connecting to different wifi networks, but no matter what, I couldn’t connect through the device’s wired Ethernet.







