02-08-2017 03:40 PM
Thanks, Lucas! Any word on when the app will support bridged mode? Also, do you have the "official" support steps available to get it working in the meantime?
Sorry for the delay in response, have been out of the office the last few days. Not sure when the app will fully support it. However I will ask one of our escalation team members to put together a quick guide on setting up bridge mode. Am hesitant to use the word official on it but am happy to share with the community the details of how to get it working for those that really are looking to enable the feature now.
02-24-2017 01:23 PM - edited 02-24-2017 01:25 PM
no - its still there..
See first post in this thread for how to get to it;
04-20-2017 03:24 PM
Here are my current observations as well as why double NAT doesn't work, and issues I'm having with bridge mode.
1. Setup sometimes is pretty bumpy through the app. Recognizing nodes sometimes takes a few tries, and if you are trying to setup each one in the place you hope to place them, you may have to retry the setup for additional nodes within a couple feet of the first one to get them to detect and speak to each other, then move it to the location you prefer it to be.
2. It is frequently not good at penetrating some walls/areas. I have 2 areas in my house, one is my garage and I have placed a node in there which is 20-25 feet from the primary node and through 1 wall. They cant reach each other even if I move one of the nodes with 10-15 feet of the other through 1 wall. I have another upstairs, directly above the main node in my office, and it cannot be reach either. I placed an additional node in my master bedroom, 25 feet down the hall with no obstructions from doorway to doorway, and the office node placed just inside the doorway but still behind the wall by 2 feet and they cannot connect to each other.
3. The double NAT will not work for many situations. I have a VPN router that I use connected to my cable internet so it functions as my router and DHCP server. Velop then has it's own DHCP for anything connected to it. I have a TiVO box that records shows and used for live TV. I have a TiVO mini which connects wirelessly to my network (now through Velop). The TiVO mini connects to the main TiVO over the network and streams live TV or recorded TV from the main box. However with Velop they cannot see eachother over the network, and since Velop is a "user friendly" solution, you do not have access to any way of manually NATting, port forwarding, etc. which means it breaks my ability to use my TiVO.
3. You cannot tune the configuration through any "supported" method. If you want to make changes, like using your main router as the DHCP server for both networks, bridging both networks (to solve solutions like my TiVO issue), or other configuration, you have to jump through hoops and click a hidden link in the browser redirect for the Velop system to get access to these features. And they don't work well at all.
07-10-2017 06:44 AM