Is there some reason that a service group can't be used as a destination service for DNAT? While it makes sense that traffic arriving on a single port can't really be duplicated on one or more ports, it would be very convenient if the rule could be set to "recognize" and forward like-to-like. For instance: I have an internal webserver that I'd like to publish for both HTTP and HTTPS. Instead of having both an HTTP target and HTTPS target, wouldn't it be clever if I could create a service group ("Web Server") with both HTTP and HTTPS as members; I could then assign "Web Server" as both the source and destination services, and the ASG would 'link up' the like-to-like service ports.
On the other hand, it could already do this, and I just don't understand how to get it to work.
This thread was automatically locked due to age.
