Starting this week, Facebook for Android stopped working while under my home network. At first I thought it was just an issue with my Access Points, and rebooted. It did not fix the problem, so I went ahead and rebooted my main router running DD-WRT. Still with the same issue, I decided to reboot the U-Verse gateway. Unfortunately nothing seemed to fix the problem.
I never had a chance to figure out why I couldn’t play tracks from Facebook or Spotify Play Button at home. After further research I found out that my DD-WRT flashed router had the “Deny DNS Rebinding” option enabled. Spotify needs to resolve *.spotilocal.com to 127.0.0.1.
In order to resolve it, I added this command to the DD-WRT startup options:
sed -i ‘s/stop-dns-rebind//g’ /tmp/dnsmasq.conf
I was pretty frustrated when I realized that for firing up my new iPad I needed to install iTunes to my desktop. On top of that, I needed to add a credit card number to download a free application from the App Store. I worked it around by generating a one-time number from citicards.
I decided to install Netflix and did not work, even tried resintalling and changing SSIDs. The only way to make it work was by using a backup SSID from the U-Verse router.
After researching I found out that the DNSMasq package from DD-WRT thinks that the connection from Netflix on the iPad looks like a DNS Rebinding attack.
There are a couple of workarounds:
Use a different DNS server in the iPad/iPhone wireless configuration, like the one provided by OpenDNS: 184.108.40.206
Add a startup rule to DD-WRT to stop DNS rebinding:
1 2 3
sed -i -e 's/^stop-dns-rebinding/#&/'/tmp/dnsmasq.conf
I pursued the second workaround as it allowed me to keep the wireless connection “stock”. Netflix is now working properly on my iPad.
Over a year ago I owned a Linksys WRT-54G V4 router configured as the main and a Netgear WNR8348 configured as a repeater bridge. Both running DD-WRT on wireless G. The solution was rock solid.
After several months, I decided to go the N route and got a Trendnet TEW-637AP and sold the Linksys. A very bad move. The Trendnet would not work as a repeater bridge (or client bridge), so I installed it as main router instead. The Netgear WNR8348, then configured as repeater bridge, started dropping packets and lost connectivity consistently.
Later I replaced the Netgear with an Asus RT-N12 and gave it away. I ended up in worse shape as the Asus lost connectivity every 15 minutes when copying large files; Netflix streaming was just impossible. I tried all kinds of configs (N, G, mixed, 20 Mhz, 40 Mhz, different power settings, you name them). It just did not work.
I was frustrated to the point of thinking about running physical cable but did not execute as it was going to be a very challenging task.
Last attempt to migrate to Wireless N:
I decided to give it a try to a pair of Cisco E2000 routers to replace my repeater bridges which got flashed with DD-WRT as soon as they arrived. I was really surprised with the positive results they gave me after transferring ISO files over wireless, to the point that they were maxing out my PC LAN port consistently. The only change I made was to lower the TX rate to 50 mW (default is 70 mW). The main Asus streaming wireless router is configured to serve N Only connection at channel 7 (2.4 Ghz) and Turbo Channel Width (40 Mhz).
Maxing out the LAN port
From now on, I will stick with Cisco or Linksys for my networking needs.
This is how my home network is configured currently: