Vyatta Solves Netflix AIP-701 Error

 


A few weeks ago my wife had an issue with Netflix giving her an "AIP-701" error code. It kept telling us any title that we tried to watch was unavailable try again later. My wife called Netflix, and they gave her the usual list of stuff to troubleshoot including rebooting everything, reinstalling the app  and even changing the DNS on our PS3 and router before finally telling her to call Sony because it was our PS3(surprise).

So while my wife was doing an Amazon Prime trial (which I find a little expensive) I decided I would trouble shoot it the Netflix problem. Below are the steps I tried and failed:

1. Rebooting devices (per Netflix instruction) --- FAILED
2. Reinstalled Netflix application (per Netflix instruction) --- FAILED
3. Changing PS3 DNS (per Netflix instruction) --- FAILED
4. Changing Wireless Bridge DNS (Linksys EA2700 -- per Netflix instruction) --- FAILED
5. Changing Vyatta DNS --- FAILED
6. Disabled Vyatta Firewall polices --- FAILED
7. Rolled back recent upgrade of Vyatta OS (VC6.6R1 back to VC6.5) --- FAILED --- updated back to 6.6R1
8. Cleared DNS cache on all devices --- FAILED
9. Tried Netflix on other devices --- FAILED

When I tried it on the other devices and it failed, that's when I realized it was something with the network or a network device and not just my PS3. Below are the steps I used that gave me results:

(1. Tested Netflix from my phone (external network --- Verizon) --- SUCCEEDED
(2. Tested Netflix from my laptop connected directly to my modem --- SUCCEEDED

At that point I realized it was something on my home network between the PS3 (and other devices) and the internet which there are only two physical hops (1 logical/routing); my wireless bridge and my Vyatta router. Next I tried the below with results:

(1. Tested Netflix from my laptop connected directly to one of my Vyatta router interfaces --- SUCCEEDED
(2. Tested Netflix from my laptop connected to my Cisco lab (bypasses Wireless bridge) --- SUCCEEDED

By this point, I pretty much narrowed it down to my wireless bridge. I tested again using wireless and wired connections to the bridge and it failed every time on multiple devices. So I tried to remedy the situation from the wireless bridge standpoint:

(1. Upgraded Linksys EA2700 firmware to latest --- FAILED (this new firmware was also very buggy)
(2. Rolled back firmware to previous --- FAILED

So the issue was not our PS3 nor any DNS settings. It was that Netflix's newest upgrade was not compatible with my wireless bridge's firmware, even after updating which left us in a bit of a dilemma. I have a plan to update my wireless but not now, and I certainly don't plan on doing it because of one application (Netflix) that we pay for that proper support and testing should have been extended for. 

So I added a spare Intel Gigabit NIC to my Vyatta build and set up a new small network (192.168.2.0/28) between my PS3 and my Vyatta Router and now Netflix works flawlessly directly connected to Vyatta, bypassing the Linksys bridge. 

SUMMARY:

1. I saw that there are various UNSOLVED threads on this issue. I would advise people to check there Wireless equipment firmware and try bypassing the device (directly connecting to Modem) if possible to test. I know for some this may be difficult because some may be entirely dependent of a wireless router for internet access or maybe you have a wireless router/modem combo device.
2. The state of American customer service and service providers is at an all-time low and sinking. "Point the Finger" is the motto. It's not just Netflix either; I deal with service providers (ISPs) at work all day and the issue is always on "the customer side of the demarc".    
3. I will not be purchasing any more Linksys equipment. This whole thing actually made me realize how well it DOES NOT work even though this was mostly Netflix's fault. When I upgraded the firmware, it started having some serious isolated issues of its own, which is why I rolled back. Cisco really dropped the ball on Linksys, which is probably why they sold it to Belkin. The next home wireless solution will either be intergrated with my Vyatta router OR an ASUS wireless device, and in my opinion and according to customer opinion, ASUS is excelling in a lot of things right now for private use. Even my Vyatta motherboard is ASUS. 

  
  

New Lab Pics 5-8-13

As promised, below are new pictures of my growing lab. The main focus here is the new AP7900 Switched PDU and the Cyclades ACS32. Enjoy!

Pictured above is my APC7900 to allow enhanced management of power for my rack. The only rack equipment not connected to this unit is my Vyatta internet router which I need to establish VPN to power on and off the rack remotely.

Beneath the switched PDU is my Cyclades ACS32 terminal access server running Linux at the base. The ports (on this model) only light up when a console session to the connected equipment is activated. I made all console (rollover) cables, but I will go into more detail below. But each cable connects from a port on the ACS to a console port on my Cisco routing and switching equipment. But this server isn't just limited to Cisco devices.

The terminal server has 32 ports available for out-of-band access to all of my Cisco devices. I use it in the same manner I did the Ubuntu terminal server except this is much more efficient. I figured 32 ports was great in case one or two stops working and for lab growth (though I doubt I will have up to 32 devices --- but WHO KNOWS!?). As long as the network to my ACS is good, I can access anything in my lab remotely, which is why I did not put the ACS in my lab network. I placed it in my home (production) network so I can easily connect and so that instability in my lab network does not cause issues with me being able to connect. That would defeat the purpose.

The switched PDU and ACS has made life managing my lab a LOT easier.

My rack to-date in its entirety.

This is the web interface for the switched PDU. It's extremely simple to configure and power on and off devices.

This is just a screen capture of myself logged into all of the console ports of my equipment remotely (notice con0) from my laptop.

This is the web interface for the Cyclades ACS32 terminal server... I have to say, this is NOT the most attractive web-gui that I've seen... I mean, gold? Really? I'd rather look at the CLI (that's true in most cases anyway). But it works.

As you can see I use telnet (currently) to access devices through the ACS. I telnet to the device over a different port (other than 23) to access the console port of specific devices. Ex. I access my HQ router by telnetting to 192.168.1.10 over port 7001 (cmd: telnet 192.168.1.10 7001). I use a different port for each device (ex. backbone switch - 192.168.1.10 port 7002).

The ACS also connects using rollover cables. I made my own rollover cables because it was cheaper and I had bulk Cat5E UTP laying around rather than buying expensive adapters.  For those who don't know (because I had to research, to make a rollover cable  you can just use standard CAT5E and the diagram I just posted that I googled above. 

I used the pattern, orange>white-orange>green>white-green>blue>white-blue>brown>white-brown because it was easy but the one above works too. You can actually use any pattern that you want, AS LONG AS IT IS THE SAME - ONLY REVERSED ON THE OTHER SIDE but it's safest to follow a diagram. Again, this cable can only be used to connect to the console port of networking (Cisco) equipment. 

I hope you enjoyed this update. More to come!