jhearn
join:2003-01-02
Leesburg, VA
1 edit | reply to John97
Re: FIOS TV Central website access with Non AT Router?
said by John97  : I don't have any DNS entries in my router, the fields are blank. Somewhere in this thread I posted the exact steps I went through to make my setup work. I didn't add any entries for port-forwarding or anything like that. I searched all your posts and nothing shows up, but that's okay, I should be able to get this setup working. I will give it another try next week. |
|
jhearn
join:2003-01-02
Leesburg, VA
| reply to Rattler
said by Rattler :Jack: You also have to make sure that Remote DVR service is enabled in the DVR or it will not respond. Occasionally, V* sends a specific sort of reset that seems to turn off Remote DVR in the STB so you have to check to make sure it's still enabled in the box. Thanks for the info. I'm going to give this another try next week. I have replaced the Verizon Dlink router with a wireless N router from Phantom Technologies which does a great job of filtering the internet for the teens in my house. So I have learned a lot about double NATing, subnets, etc. I can't see any reason this router shouldn't work with remote DVR. I am using connection type DHCP to Verizon and was thinking maybe that was the problem since my original connection a few years back was PPPOE. |
|
Rattler
join:2001-04-13
Havertown, PA
 ·Verizon Online DSL
 ·Verizon FIOS
1 edit | As the V* fates would have it, mine is, AGAIN, not working today. This time, both the website and the DVR say it should be. There seems to be no rhyme or reason to whether it will be working from one day to the next.
My daughter uses the Actionec router and hers always seems to work. I've had mixed results when I reinstall the A/T in my system. I'm beginning to think it may have something to do with goings-on in the CO that services me and not my configuration...
This also coincides with me not currently being able to poll or reset the DVR from the "My TV" page on the Verizon.com site.
--
Never raise your hands to your kids. It leaves your groin unprotected. -- Red Buttons |
|
Churten
@verizon.net
|  reply to Psyclone
Thought I'd share with people my success getting the FIOS TV Central site working, including remote dvr, without having the Actiontec router out front.
Note that this involves some somewhat advanced linux iptables setup, so I'm not sure how useful it is to everyone, but it at least is a starting place.
My Setup:
•FIOS Business With 1 static IP and TV service
•Linux iptables firewall/router connected to ONT on eth0
•Linux firewall connected to my LAN on eth1
•Actiontec WAN port connected to my LAN
•Actiontec providing DHCP address to the STB
My internal network has 10.0.0.x addresses. The firewall's internal is 10.0.0.1, the Actiontec is assigned 10.0.0.251. The Actiontec is also (of course?) configured with the firewall as its default gateway, dns server (I have a dns cache running there), and ntp server (also have an ntp server running).
The firewall is configured to allow all outgoing connections from the LAN, with a standard NAT configuration.
Here's where it gets interesting/complicated. The basic idea is to reroute all incoming traffic from www36.verizon.net (the fios tv server, 198.23.16.154) to the Actiontec router, except for traffic that looks like responses to an http request from the LAN (i.e. me browsing the fios tv website from my LAN).
So, the iptables voodoo to achieve this (note that some things have gobbledygook names since I'm using fwbuilder to generate these rules). I've replaced my public static ip with 9.9.9.9 below.
Part 1: mark incoming packets, except those coming from port 80 (i.e. http return traffic)
itpables -N Cid3810X30282.0 -t mangle
itpables -t mangle -A PREROUTING -i eth0 -s 198.23.16.154 -j Cid3810X30282.0
itpables -t mangle -A Cid3810X30282.0 -p tcp -m tcp --sport 80 -j RETURN
itpables -N In_RULE_12_3 -t mangle
itpables -t mangle -A Cid3810X30282.0 -j In_RULE_12_3
itpables -t mangle -A In_RULE_12_3 -j LOG --log-level info --log-prefix "DVR Mark "
itpables -t mangle -A In_RULE_12_3 -j MARK --set-mark 1
Part 2: Perform DNAT on marked packets to redirect them to the Actiontec router
iptables -t nat -A PREROUTING -s 198.23.16.154 -d 9.9.9.9 -m mark --mark 1 -j DNAT --to -destination 10.0.0.251
Part 3: make sure packets marked packets aren't dropped by other firewall rules/policies (not sure this is necessary)
iptables -N In_RULE_13
iptables -A INPUT -i eth0 -m mark --mark 1 -j In_RULE_13
iptables -A FORWARD -i eth0 -m mark --mark 1 -j In_RULE_13
iptables -A In_RULE_13 -j LOG --log-level info --log-prefix "DVR Accept "
iptables -A In_RULE_13 -j ACCEPT
The log items in the rules above are mostly to help diagnose and monitor this stuff. I don't think the rules in part 3 are actually necessary, since the log entry for them never fires.
If you have a dynamic IP, you can probably avoid the "-d 9.9.9.9" bit by instead using "-i eth0", but I haven't tested that.
With these rules in place, I was able to activate and use the remote dvr through the website without having to call and cajole any tech support :) |
|
John97
Over The Hills And Far Away
Premium
join:2000-11-14
Southampton, PA
| reply to jhearn
said by jhearn :said by John97 : I don't have any DNS entries in my router, the fields are blank. Somewhere in this thread I posted the exact steps I went through to make my setup work. I didn't add any entries for port-forwarding or anything like that. I searched all your posts and nothing shows up, but that's okay, I should be able to get this setup working. I will give it another try next week. Here's my post detailing the steps:
»Re: FIOS TV Central website access with Non AT Router?
BTW, just checked - everything still works.
--
So put me on a highway, and show me a sign.
And take it to the limit one more time... |
|
jhearn
join:2003-01-02
Leesburg, VA
| Thanks! Looks easy enough. I haven't had a chance to do anymore troubleshooting since my last post, but it's on my list on things to do. |
|
Squirrelly
join:2000-10-24
Harrisburg, PA | Anyone using an Apple Airport with the Actiontec care to post there setup? |
|
KewlRobD2
join:2007-01-30
Hawthorne, NY
| reply to Psyclone
Seems this thread went quiet for a while now. My Fios was installed this weekend and I have Coax to the actiontech which is in bridge mode to my DGL-4500. The installation was a nightmare and took two days to complete. They finally completed it on Saturday and Saturday evening I signed up for Remote DVR. Its been over the 48 hour period they say it takes to set it up but I guess given the holiday I should wait a little longer. I was just wondering if there has been any progress made on how to set this up or did the supposed changes Verizon made actually fix the issue. Not sure if the delay in setting up my Remote DVR is holiday related or configuration related. |
|
More Fiber
Premium,MVM
join:2005-09-26
West Chester, PA
·Bay Area Internet ..
| Did you have the Actiontec as the primary router (not bridged) when you enabled the remote DVR?
Several posters have reported success once they did that.
Once the remote DVR is enabled and working with the Actiontec as primary, then try switching router roles.
I would recommend forwarding port 63145 in your router (as primary) to the IP of the MR-DVR.
Also, make sure that your router is set to forward IGMP requests. |
|
gadgetboyj
join:2009-08-25
Staten Island, NY
 ·RoadRunner Cable
·Time Warner Cable
 ·Time Warner VOIP
| said by More Fiber :Also, make sure that your router is set to forward IGMP requests. Where is that on Belkin or most routers? The Port Forwarding I Can do but not sure what IGMP is. |
|
More Fiber
Premium,MVM
join:2005-09-26
West Chester, PA
·Bay Area Internet ..
| said by gadgetboyj :Where is that on Belkin or most routers? Refer to your router documentation.
said by gadgetboyj :Not sure what IGMP is. »en.wikipedia.org/wiki/IGMP
Also see this specific post earlier in this thread:
»Re: FIOS TV Central website access with Non AT Router? |
|
Zero
join:2009-07-01
Collegeville, PA
| reply to Psyclone
To be honest, I have not gone through this entire thread but I thought that I'd share my configuration and experience getting Remote DVR to work.
I want to note that in the FiOS FAQ, my configuration is a combination of both networking configurations #6 and #7:
#6 ONT -> CAT6 -> WAN DGL-4500 -> WAN Actiontec Rev. D
#7 LAN DGL-4500 -> Switch -> LAN Actiontec
The Actiontec is in the DMZ behind the DGL-4500.
I think having both of them is probably excess however it gives the best of both worlds. The Internet light on the Actiontec is green and connected so to a normal user everything is green and looks healthy. The DGL-4500 is the main router so, on the Actiontec, DCHP is off and it's only acting as a Wireless AP (2.4GHz while the 4500 does 5GHz) MoCA bridge, and a Fast Ethernet switch with the leftover 3 ports.
Anyways, after initially activating the Remote DVR function I had gotten an email that it failed and to set the Actiontec as primary router and reset factory defaults then try again. I made no changes and didn't even request to try again but a few days later l got another email saying it was activated. Surely enough after testing it out on the site it works perfectly!
I'm not sure if Verizon changed something in the way that their activation works or if my setup is unique to allow communication between the site and the DVR. Inside the Actiontec it doesn't show any special Verizon port forwarding rule(s) as it does on another FiOS account that I manage where the Actiontec is the sole router.
I don't know what's the deal with things but I hope this info could help someone else out who's still having issues getting Remote DVR to work without the Actiontec as the main router. |
|
jhearn
join:2003-01-02
Leesburg, VA
| said by Zero :To be honest, I have not gone through this entire thread but I thought that I'd share my configuration and experience getting Remote DVR to work. Like you I have been through this thread. My situation is different in that I have a non-verizon router as my primary router, and I use a NIM to provide guide data and VOD to my two HD-DVRs. My connection to the ONT is via ethernet. If I run the DVR diagnostics everything comes up green, and for remote DVR a message that "Listener 1 is started". My connection to Verizon is PPOE, I use Verizon's DNS servers. So I have a hard time understanding, 1. How does verizon know that I am using a non-verizon router? and 2. Why do they care?
I have read in comments in this thread that errors can occur in Verizon's "database" which when cleared up solves problems associated with the remote DVR function. Right now all I get is the email saying I am using a non Verzion router.
My next step will be to call Verizon tech support and ask about the "database" solution. |
|
John97
Over The Hills And Far Away
Premium
join:2000-11-14
Southampton, PA | I'm sorry to hear it's still not working for you. I can't imagine why as you have a similar setup to me, and mine works.
--
So put me on a highway, and show me a sign.
And take it to the limit one more time... |
|
jhearn
join:2003-01-02
Leesburg, VA
| said by John97 :I'm sorry to hear it's still not working for you. I can't imagine why as you have a similar setup to me, and mine works. It's got to be the database problem that's been referred to in this thread. I will be calling tech support, I haven't called because I dread Verizon tech support so much, but maybe it's changed since my last experience. |
|
jmcging
join:2005-08-04
Columbia, MD
| reply to jhearn
said by jhearn :said by Zero :To be honest, I have not gone through this entire thread but I thought that I'd share my configuration and experience getting Remote DVR to work. Like you I have been through this thread. My situation is different in that I have a non-verizon router as my primary router, and I use a NIM to provide guide data and VOD to my two HD-DVRs. My connection to the ONT is via ethernet. If I run the DVR diagnostics everything comes up green, and for remote DVR a message that "Listener 1 is started". My connection to Verizon is PPOE, I use Verizon's DNS servers. So I have a hard time understanding, 1. How does verizon know that I am using a non-verizon router? and 2. Why do they care? I have read in comments in this thread that errors can occur in Verizon's "database" which when cleared up solves problems associated with the remote DVR function. Right now all I get is the email saying I am using a non Verzion router. My next step will be to call Verizon tech support and ask about the "database" solution. You describe me (except I have 3 DVRs) when you described yourself (I have a dlink dir-655) and I ask you to please keep us approsed of your findings, as I too have been puting off the phone call. |
|
oiler_head
join:2009-09-19
| reply to Psyclone
I thought I, too would share my configuration as I just got TV Central to work.
STB: 192.168.1.100 connected to
Westfall FIOS Router: 192.168.1.49 connected to
Linksys Router (running tomatovpn): 192.168.1.1 connected to
ONT (Ethernet)
I followed the LAN-LAN (option4) process of setting up my stuff.
I read through this thread over the past couple of days and got to page 11 and things are now working. I have mostly followed everything in this thread and and can't say that any one thing put it over the top so it must be a combination of it all.
on my linksys:
forward TCP/UDP for 63145 and 4567 to the STB.
enable NAT-PNP (no particular reason)
On Westfall:
ensured that DNS points to Linksys (on linksys I am using opendns servers)
Verified through self diagnostics that all is well (Help->SelfDiagnostics)
I have confirmed that both remote dvr and mobile access works. No particular thing worked until I enable mobile access. I wonder if there is something that turned the listner on the stb.
Just in case this all dies, I saved out the configs for both routers.
Wish I could be more help but for all the non-networking geeks out there, there is hope. I think the problem that most people are having revolves around configuration. Perhaps the solutino is through everything at it including the kitchen sink (mobile access?). |
|
jhearn
join:2003-01-02
Leesburg, VA
1 edit | said by oiler_head :Wish I could be more help but for all the non-networking geeks out there, there is hope. I think the problem that most people are having revolves around configuration. Perhaps the solutino is through everything at it including the kitchen sink (mobile access?). I was hoping maybe the mobile access would get me working. But the DVR menu tells me that my STB does not support FoG. Anyone know what FoG is? |
|
oiler_head
join:2009-09-19
| I took a quick search and it looks like it may have to do with home media dvr versus "regular" dvr. Does that apply to you?
Is there anything drastically different between what you have setup and my configuration? Have you checked the self diagnostics? |
|
jhearn
join:2003-01-02
Leesburg, VA
| said by oiler_head :I took a quick search and it looks like it may have to do with home media dvr versus "regular" dvr. Does that apply to you? Looks like that may the answer. I just read a blog entry describing the same FoG message was due to not have the Home Media DVR. Now I wonder if that is why I can't get the Web Access function to work? I'll search around. |
|
