Hi @Fausto879 

Thanks for posting in our business forum.

Remove the Service Type in the ACL and it allows you to delete it.

I would appreciate it if you didn't mention it as a bug before you have some concrete results or dialectic steps.

Looks like you like spam the word bug and this is not a good choice to pick this word. Hope you can consider your description next time.

Hi @Fausto879 

Thanks for posting in our business forum.

Fausto879 wrote

  @Clive_A 

 

There is nothing using this rule, even if it existed it would have a darker color, notice that it is grayed out, this means that the router recognizes it as a default rule for the equipment.

 

If you can, do the test, create a new rule equal to any one on the list, you will not receive notice of the existence of this rule and it will be grayed out, with this lighter color.

 

See that there is rule number 6 Dns and number 13 UDP_BLOCK I created, they are the same.

 

The rule 14 that is not the same as the existing ones becomes dark. If you do the same, it will be grayed out (light), as is the router's default.

 

Look at the images

 

 

 

On a different model, with the alpha test firmware, I did not have this issue. Same SRC and DST port.

Did you apply this service type before you noticed it is a duplicate? Try to reboot your router as well.

Have you tried a different browser to rule out the cache issue?

Hi @Fausto879 

Thanks for posting in our business forum.

Fausto879 wrote

Did you apply this service type before you noticed it is a duplicate? Yes.

 

Try to reboot your router as well? Yes, restated.

 

Have you tried a different browser to rule out the cache issue? Yes.

 

I updated the firmware to 2.2.2 Build 20231017 Rel.68869

I created the same rules and the problem did not repeat itself.

 

The problematic rule remains after the update, as it came with a backup of the previous version. I will do a factory reset and test

 

 

 

 

 

 

So, I'd recommend you do this. Don't use the old backup as it is already corrupted as far as I can tell. Reset and use the V2.2.2 and start a fresh start. Then create this DNS again UDP 53 and check if this issue can be reproduced.