Add support to choose both protocols (TCP/UDP) in Service object
Currently we have to create a separated rule to each protocoal TCP/UDP.
We are currently implementing object based forwarding rules, for inclusion in v17
Much -Much needed, it is really a big hassle to manage so many rules. Also, I feel it'ld be adding load on the processor.
Please add this feature to have TCP and UDP in the same rule.
Aland Coons commented
Its a work around for Network/User rules, but Business Application Rules can't be associated with a Service/Service Group yet. :(
That's a good workaround but would be nice to have a both setting for quick configuration.
You can create a custom service wich includes both TCP and UDP ports.