Modem => Firewalla Gold SE (router mode) => TP-Link Deco XE200 (AP-mode) requires daily restarts

March 14, 2024 15:55
Edited

At least daily, and sometimes more than once a day, my network goes offline, and I have to restart the Gold SE, or modem to restore functionality.

My full setup is as follows:

Modem => Firewalla Gold SE (router mode) => TP-Link Deco XE200 (AP-mode) <- wireless backhaul-> XE200

I am running the FWG-SE in router mode. I did not see XE-200 listed anywhere below. Should I be trying other modes?

https://help.firewalla.com/hc/en-us/articles/360047098773-Router-Compatibility-Simple-and-DHCP-Modem-Legacy

Is there some standardized way to upload+report logs from FWG-SE that could be used for debug?

I used to run my network like so with the same modem and didn't experience nearly the same level of problems as I am now with FWG-SE.

Modem => Ubiquiti UDM SE => UI APs
Modem => XE-200 mesh in router mode

Comments

5 comments

Firewalla

March 14, 2024 20:02
The compatibility article only applies to simple/DHCP mode, and it does not apply to router mode.

For your problem, please look at this article https://help.firewalla.com/hc/en-us/articles/360053534593-How-do-I-debug-network-connectivity-issues first, and identify the problem location first
0

Comment actions Permalink
Alex Mastro

March 14, 2024 21:51

Edited
Thanks
1. cables are good, all the lights are on and blinking at the expected speeds for both the WAN and three LAN ports
2. I am unable to connect via the app when the system is in the failed state. While wifi is on, when the system fails, I get the "Firewalla is offline" dialogue. Disconnecting my phone from wifi and re-opening the app to attempt to connect via Bluetooth I get "Firewalla box is unreachable"
3. When the system is in the failed state, I am unable to ping the box from my machine connected over ethernet LAN to FWG-SE (with wifi turned off)
```
amastro@amastro-mbp ~ % ping fire.walla
ping: cannot resolve fire.walla: Unknown host
```
After unplugging and re-plugging FWG-SW the system comes back up, and I can ping the box over LAN with wifi off. Rebooting FWG-SE only (not the modem or mesh APs) causes wifi and internet access to be restored.
```
amastro@amastro-mbp ~ % ping fire.walla
PING fire.walla (192.168.156.1): 56 data bytes
64 bytes from 192.168.156.1: icmp_seq=0 ttl=64 time=696.069 ms
64 bytes from 192.168.156.1: icmp_seq=1 ttl=64 time=1.005 ms
64 bytes from 192.168.156.1: icmp_seq=2 ttl=64 time=0.688 ms
64 bytes from 192.168.156.1: icmp_seq=3 ttl=64 time=0.868 ms
```
0

Comment actions Permalink
Firewalla

March 14, 2024 23:35
Alex, I am creating a ticket for you. We can take a deeper look at the logs
0

Comment actions Permalink
Firewalla

March 14, 2024 23:47
Can you also double-check if the USB-C power supply used is the supplied by us?
1

Comment actions Permalink
Alex Mastro

March 14, 2024 23:48
Great - thank you! Yes, I am using the included USB-C power supply. I will work with you in the ticket.
0

Comment actions Permalink

Please sign in to leave a comment.

Comments

Didn't find what you were looking for?