@FatherMadman wrote:
Once he has completed the things he wants to do I will update the thread to see if it worked or not. My next step is to use a router of my choice as the primary internet device and then put this crappy Actiontec router into bridge mode to support the MoCA equipment. Atleast this way my internet will not go down constantly (I hope) and this will still allow the DVR/STB devices to still not work which I thin is Verizon's master plan.
You don't need to put it in bridge mode.
You can add your router as any subnet other than 192.168.1 and then connect the VZ router as a subordinate i.e. your router lan port -> VZ router wan port.
It's not really necessary, except for caller id on tv, but I would suggest that if you do connect it that way that you forward from your router to the vz router the 3 port ranges that are in the VZ router pf rules maked as verizon services.
That way the verizon router will be completely segregated from the premises network
Also that way you can still test anything that you are testing on the VZ subnet without interfering with your main internet connection via your router.
Hey viafax999 thanks for the info. I will difnitely make note of it and try it out. I am hoping to have time this week after the VZ tech does his stuff if work doesnt kill me like it did last week. Will keep the thread updated. I;m hoping between all the postings on the net by users and maybe by some grace of VZ this gets sorted out rather soon and allow all of us to go back to using our time with things we want to do.
@viafax999 wrote:You don't need to put it in bridge mode.
You can add your router as any subnet other than 192.168.1 and then connect the VZ router as a subordinate i.e. your router lan port -> VZ router wan port.
It's not really necessary, except for caller id on tv, but I would suggest that if you do connect it that way that you forward from your router to the vz router the 3 port ranges that are in the VZ router pf rules maked as verizon services.
That way the verizon router will be completely segregated from the premises network
Also that way you can still test anything that you are testing on the VZ subnet without interfering with your main internet connection via your router.
This will create a "double NAT" situation which is generally frowned upon for networking as it creates latency, can mess up Upnp, could cause remote access issues like remote dvr, etc.
Just as an update. I have been up for 281 hours with no changes to router or cisco stb firmwares. I also did not make any changes to settings in the REV I router. No Upnp or IGMP changes. From my perspective, it really appears that VZ made some change outside of my network. ONT or beyond. Just speculation of course.
FWIW I went into that hidden/orpganed IGMP page last week and re-enabled IGMP proxy. Soon afterwards my router started rebooting again every few hours. I disabled IGMP proxy again and it hasn't rebooted for several days. I can't explain whats going on but for me this setting seems to have solved the problem.
Here's the jump to that hidden page again. All I did was change IGMP Proxy to disabled.
@Chuckh1958 wrote:FWIW I went into that hidden/orpganed IGMP page last week and re-enabled IGMP proxy. Soon afterwards my router started rebooting again every few hours. I disabled IGMP proxy again and it hasn't rebooted for several days. I can't explain whats going on but for me this setting seems to have solved the problem.
Here's the jump to that hidden page again. All I did was change IGMP Proxy to disabled.
https://192.168.1.1/index.cgi?active_page=6059
According to a previous poster, that appears to disable the MRDVR ability though..
@sangs wrote:
According to a previous poster, that appears to disable the MRDVR ability though..
It hasn't for me. I disabled IGMP Proxy on Friday morning and was watching recorded shows on Saturday from a non-dvr STB. FWIW my STBs are all the Cisco ones.
Can't be sure, but it looks like the rebooting issue is centered around my laptop. Unfortunately, it's a work machine and I don't have admin rights to change any adapter settings and, as I've documented here, tweaking the router hasn't helped. Interestingly, the Rev. D never had any problems with it.
@g00py wrote:Can't be sure, but it looks like the rebooting issue is centered around my laptop. Unfortunately, it's a work machine and I don't have admin rights to change any adapter settings and, as I've documented here, tweaking the router hasn't helped. Interestingly, the Rev. D never had any problems with it.
Why do you think it is centered around your laptop?
Process of elimination, basically. Over the past few weeks, I've been testing all my devices to see which might be causing the problem and the router only seems to reboot after I initially connect with the laptop either wirelessly or wired. Reboot seems to happen in the first 5-10 mins. Or, at least, this is what I think is happening. It's a bit hard to determine because I have something like 10 devices on my network.
@g00py wrote:Process of elimination, basically. Over the past few weeks, I've been testing all my devices to see which might be causing the problem and the router only seems to reboot after I initially connect with the laptop either wirelessly or wired. Reboot seems to happen in the first 5-10 mins.
What OS?
Start a new topic or ask questions in the open forum.
