Best Of

Hi @Zyxel_Melen

for example you create a rule "New_Server" for opening a port TCP 12345.

Some time after that you receive another request for opening another port on the same server, so it could be useful to rename first rule "New_Server_TCP12345" and write a second rule as "New_Server_UDP98765"

Nowadays to have those 2 rules, you have to recreate the first one from zero.

It is not efficient.

If it is impossible by design, I don't know your source code, at least having a Copy command should save some time: you could copy the first rule renaming it before saving to firewall and you could add the second rule.

@Lucas_Wilson

Also, since VoIP traffic is usually UDP, keep in mind that bwm currently doesn't seem to be able to prioritize UDP traffic. At least it seems that way for @PeterUK and myself. Zyxel is investigating what's going on:

Hi,

I believe this was a feature in the legacy USG series firewalls, but doesnt seem to be the same on the H series.

I read the following guide on setting up BWM for VOIP traffic QoS:
https://mysupport.zyxel.com/hc/en-us/articles/360010431759--ZyWALL-USG-How-to-configure-BWM-QoS-on-Zyxel-firewalls
It suggests that incoming/outgoing interface should be set as "any", this makes sense since VOIP traffic is bi-directional. However, on the H-Series, "any" doesn't appear to be an option for incoming/outgoing interface.

Please can this be addressed in a future release?

Hi @PeterUK

Thanks for the video. Let us take further investigation, and I will keep you posted.