![]() I don't remember the exact model but it was SuperMassive E10000-something. Not too many years ago I worked at a government office that had the biggest and baddest of SonicWall as central firewall. Hope other people have had better experiences but for me this bridge has been burned. As an engineer you never know if you did something wrong or if the firewall is having a tantrum. What I think is the worst is the lack of consistency. The above has happened across multiple deployments now, all different models so it's unlikely I just got a bung unit. Again, a restart is needed to resolve.īuggy firmware - It has happened more than once now where what should be a simple firmware update, bricks one of the devices in an HA pair. It doesn't drop them, it just does nothing. The configuration is correct, packets are arriving at the interface but the XG just decides not to process them. ![]() Reboot needed to resolve and you never know which config you'll end up with. ![]() A reboot fixes it but sometimes on reboot it takes 5 min to come up, sometimes 15 min.Ĭonfiguration disparity - At times, the Web UI configuration will show different values to the CLI. Web Interface/CLI - The web interface is slow and clunky and sometimes just hangs. I don't even know where to start so will just do a brain dump. I've worked with many firewalls over the years and have never come across anything as buggy as Sophos XG.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |