Firewalla does not recognize network names Mash Deco M5
Good morning! I bought Firewalla and added to my main router. I also have a mash network running perfectly well. The MASH network is from the manufacturer TP-Link deco M5.
At first I plugged the Firewalla into the Deco M5, but the 2 remote devices lost the connection making the network unstable. The main Deco M5 was always operant.
So I took the firewalla from the MASH network and plugged it into the main router. Everything's working fine so far, but I can't see the device names coming from the Mash network. The Firewalla only sees traffic and the name of the main equipment Deco M5.
Any alternatives to this problem?
-
We have not personally tested with TP-Link Deco. From what we know, after you have Firewalla running in simple mode, make sure the 'monitor' mode on the satellites are set to off. See following https://help.firewalla.com/hc/en-us/articles/360008005173-About-Mesh-Routers
The reason when your main router working is, you have router within router deployment. When you attach to main router, you are looking at the TP-Link Deco as one device. (via NAT).
So best is connect back Firewalla to the main unit of the Deco and turn off monitoring on the satellite.
-
Unfortunately, I andy encountered this issue. I have the TP-LINK Deco M4. My Firewalla is connected directly to the main Deco router, not the satellite. However, every time Firewalla is on and running, traffic from the devices on the network never show within the TP-LINK app. It may display two or three, but other active devices don't show up at all even though they have internet activity. When shutting Firewalla off, all the wireless devices show up within the TP-LINK app. This becomes an issue when making changes to parental controls within the TP-LINK app, as they do not receive updates. Any suggestions?
-
This is very likely due to how TP-LINK App to track traffic + how firewalla is directing traffic. If device tracking is done via DHCP services + IP, then shouldn't be a problem. From what you have described, it is likely TP-LNK using ARP table, when that happens, it will likely be confused by firewalla simple mode. Nothing really we can do, that's how their software works. Best is just use firewalla to track devices.
-
Would there be any workaround or resolution I can do temporarily? For example, right now Firewalla is setup with simple mode. Should I change it to "DHCP" mode or "Expert" mode to get around this? If not, could there be any future updates to resolve this? I don't mind using Firewalla for all those needs, but options such as Device Priority aren't yet available. Thanks.
-
What you can do is: (in theory it should work)
1. Stop firewalla monitoring. (disable it or change to limited mode)
2. Your device list should become normal ... then assign whatever priority you have
3. turn monitor back on
Or for individual devices
1. devices->[device]-> scroll to the bottom and disable monitoring
2. hopefully you will see that device in the app, then modify its priority
3. turn monitor on
Please sign in to leave a comment.
Comments
6 comments