Monday, December 15, 2008

XBox 360 & Verizon FiOS Networking adventures

As discussed before, I got a 360. So it was quite a bit of a pain getting this to work with my Verizon FiOS network connection, specially because paying $100 for a wireless adapter is kind of expensive, and my wireless signal's bad. Here's how thing are:

FiOS is the Verizon fiber optic service for internet/cable/TV/phone, etc that supplies my home with information and entertainment. The house is (as most of the houses on the US) wired for coaxial/cable all over, at least on each room.

The fiber optic from FiOS gets home from the street into my garage, where they have a hub which converts it to coaxial. This hub also has an ethernet output, which would be awesome and solve all my problems had the house be wired with ethernet. Anyways, so from this hub coaxial is conected to the house's wiring and that distributes it to the rooms.

My desktop is upstairs, and from the coaxial there's a so-called MoCA converter, which convertes coaxial to ethernet through Verizon's router, an Actiontec MI424WR. This is a wireless router too. So I plug my PC from there and use the wireless on the laptop downstairs and the Wii. Signal's pretty bad, too many walls in between (my house has a weird layout).

So the first thing I though is well, if I can get my DLink DI-524 as a wireless bridge, I can then just plug the 360 (which is downstairs too) directly into it and be done. So I looked at the DD-WRT project, but seems my DLink doesn't have enough on-board ram to be reflashed and reused as a bridge.

Just for kicks sake, I got a WRT54GL router and tried it with dd-wrt, and seems the Verizon router has issues with some routing table being too small. I also tried hooking up both the 54GL and the DLink's WLAN port into to the Verizon's LAN port, but that seems to kill the Verizon router.

After looking over pages and pages of info, I found this pretty useful one. So I would have to get new hardware...

Got on eBay and bought the same Actiontec router from Verizon for $20 bucks. Verizon wanted $150 for a new one. Crazy talk.

So days later I got the router.

So I looked at the previously mentioned report, double checked my equipment matched the diagram from the tutorial, and proceeded. I set the range of IPs for the 'main' router, the one where the 360 was hooked up, to through 49, and set the static ip of the secondary (where the PC is connected) to, and the range of addresses to give from 51 to 99.

I got an IP for my PC of, which sounded good. I could ping the main router (1.1), and the secondary router (1.50). So far, so good!

Then I tried pinging, and... no cookie. Tried ipconfig /renew, tried changing settings and port forwarding for http and https ports in the verizon config for both routers, but still nothing.

So then I looked at my PC's ipconfig, and saw this:

After some fiddling with it (and getting angry), I figured out that the gateway was the issue. So I went ahead and changed my PC's IP to be static ( and forced the gateway to be the main router (

Everything works like a charm.

Not bad for somebody who slept through most of his computer networks classes ;)

1 comment:

Edmundo. said...

I didn't get it for the reason to split up your IP address space. It seems like you "chained" the routers instead of having them in parallel as in the diagram you mention.

Another solution, having the connection I think you have, is to leave the IP address space originally as the main router was, set up the second router to get a dynamic IP address (DHCP), then set the second router to be on some address space of a different range as

So your computer would have an IP address like / 24, with gateway at, and that gateway would have a gateway at, all of this transparent to you and your equipment.

Doing this, you don't need to change any setting on your PC, and in case you decide to connect it directly to the "main"router, it woudl work without changing anything on it.