Firewalla Blue needs reboot regularly
I have a Firewalla blue (1.966) and has been running fine for many months since I switched to DHCP mode shortly after I bought it. But I noticed recently that all devices will stop working and needs to reboot Firewalla. It happens at random time between every day to once a week.
I have Firewalla in DHCP mode, connected to Google WiFi and with VPN client enabled with a 3rd party VPN provider. But I can eliminate the issue with Google WiFi because I need to reboot Firewalla while reboot Google WiFi has no effect.
I don't recall adding any new device for this to start happening, so I'm not suspecting device related issue. But is there a way to check why is it happening or anything I can do to prevent or minimize it?
-
@BenS
Broadening the network range will likely put more pressure on the Firewalla for sure. The Gold should be able to handle that range, but the blue+, blue, and red is unlikely.
My advice is, if you do not have to, don't increase your network range; the reason is, for every address, firewalla will need to keep track and make sure there isn't anything else on that spot... this scan + record keeping will eat up both CPU and memory.
For example, 192.168.0.0/24 will require 255 scans, but a /21 will require 255*8 = 2040 scans ... (I think only the blue+ and gold can support this)
-
Maybe that's my actual problem then. I hadn't thought this would stretch the firewalla since the number of devices obviously hadn't changed, but I can see I have increased the number of IPs 8-fold if they all need to be looked at all the time.
The Gold looks like a lovely device but alas I can't justify the cost for domestic use when the router I've got has /nearly/ all the functionality I need, so I'll look at going back to a 24 bit mask.
Please sign in to leave a comment.
Comments
32 comments