Setting up Blue+ with new Velop mesh
My blue+ was running in DHCP mode on my Nighthawk router and extender. I have just replaced the old network with a 2 node Linksys Velop MX8400 (2 AX4200 units with 1 as router and second as child). I have not connected the firewalla to the new network yet.
The firewalla was already set up with wall of my rules, IP reservations and settings. I would like to continue to use DHCP mode.
How do I add to the new mesh? Just plug it in and reboot after turning off DHCP on the Velop?
Has anyone done this?
After reconnecting the Firewalla, I disabled the DHCP on the Velop. Then each of the connected devices needed to reboot or disconnect/reconnect in order to get an IP address assigned by the Firewalla instead of the IP that had been assigned by Velop previously.
Everything seemed to be working but I received a message in the Firewalla app "Disable DHCPv6 on Router. To monitor this WAN network, DHCPv6 service on the router should be disabled."
The Velop admin web page isn't as granular as the Netgear that it replaced. The only place where I see the ability to disable is the IPv6 check box on the internet settings tab as seen in the attached screen grab. Is this what the error message is referring to?
I have disabled the "IPv6" box but the Firewalla is still showing the same message. When I check each attached device, there are no more IPv6 IP addresses.
I have another related question. I don't recall some of the settings while running the Firewalla in DHCP mode with a different mesh system (tested and didn't work well so replaced it).
The Firewalla receives an IP address within the base range of the primary mesh node connected to the cable modem and has DHCP disabled. In this case, the Firewalla's IP address falls within is 192.168.1.x. Should the mesh daughter nodes receive their IP address from the primary mesh node, ie 192.168.1.y OR should the daughter node receive an IP address issued by the Firewalla ie 192.168.184.z?
I'm wondering if I need additional reboots to the modem, primary node, secondary node and Firewalla to get everything sorted out and eliminate the warning message.
The message stayed for a couple of hours, then left for as far as I can tell overnight, then came back for a short while this morning and now it's gone and hasn't come back. I'm on Android 12 on my phone and Android 8 on a tablet but I haven't been using the tablet for a couple of days and didn't see the message there.
Maybe there's a device that is still pulling an Ipv6 address when it's in use? I haven't seen any Ipv6 addresses in the device list of firewalla but some devices show no IP address (maybe devices connected via child mesh unit rather than the base router?
I did some more checking and all of the devices that provide WiFi details have an fexx address in addition to the ip4 address. I tried converting one to ip4 and it was invalid. But the firewalla device list is showing only ip4 addresses.
Ipv6 is turned off in the 2 places where the router admin page provides that option. The Linksys web page and app don't provide a lot of options. It's very consumer oriented.
Would it be better for me to try simple mode and let the router handle DHCP?
Please sign in to leave a comment.