TP-Link Omada - Firewalle Purple - Constant Reconnection

Follow

J

• March 23, 2023 10:38
• Edited

Hi all,

I use the Firewall Purple in Brigde Mode with a TP-Link ER605 router. I have configured four VLANs (see screenshot), which are also monitored correctly.
However, I have now noticed in the router log that the Firewalla box is connected to and disconnected from the individual VLANs nearly every minute ( other screenshot)
I cannot imagine that this is normal.

Does anyone have a tip on where this behaviour comes from and how it could be better?

 

 

 

1

• 

  Firewalla

  • March 23, 2023 16:57

  When in bridge mode, does the firewalla purpel run correctly? (meaning, you see all the traffic, can block things) besides what you see in the logs?

  If above is yes, likely the logging software is buggy, need to talk to them and ask how they test these things.

  0

  Comment actions Permalink
• 

  J

  • March 24, 2023 09:27
  • Edited

  Hi,

  well, it is my first firewalla product, so I would assume everything works as it should on the side of firewalla.

  I can see the traffic from all four VLAN and Ad Blocking, Parental Control etc. is working.

  For me it looks like my router accepts the IP connection of bridge 1, after some minutes bridge 1 is disconnected and bridge 2 ist connected. After some minutes bridge 2 is disconnected and bridge 3 is connected and so on and so forth...

  Also my router only shows one Firewalla IP in the device manager at a time.

  Whats should be the default behavior? Should all four bridge IPs be displayed as connected at the same time?

   

  1

  Comment actions Permalink
• 

  Firewalla

  • March 24, 2023 17:24

  When bridging, Firewalla is fairly transparent. It only grabs one IP to communicate, other than that, on each VLAN there is no IP. Meaning, you are not going to see firewalla grabbing IP from each VLAN

  If everything is operational, likely your router UI may be either buggy, or need to be tuned to reflect waht's going on 

  0

  Comment actions Permalink
• 

  J

  • March 24, 2023 21:06

  Hi, but doesn't Firewalla have to get an IP in each VLAN segment to see the traffic? In the screenshot above you can see that Firewalla gets an IP from each VLAN. Or do I understand something wrong?

  1

  Comment actions Permalink
• 

  drapier

  • November 12, 2023 19:59

  Has this been issue been addressed? I'm experiencing the same thing with our Firewalla purple in bridge mode. In addition to this issue I can only manage firewalla while my device inside the network. Is there some port forwarding that is required to manage firewalla remotely?

  0

  Comment actions Permalink
• 

  Firewalla

  • November 13, 2023 01:18

  is your VLAN's also disconnecting? is your output for disconnection also from tplink app?

  0

  Comment actions Permalink
• 

  drapier

  • December 11, 2023 01:13

  No. The Tplink network and VLANs are connected and working fine. We just can't manage the firewalla from outside the network. It looks the IP to the firewalla is changing all the time. I'm not sure why because I reserved the IP for it with the Tplink config. Is this a TP-Link config issue/bug or something that needs to change on the firewalla side? Thanks

  0

  Comment actions Permalink
• 

  Firewalla

  • December 11, 2023 17:22

  The firewalla unit shouldn't change IP addresses, it is like any of your LAN device, just filter traffic when in bridge mode. 

  Can you check if you are filtering anything on the router side? may be it is blocking firewalla communications. 

  0

  Comment actions Permalink
• 

  drapier

  • December 12, 2023 12:34

  I don't see any filters applied. The list of device clients shows that the Firewalla is in a pending status with an IP assigned to a different VLAN from what device is configured on. I tried to set a fixed ip address and assign it to the correct VLAN but no luck.

  0

  Comment actions Permalink

Please sign in to leave a comment.