USG Flex 200H - Renaming interfaces

GiuseppeR

Hello everyone,

I went to configure parameters and names about standard interfaces on this 200H but I was unable to do that:

It seems strange to me because I could do that on an old USG60 that I use for configs' tests:

Is this something expected?

See you soon 😁

Zyxel_Kay

Hi @GiuseppeR

The behavior you're seeing is a design limitation of the USG FLEX H series firewall. Unfortunately, renaming the interface directly is not supported on this model. As mentioned by @mawokiel, the workaround is to remove the interface and then recreate it with the desired name.

For further details, feel free to check this post:

https://community.zyxel.com/en/discussion/25477/why-cant-i-edit-the-interface-name-on-the-usg-flex-h-models-in-the-web-gui-how-can-i-resolve-this

mawokiel

Hi Giuseppe,
same for me here. Imho the only possible way would be to create a new interface, put it in the same zone, delete the old one and bind the physical interface again.

Cheers,
Mathias

PeterUK

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

@mawokiel

I don't think that way is an efficient one, I understand the trick but too much time waste with these paths.

@PeterUK

I can understand the "possible" coding nightmare, but something that was possible to be done in an old USG60 I don't understand how could be impossible to be done with a sparkling 200H.

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

As you can see I cannot rename "VLAN_Ospiti" (in English VLAN_Guests) with another name. The only way I have is deleting it and re-programming it.

It is really strange.

mawokiel

@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!

GiuseppeR

Hello @mawokiel

where did you find that wish list?

I'm interested into reading it 😁

PeterUK

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

GiuseppeR

https://community.zyxel.com/en/discussion/comment/69767#Comment_69767

I understand that, but it seems strange not be able to rename it after saving it. It happens you have to rearrange names for internal purposes.

PeterUK

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.

Zyxel_Kay

Hi @GiuseppeR

The behavior you're seeing is a design limitation of the USG FLEX H series firewall. Unfortunately, renaming the interface directly is not supported on this model. As mentioned by @mawokiel, the workaround is to remove the interface and then recreate it with the desired name.

For further details, feel free to check this post:

https://community.zyxel.com/en/discussion/25477/why-cant-i-edit-the-interface-name-on-the-usg-flex-h-models-in-the-web-gui-how-can-i-resolve-this