Bester1
Premium
join:2005-03-25
Long Beach, CA
3 edits | reply to SubnetMask
Re: Verizon Fios ONT - Enabling CAT5 Connection Help!
I had the installer activate the ethernet port on the ONT but I still had to argue with the installer to run cat5 even after I specifically asked for a cat5 run when I put in my order. The reason you've seen many posts about "running cat5 yourself" is because Verizon tells installers to not do cat5 if coax is already present to save on installation time unless they get their supervisor's approval first; many people here try to put in the cat5 run beforehand to avoid having to "negotiate" with the installer (who gets caught in the crossfire between Verizon and the customer).
Other than that, there isn't anything special about the wiring part of the process; cat5 from the ONT to the WAN port of your router, then a call to Verizon...just as you were thinking. For sanity's sake, I'd get the Actiontec up and running on cat5, then switch to your own router, get that working, and then finally connect the Actiontec to one of your router's LAN ports and get that working.
There's what I'd do:
1. Save your current Actiontech settings so you can go back to a working configuration.
2. Connect a cat5 cable from the ONT to the WAN port of the Actiontec. I don't know the specifics for your ONT since I have the 612 model.
3. Call Verizon and get the call center rep to switch your ONT data connection to the cat5 port.
4. Once your internet connection is working fine on the Actiontec, enable remote access and change the Broadband (Ethernet) gateway address to your linksys router's IP address.
5. Release the Actiontec IP address lease BEFORE swapping it out for the linksys router.
6. Once ethernet is working on the linksys, plug an ethernet cable from one of its LAN ports to the WAN port of the Actiontec. The Linksys will give the Actiontec an IP address and ethernet access to get the Program Guide and VOD info for the settop boxes.
Once you get the wired connections going, then try the wireless idea, but I'd recommend staying with a wired connection to the Actiontec. |
|
SubnetMask
join:2008-03-11
Fort Wayne, IN | Hey Bester thanks for the help! Much appreciated. I will let you know how it turns out. |
|
nh5
join:2006-01-21
Seaford, NY
| reply to Bester1
I would recommend setting up the actiontec as a bridge instead of double NAT its alot faster and will give you less headaches down the road. There's a guide to doing it somewhere on here also if you plan on Double NAT just make sure to make the actiontec's network 192.168.2.1 and your linksys leave at 192.168.1.1 otherwise you may run into problems like I did when I used to do that. I ditched the linksys though and stuck with the actiontec since vod is not gonna be the same with the linksys in front no matter what you do. |
|
birdfeedr
Premium,MVM
join:2001-08-11
Warwick, RI
 ·Verizon FIOS
| said by nh5  :also if you plan on Double NAT just make sure to make the actiontec's network 192.168.2.1 and your linksys leave at 192.168.1.1 otherwise you may run into problems like I did when I used to do that. I ditched the linksys though and stuck with the actiontec since vod is not gonna be the same with the linksys in front no matter what you do. If all the Actiontech does is feed VOD and Guide data, it should be fine with double NAT. Add HD and/or multiple STBs simultaneously, and maybe you need to bridge. Try it without bridging, first, and get everything going at once to know for sure.
I have a DLink DIR-655 with IP 192.168.0.1 connected to ONT. WAN of Actiontec with IP 192.168.1.1 connected to LAN port on DLink, and it delivers data just fine. I switched off the STB by mistake yesterday morning. Turned it on, and after it rebooted, the Guide data was not available for display at first, but was OK within a minute or so. VOD (SD, not HD) appears unaffected.
I also have a Mac connected by wire to the Actiontec, and don't have problems with speed tests or other performance issues. I only use that one for web browsing and ftp.
If you need to get into serious open ports or VLAN, yes bridge, but for plain vanilla, you don't need to worry. I say this because some people have reported problems with bridging, and it appears there are several variations on the method.
So, as always, YMMV. |
|
