Editing interface name (alias) on WG M390 crashed the device
Hello,
We have an M390 updated with latest firmware, everything working fine until our director tried to edit the alias name on one of the external interfaces via the webui. He tried to only change the name, no other configuration, IP addresses or anything else, but a few minutes later we noticed network connectivity cease completely.
We tried to connect through the web but couldn't, it seems like that change killed all communication. The lights on the box still indicated activity as normal. There was an error when saving the config (luckily, in this instance) as we power cycled the device and the previous running config was loaded.
We then tried to connect to the device again via web UI and could get in - the interface name was still on the new name and we had no internet. Once we changed back to the old alias name, everything started working again. The next step would be a serial cable but we didn't need to get that far thankfully.
I've never seen a name change break things before - I went through our firewall policies and all other settings but couldn't see anything specifically tied to the name and not an IP address. I did see only the interface alias name listed under Multi-WAN - maybe changing the name broke multi-WAN and caused the issue?
Any advice or guidance would be appreciated,
Thank you
Comments
Assuming that you used the Web UI to make this change, it would appear to be a Web UI bug.
You should be able to do this using WSM Policy Manager without issues.
Consider opening a support case to report this to WG so that they can investigate it.
Thanks Bruce. I'll try again out of hours with WSM.
For anyone else wondering about this one - turns out it indeed is a known UI bug from the last December roundup.
https://techsearch.watchguard.com/KB?type=Known Issues&SFDCID=kA1Vr0000008jXpKAI&lang=en_US
In Fireware 12.11, after you use Fireware Web UI to rename an external interface, the Multi-WAN settings show duplicate entries. You receive an error if you try to rename the interface again.
Workaround - Use WSM Policy Manager as Bruce advised.