Forum Discussion
You probably referring to LTM and not GTM, as GTM does not care about ports. I need more information about your configuration.
Can you please provide these parts of the configuration?
Datagroup hbss-port-exception
Virtual Server
Pool
Why wouldn't GTM care about ports? It needs to allocate a local source port for both TCP and UDP when providing DNS LB to DNS servers, does it not?
I don't think the LB_SELECTED was the event that is able to identify the local port so I've shifted to calling it in the SERVER_CONNECTED event. This is working for us and I don't like it because it's brutal to the client, but this affects only TCP and we only see about 4 events per 12 hours that match across the 10 ports we want to avoid. The client would simply timeout and retransmit - thus getting a new port which is most likely no in the restricted port range.
when SERVER_CONNECTED {
if { [class match [TCP::local_port] equals hbss-port-exception] } {
log local0. "HBSS EXCEPTION LOG: [TCP::local_port] - GTM dropping"
TCP::close }
}