So doing the above keeps all the media share, guide, etc. functions intact?

Also let me make sure I understand: verizon ONT via coax -->verizon router (set up as DMZ with wireless disabled)-->set top boxes and my own router.
And then I just have to make sure that the DHCP range for the verizon piece does not overlap with that on my own router.
Do I need to do anything special on my own router?

Wow, a bit angry, aren't we ?. I guess since i was the one that mentioned ubiquiti, this rant is directed towards me. Let me start working on a resignation letter to my boss, and who knows maybe a local McDonalds is hiring :)
Anyway, I have no problem admitting my mistakes and i stand corrected on the subject of Fios cable services and moca adapters, i should have figured this one out. However ,i can't agree on anything else you have said. There is a reason why a Verizon router is on a short " DO NOT USE !! " list posted by Control4 tech support. I have actually seen and fixed problems caused by those routers in C4 systems simply by following the steps listed in my first reply.

I've NEVER been able to get Verizon to do this for me. Gave up, ended up doing DMZ, never had a single issue so I stopped worrying about it.

Every step we do in the Verizon router:

1 - change DHCP range from 192.168.1.2-192.168.1.150
2 - go in Connection List, find the Mikrotik router we have plugged into it, click edit, check Static Lease Type, go back in and click it again, set it to 192.168.1.160
3 - go in Firewall, then DMZ Host, check Enable and set the IP to 192.168.1.160

That's basically it. Make sure the Mikrotik gets the .160 IP address and you can basically act like the Verizon router isn't even there.

you can, it is seriously an uphill battle though.

You change anything in a network, you own it. One device, 100 devices. Their router, your router. You own it.

I actually do know networks very well. Just FYI, the only control systems I touch are network dependent. (not to sound cocky, but I'm not working ccp jobs here, you know).

I 100% disagree with you that " it cannot be used to base our systems on, especially if there is an automation system that is entirely network required (TC-C4 etc)." I am happy that you can convince you customer's to purchase one more piece of equipment they don't NEED, but there is no reason you can't use the Verizon router. I stand behind what I said before. If you can't make the ISP router work for what you need, then it's time to re-evaluate.

I don't mean this is any kind of offensive or personal way. I have at least 30 outstanding TC alone in the last year, 98% on verizon routers. SOLID. Truly, I don't care what you use on your jobs or in the field, but I do not like the spread of misinformation. You don't NEED a 3rd party router.

Here's the thing. Your router has two responsibilities. 1. Route packets. 2. Separate Broadcast domains. That's it. A properly configured network with static IP's and switches can continue to function without the need of a router. This means that in essence if your ISP router can do those two things above, then it is doing EXACTLY what it is designed to do.

As a closing note, I have never had an issues getting the ethernet wan turned on from the ONT to the router. Like I said, if you are pulling 75 down it's required. What speeds are your clients on?

Angry? Not one bit. I am passionate about spreading disinformation. As my post repeatedly said, this was not to single out anyone or directed personally. (as I am sure many of you are, I am reading and responding on mobile). I can't remember or tell the OP vs a response post, as RC doesn't have a mobile site. I just said Ubiquiti because it was the first thing that came to mind. I had no idea who said it, and it certainly wasn't directed at you. I had to go back to the first page to even know what you are talking about.


Regarding Control 4:

I rode the control 4 train back in 2006 essentially beta testing for them on their first several hardware revs until their 2.0 software came out. With any of you around back then, you know it was an utter nightmare. That being said, while I recognize that C4 is doing a lot, they are also another big box brand. It's starting to feel a lot like the iTach stuff I see out there. It's hot right now; it's popular, but that doesn't mean it's vested.

Now, I say that having put my time in as lead at Magnolia, but it's hard to take them seriously now when I compare the type of work I do now and the rebranded "geek squad" that is BB everything now. (I wonder how BB will squander McIntosh now as well).

If Verizon routers are on the short list of things that C4 can't work with, then C4 needs to get their act together. You mean I have to change ISP because the way you coded the soft/firm on your equipment can't work on my network. This is why we have the damn TCP/IP stack STANDARD. It's universal. It's ubiquitous. I buy a network device, and it just works for any network.

Then, C4 comes along and expects me to just change everything because they can't hack it. NO THANK YOU. That's like telling me that I bought an NAD receiver, but I can't use it because I have a Samsung TV. Now i have to buy a Sony.

I don't know why you think that a company doing that is OK or normal or acceptable, but it's not. It is simply their shortcomings.

Personally, I don't touch c4 anymore. I don't know what it is about their gear (I am thinking an icmp issues, as this is a big hurdle with tc and verizon) that doesn't work with the verizon router, but they need to get their ducks in a row and fix it. Asking me to change my isp provided equipment because of your programming shortcomings is absolutely crazy to me.

The verizon router works fine. It does exactly what it is supposed to. This is just more stupid hating because you can't have complete control over it. Well, I don't have complete control over when my smart TV takes it's update, unless I pull the ethernet and disable wifi. We aren't always going to own every section and every piece, but it's still custom. Stop making excuses for crappy engineering in control systems.

Again, I am not trying to start anything with the post or directed toward any individual. I feel like I have given way to much to this community just to be trolled out by some people with misinformation. And I am not slamming c4 or bb as a brand or company. I just fundamentally believe that a two router situation is the WRONG solution. Maybe there is a time it might be A solution, but it should not be the goto.

Sorry.

I have not worked in a Verizon area in several years so obviously things have changed. But I had made the call and request several times, sometimes having to work my way through the process of tech support. Like anything, if you need to get it done you pursue until you get what you need.

And the possibility of using a Verizon router up front on one of my systems was not going to happen. No more than a Comcast router running the show. That is one of the dumber things I have read on any of these forums.

I've had Verizon FIOS at home for a number of years and I became very bored with their router. The situation improved over time, but periodically clients would start dropping off the network and I would need to reset the whole crew. The interval between these events stretched out as successive firmware updates seemed to improve the situation, but even three months between resets became boring. Power failures were a blessing because they would reset the system for me. Finally, I followed the FIOS router with another router and these "events" stopped.

For a while I was connecting directly to the ONT, but I found that if I needed Verizon support, most of the support operators could not deal with the situation. Because of a business, there are two ONT's on this house and one of them was failing. In addition to not being able to keep them properly identified, I had constant "we don't support ... " with every call. Eventually, I gave up the direct to ONT connection so that we could deal with the situation. (Actually, it was the business box that failed.)

There seems to be a local network complexity threshold before the LAN gets into trouble. Fortunately, I don't have many customers with FIOS and most of these systems are simple enough that the FIOS router can deal. For the couple of more complicated systems, I use my own router.

Who's the OEM for these Verizon routers? I don't deal too much with Verizon so I really don't know.

If they are anything like Comcast and provide some POS rebranded Netgear consumer device with built-in wifi, you bet your ass I'm putting in a tried and true router to run my automation systems.

Actiontec

Unless the Actiontec is first in line, you wont be able to use remote dvr (dvr management from phone/tablet). There's pages of these discussions over at dslreports.com.

Ive had Fios for 5+ years at home and gave up trying to put my router in front of the VZ one. Being able to manage my DVR is not something I want to lose. I just forward everything I need thru the Actiontec to my preferred router, and leave the Actiontec to serve guide data and VOD to my boxes. I think that Double NATs me, but I have zero problems with connectivity any equipment in my house.

We do the opposite with clients and put our managed router first. We require VPN access to the network, which the Actiontec wont do. They do not seem to miss the remote dvr functionality, but it is not a perfect solution. Ive also done many jobs where there is Fios and never had a problem getting the ONT switched to ethernet. Most installs in our area are Quantum internet so as mentioned above they are already provisioned ethernet from the start, along with a gigabit Actiontec router.

Never looked too much into the DMZ idea but if that would do the trick it would be something we/I would use.

FYI there is a problem with the Fios Actiontec routers where they will not update DYNDNS addresses. Has to do with how Dyn changed their SSL, and the Actiontec routers do not work correctly with it. Its been like that for months, and apparently VZ/Actiontec is in no rush to fix it. So you have to manually put your IP into your host config at DynDns. Not a big deal as VZ rarely if ever changes yor IP address.

Putting your router behind the Actiontec in the DMZ takes care of the VPN issue. VPN to your router through it.

The dyn issue sucks....once you put in your router though you can have that one do the updating.....been doing that for a few months now

Are you freaking kidding me? you mean to tell me that you would put your automation system on a Fios router? You obviously haven't had to support this system yet. C4, URC, RTI, Crestron, if they rely on the network to work then they get my network.



BTW, Springs is a very reliable asset in my world. Sadly, he's no longer a part of this forum. But if m project gets any sort of IP control, or need of IP reliability then he gets called, and sets my system's backbone up properly.


If you would like his info send me a PM.