USG Flex 200H - Renaming interfaces

It can be done but you must do it at the start remove all references delete Ge# then make new WAN# interface name

It has to be do like this because the interface name links to all routing rules and such yes the USG60 can do all that but its likely a coding nightmare it be like every port is really Ge# per port then you add a interface name WAN1 mapped to Ge1 but you see it as WAN1 this way rules really use Ge1.

@GiuseppeR
Never meant it to be efficent, but i think its less painful than re-editing the whole config file.
But i get your point. I think that we will see the "old" features in the new firewalls, but dont ask me when ;-)

There are a lot more paint points as well like the limited ad-join capabilities or the filtering of the ad-groups and a lot more..

Cheers!

A part from what I wrote above, I cannot rename also a VLAN I created manually:

You name it when you make it not after

Well the USG60 for VLAN's when you name the interface you can't rename it after

The reason why for the WAN on the USG60 can be changed is like I said its hardware name is then mapped to what you want but its really mapped to another name you don't see.

I guess it depends how you see this as a problem the way I see it is your own going to do it once and never change it later on.

Another way to look at it is you have a description so name what you want there and keep the interface name simple like VLAN443 because thats what it is.

Or something Zyxel could do is on selecting the interface for rule include the description along side and if the description need changing it can be done without problem.