05-25-2017 09:39 AM
Reverted back - still not working.
Only one velop port is connected to the main router.
Double check that the firmware version listed under the problem node's WebUI is the latest version.
05-25-2017 09:53 AM
05-25-2017 10:17 AM
I'm running out of ideas
AFAIK there are only two users posting this issue. Not much to go on.
05-26-2017 01:20 AM
I have the same problem. 3 nodes and in normal mode Velop use double nat. Wifi dhcp uses 10.1.X.X and in my wired network I use 192.168.X.X so you must use double nat and wired devices have problems to comunicate with wireles devices. In bridge mode Velop devices do not give IP from the DHCP server (router).
I am very unhappy with the Velop system because I have lost a lot of time and it isf rustrating.
I am running out of ideas, so I'm thinking about returning it...
05-26-2017 05:15 AM
Hello, jlmkerr. Allow us to forward your case to our 2nd level Support Team so our Escalation Engineers can work with you and conduct a further diagnosis with this issue. Please e-mail us the following information at LinksysCares@linksys.com so we can create a case for you in our system:
We'll be waiting.
05-26-2017 06:30 PM
06-11-2017 10:30 AM
Exact same problem here.
New 3 node system. Initally set up as "automatic - out of the box" 192.168.1.1 system - worked fine.
All nodes functional and good coverage.
Changed the connection to "bridge mode" and am finding that one or more of the nodes will not provide an IP address.
DHCP server is a Billion BiPAC7800 ADSL router.
Tried resetting all nodes to factory and initializing the parent only in bridge mode - seemed to be ok. Then added children and same issue.
The mesh system seems to work well, but is pretty useless to me unless the bridge mode works as there are many hardwired static devices on my network already that need to be accessed by the mobile wifi connected devices.