Port Forwarding - Changed Destination Port greyed out when mixing TCP/UDP/ICMP in Services field

version: (SFOS 17.0.0 Beta-1)

When creating a Business Rule DNAT template i have found that, when mixing TCP/UDP/ICMP protocols in the services fieldthe option for re-mapping ports:

1. Remapping option is greyed out and not possible to change the port

2. only possible to do remapping when using a single Protocol. eg TCP only or UDP only.

Is this a known limitation, that will be fixed in a future release?

Matt G - Bluechip IT

Parents

lferrara over 7 years ago

Matt,

I saw this behaviour too few days ago. How can the firewall understand which service must be changed to another one?

In order to improve this aspect a one to one relation is required and I guess a the moment XG is not able to handle it.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Reply

lferrara over 7 years ago

Matt,

I saw this behaviour too few days ago. How can the firewall understand which service must be changed to another one?

In order to improve this aspect a one to one relation is required and I guess a the moment XG is not able to handle it.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Children

MattyG over 7 years ago in reply to lferrara

Whats available in Beta 1 is a good step forward, at least a basic portforward (no port changes) can now be done in a single rule

Maybe they could either:

1. have 2 mapped port boxes for TCP and UDP ports and then inside those list the ports in csv order.

2. have a mapped port boxes for each port forwarded TCP/UDP allowing control over each port with its own box.

Matt G - Bluechip IT.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
lferrara over 7 years ago in reply to MattyG

The 2nd option makes more sense in my opinion (it is only my opinion :-)
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel