Gateways created at the console do not apply the naming convention used in the GUI
When you create a gateway in the webgui by setting an interface as static and adding a new gateway it will, by default, create a gateway named 'WANGW' for example.
However if you do the same thing from the console menu the gateway created is named 'GW_WAN'.
That is not normally an issue if, for example, you are changing the WAN interface from DHCP to Static IP. If you are changing an existing static IP however you then create a second gateway.
If WANGW was set as default then the result is no default route as WANGW is now invalid.
Gateways created in the webgui and the console should use the same naming convention to avoid that.
Same gateway naming convention for the console and the WebGUI. Issue #10264