jwdv22
join:2008-01-15
Phoenixville, PA
 ·Verizon FIOS
1 edit | reply to Psyclone
Re: FIOS TV Central website access with Non AT Router?
said by Psyclone  : By following the FAQ that I linked Can you link again, so I can follow it. I can't seem to find your link. Thank you.
***EDIT NEVERMIND***** |
|
flashcore
join:2007-01-23
Lutherville Timonium, MD
1 edit | reply to Psyclone
I just figured I would debunk a lot of the theories in here.
First I am having the exact same problem as Psyclone, I am using a DLink DGL-4500 along with a NIM instead of the Actiontec and the website can not see my box's DVR data. The guide, streaming to other STB's and VOD work fine, in fact the VOD actually works better then with the actiontec.
I am using the cloned MAC address from my original Actiontec so Verizon would not know my router is not the Actiontec.
All of my STB's are in the 192.168.1.100-192.168.1.150 range set from my windows 2008 DHCP server using static lease's so they always get the same IP's, the Multiroom DVR gets 192.168.1.100 every time.
I suspect this problem has more to do with some feature on the Actiontec that allows certain traffic or specific verizon IP's to bypass the firewall completely to communicate with the box's (I have not confirmed this yet but I suspect that is what is going on). I have not had time to mess with it yet however I plan on mirroring the switch port I have my NIM hooked to and using wireshark to try and find out exactly where the box's are connecting to for the guide and vod data. Maybe with that information I can narrow down exactly what rules need to be on a 3rd party router to enable the website features. |
|
More Fiber
Premium,MVM
join:2005-09-26
West Chester, PA
 ·Bay Area Internet ..
| On VZ TV Central, I can see my boxes that have been activated, but nothing else, however, I'm not on IMG 1.6 yet.
The Actiontec returns specific information to the STBs as part of their DHCP lease information (DHCP option code 60), whether this is related to the web access to the DVR, I haven't positively confirmed yet.
My last post to Psyclone ] was to help get his configuration working as intended, since he stated he was not pulling a WAN DHCP address on the Buffalo. I have not said that would fix the problem seeing the DVR data from VZ TV Central.
Any insight you have to the problem is welcome. |
|
Psyclone
join:2002-09-29
Beaverton, OR
4 edits | reply to More Fiber
said by More Fiber :said by Psyclone :I don't know who authored the FAQ but it seems that it needs some tweaking. Step 12 for example says to 'Set your new router gateway address to 192.168.1.1' I assume this to mean to set your non Actiontec router's gateway to this ip address. I did this and it caused me to not be able to pull an IP address from the WAN. The FAQ was authored by birdfeedr . I reviewed and edited the FAQ. There is a feedback link on the FAQ page. Step 12 as currently written: 12. Log in to your new router to verify and change any settings. Make sure you change your router password off the default value. Set your new router gateway address to 192.168.1.1, subnet 255.255.255.0. Also set it to distribute DHCP addresses in the range from 192.168.1.100 to 192.168.1.199. You can use the lower addresses for static IPs. Reboot router and PC if you made any changes. I've revised the wording as follows to clarify: In your your new router DHCP Server settings set the gateway address to 192.168.1.1, subnet 255.255.255.0.which means that you need to set the gateway IP address and subnet that the Buffalo will distribute to it's clients. This does not mean the Buffalo's WAN IP address. Clients that request DHCP addresses from the Buffalo need to receive back that gateway address and subnet mask. If the wording needs to be further clarified, I'm sure birdfeedr would be glad to do so. said by Psyclone :It really doesn't make sense, particularly when previous steps direct you change the Actiontec from it's default of 192.168.1.1 to 192.168.1.2 with no step to change it back to the .1 range. Step 6 instructs you to set the IP address of the Actiontec to 192.168.1.2. This ensures that the IP address of the Actiontec does not conflict with the Buffalo. The Actiontec is still on the 192.168.1.x range. Your statement "no step to change it back to the .1 range" implies that you moved the Actiontec to a different subnet. The Actiontec must be on the same subnet as the Buffalo for MediaShare to work. At no point did the Part 4 FAQ instructions refer to moving the Actiontec If the Buffalo can not pull a WAN IP address, then you have a configuration error or a WAN DHCP lease issue. I recommend doing a hard reset on both routers; follow the instructions from the beginning as written; and verify that everything works before trying to incorporate any customizations. Thanks for clarifying this should help future folks in getting their configuration to work, it's clearer now. As you can tell I thought this was referring to the WAN side of things which is why I stated this didn't make any sense since the WAN gateway would be auto configured
as part of the DHCP process for the Buffalo. At any rate to clarify, I am getting a DHCP(Actually PPOE in my case - semantics  ) address and am not having any issues with connectivity as it pertains to VOD, guide data, or Internet access from any device on my LAN. I do in fact have all devices on the same subnet. Again to clarify:
Buffalo:
WAN config : PPOE - pulling from VZ servers
LAN IP : 192.168.1.1
DHCP server ip range : 192.168.1.2-192.168.1.28
ActionTec:
LAN config : DHCP - pulling IP from Buffalo (statically set at the Buffalo to 192.168.1.26)
DHCP Server : disabled - Not leasing IP's to any networked device
STB's receive IP addresses from the Buffalo, which assigns them 192.168.1.27 and 192.168.1.28
Again, everything works in this configuration. I also want to point out the requirement for the devices to be in the .1.* subnet for VOD and Guide data to work. This is NOT true. I have successfully used the above configuration with everything being in the 0.* subnet and everything(except the VZ Central site) worked. |
|
Psyclone
join:2002-09-29
Beaverton, OR
| reply to flashcore
said by flashcore :I just figured I would debunk a lot of the theories in here. First I am having the exact same problem as Psyclone, I am using a DLink DGL-4500 along with a NIM instead of the Actiontec and the website can not see my box's DVR data. The guide, streaming to other STB's and VOD work fine, in fact the VOD actually works better then with the actiontec. I am using the cloned MAC address from my original Actiontec so Verizon would not know my router is not the Actiontec. All of my STB's are in the 192.168.1.100-192.168.1.150 range set from my windows 2008 DHCP server using static lease's so they always get the same IP's, the Multiroom DVR gets 192.168.1.100 every time. I suspect this problem has more to do with some feature on the Actiontec that allows certain traffic or specific verizon IP's to bypass the firewall completely to communicate with the box's (I have not confirmed this yet but I suspect that is what is going on). I have not had time to mess with it yet however I plan on mirroring the switch port I have my NIM hooked to and using wireshark to try and find out exactly where the box's are connecting to for the guide and vod data. Maybe with that information I can narrow down exactly what rules need to be on a 3rd party router to enable the website features. So I'm not crazy Thanks for taking up the cause flashcore. Like you I found that VOD performance is better on the non ActionTec router. The FF, the initial startup, etc. was noticeably quicker for me. At any rate, whatever you could find out about what's needed to get this all working that'd be great. I'll be willing to help test out configurations, etc., whatver is needed to nail this thing down.
I am going to play with my config a bit more by setting the ActionTec up as the 192.168.1.1 device and see if that helps. That's one thing I haven't tried yet. |
|
mwangen
join:2006-10-26
Beaverton, OR
| Let me chime in here. I'm having the same problem as flashcore and psyclone. I'm running an IPCop linux firewall as my main router getting an IP from Verizon via DHCP. The ActionTech is connected LAN-LAN and in the same subnet. Like flashcore I'm using static IPs for the STBs so they always get IPs in the 192.168.1.100 and up range. Like flashcore my IPCop uses a cloned MAC address from the ActionTech. Everything works fine (VOD, Guide, streaming in-between STBs, Media Manager streaming from PC to DVR etc.) but the darn Remote DVR function. For a short time I hooked everything up to the ActionTech forgetting about running my own router as I wanted to know if the Remote DVR function even works. If the ActionTech is the one and only router the Remote DVR functionality works fine. I used Wireshark to monitor the traffic going through the AcionTech, but I didn't see anything out of the ordinary. I put my IPCop router back in the mix and the Remote DVR function no longer works. I even went as far as port forwarding EVERY port UDP and TCP on my IPCop to the DVR and still the Remote DVR feature doesn't work. If any of you guys find out how to make this work with a 3rd party router please let us know. |
|
More Fiber
Premium,MVM
join:2005-09-26
West Chester, PA
·Bay Area Internet ..
3 edits | reply to Psyclone
said by Psyclone :everything works in this configuration. I also want to point out the requirement for the devices to be in the .1.* subnet for VOD and Guide data to work. This is NOT true. I have successfully used the above configuration with everything being in the 0.* subnet and everything(except the VZ Central site) worked. You're correct, any subnet will work, as long as all media sharing devices are on that subnet. I don't believe the FAQ states that use of the 1.x subnet is required. We had to pick a subnet to use as an example, and that was as good as any.
To Psyclone , flashcore , and mwangen
While I understand that you would prefer to use the DHCP server in your respective primary routers, I would like to ask you to try the following as a test:
•Disable the DHCP server in your primary router.
•Enable the DHCP server in the Actiontec.
•Reboot the STBs (disconnect & reconnect AC)
•Check if you can access the STBs from VZ TV Central.
If this works, we should be able to configure both DHCP servers to be active, each with it's own IP address range, with the Actiontec serving only the STBs. |
|
mwangen
join:2006-10-26
Beaverton, OR
| said by More Fiber :While I understand that you would prefer to use the DHCP server in your respective primary routers, I would like to ask you to try the following as a test: •Disable the DHCP server in your primary router. •Enable the DHCP server in the Actiontec. •Reboot the STBs (disconnect & reconnect AC) •Check if you can access the STBs from VZ TV Central. If this works, we should be able to configure both DHCP servers to be active, each with it's own IP address range, with the Actiontec serving only the STBs. I'll give this a try tomorrow though I'm not sure why this would help. An IP address is an IP address. Why should it matter where it's coming from? Especially when both routers give out the same IP of 192.168.1.100 |
|
More Fiber
Premium,MVM
join:2005-09-26
West Chester, PA
·Bay Area Internet ..
| said by mwangen :I'm not sure why this would help. An IP address is an IP address. Why should it matter where it's coming from? It's not as simple as just an IP address. DHCP is an entire protocol where the client can request specific information and the server can return specific information. For an overview of the DHCP protocol, see this link:
»en.wikipedia.org/wiki/DHCP
There are lots of options. See this link regarding option code 60.
»www.cisco.com/warp/public/109/cn···l#topic1
Most home routers do not have the ability to specify option code 60 information to be returned to the client. As I explained in an earlier post in this thread, the STBs and the Actiontec do indeed exchange option code 60 information.
From what I've seen in the router and in Wireshark, URL information is sent, along with setting QOS in the router.
This may indeed not make any difference, however, IMO, it is worth a try. |
|
Psyclone
join:2002-09-29
Beaverton, OR
| reply to More Fiber
said by More Fiber :said by Psyclone :everything works in this configuration. I also want to point out the requirement for the devices to be in the .1.* subnet for VOD and Guide data to work. This is NOT true. I have successfully used the above configuration with everything being in the 0.* subnet and everything(except the VZ Central site) worked. You're correct, any subnet will work, as long as all media sharing devices are on that subnet. I don't believe the FAQ states that use of the 1.x subnet is required. We had to pick a subnet to use as an example, and that was as good as any.
To Psyclone , flashcore , and mwangen While I understand that you would prefer to use the DHCP server in your respective primary routers, I would like to ask you to try the following as a test: •Disable the DHCP server in your primary router. •Enable the DHCP server in the Actiontec. •Reboot the STBs (disconnect & reconnect AC) •Check if you can access the STBs from VZ TV Central. If this works, we should be able to configure both DHCP servers to be active, each with it's own IP address range, with the Actiontec serving only the STBs. I tried your last suggestion(2 dhcp servers with ActionTec serving only STB) last night and it didn't work. Do you know how I would obtain the Vendor Class ID info? DD-WRT does have a place to enter this information. I'd like to try it and see if it helps. |
|
mwangen
join:2006-10-26
Beaverton, OR
| reply to More Fiber
said by More Fiber :Most home routers do not have the ability to specify option code 60 information to be returned to the client. As I explained in an earlier post in this thread, the STBs and the Actiontec do indeed exchange option code 60 information. IPCop does support DHCP Option 60. What info needs to be provided here? |
|
mwangen
join:2006-10-26
Beaverton, OR | reply to Psyclone
Psyclone a little off topic here, but I find it interesting that you are running PPoE. I'm in Beaverton and I'm getting my IP from Verizon via DHCP. |
|
darcilicious
Cyber Librarian
Premium
join:2001-01-02
Forest Grove, OR
·Verizon FIOS
 ·Comcast
| said by mwangen :Psyclone a little off topic here, but I find it interesting that you are running PPoE. I'm in Beaverton and I'm getting my IP from Verizon via DHCP. Verizon has never deployed PPoE for exGTE areas (that I'm aware of), and definitely never in Oregon -- not for DSL and not for FiOS. |
|
mwangen
join:2006-10-26
Beaverton, OR
| reply to Psyclone
Well I'm glad we have this thread going. I spent a few hours trying to get the Remote DVR feature working a few weekends back and basically gave up after running Wireshark and not being able to see anything that would cause this not to work with a 3rd party router. I figured sooner or later someone would start a thread and ppl that are much smarter than me in the network arena would figure this out =) So come on guys what's the problem  |
|
Psyclone
join:2002-09-29
Beaverton, OR
2 edits | reply to darcilicious
said by darcilicious :said by mwangen :Psyclone a little off topic here, but I find it interesting that you are running PPoE. I'm in Beaverton and I'm getting my IP from Verizon via DHCP. Verizon has never deployed PPoE for exGTE areas (that I'm aware of), and definitely never in Oregon -- not for DSL and not for FiOS. *shrug* I have been a Verizon customer for 7-8 years now. I started with 3rd party DSL leasing a line from Verizon. It was PPoE then. After about 2 years I made the switch to Verizon as my ISP to a full Verizon DSL package. Subsequently I upgraded to FIOS Internet and most recently FIOS TV. I am not sure why I'm not on DHCP. |
|
darcilicious
Cyber Librarian
Premium
join:2001-01-02
Forest Grove, OR
·Verizon FIOS
·Comcast
| said by Psyclone :said by darcilicious :said by mwangen :Psyclone a little off topic here, but I find it interesting that you are running PPoE. I'm in Beaverton and I'm getting my IP from Verizon via DHCP. Verizon has never deployed PPoE for exGTE areas (that I'm aware of), and definitely never in Oregon -- not for DSL and not for FiOS. *shrug* I have been a Verizon customer for 6-7 years now. I started with 3rd party DSL leasing a line from Verizon. It was PPoE then and has never been changed. I am not sure why I'm not on DHCP. Wow, that really is odd. I was using GTE/ISDN before it became Verizon -- perhaps there was a sliver of time when they configured some COs with PPPoE for some customers. The vast majority of folks in exGTE don't have it, that's for sure. |
|
Hooper
Premium
join:2001-10-22
Villanova, PA
1 edit | reply to Psyclone
My guess is that there is some code in the Actiontec that registers your STB's with the Verizon Central website. Same way when you call in and the FSC reps can see the boxes. If you are using your own router or even their DLink, they can't see them. I hate to break the news, but Verizon Central will probably never work without the actiontec as the lead router. |
|
Psyclone
join:2002-09-29
Beaverton, OR
| reply to mwangen
I think the Vendor Class ID needs to be set to IP-STB, this according to page 46 of the ActionTec manual. I also found info alluding to this on another BBR post here |
|
Hooper
Premium
join:2001-10-22
Villanova, PA
| said by Psyclone :I think the Vendor Class ID needs to be set to IP-STB, this according to page 46 of the ActionTec manual. I also found info alluding to this on another BBR post here That DHCP option is for QoS and nothing else. Forget it even exists. |
|
mwangen
join:2006-10-26
Beaverton, OR
| reply to Hooper
said by Hooper :My guess is that there is some code in the Actiontec that registers your STB's with the Verizon Central website. Same way when you call in and the FSC reps can see the boxes. If you are using your own router or even their DLink, they can't see them. I hate to break the news, but Verizon Central will probably never work without the actiontec as the lead router. I'm not saying you're wrong here, but I certainly didn't see anything of that sort when I monitored my network traffic using Wireshark. |
|
