For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

ankuragiwal_102's avatar
ankuragiwal_102
Icon for Nimbostratus rankNimbostratus
May 09, 2011

SNAT port collision to Windows Server

We are using FastL4 profile and we are seeing SNAT port collisions to external servers running Windows TCP/IP.     F5 reuses port as soon as it becomes available while Windows TCP/IP keeps clo...
config
design
ankuragiwal_102's avatar
ankuragiwal_102
Icon for Nimbostratus rankNimbostratus
May 10, 2011
We are not using OneConnect profile. I have confirmed that for two differnet clients, F5 is using same source port (this issue happens when as soon as first client closes connection, second client opens connection with same port). Modifying Windows TCP/IP stack is not an option. I will try changing SNAT configuration to "change".

 

 

There is also TIME/WAIT Recycle setting. This belongs to TCP profile. Will this setting apply while using FastL4 profile?

 

 

 

TIME/WAIT Recycle

 

 

The system will recycle or reuse the connection when a SYN packet is received in a TIME/WAIT state. This option allows the system to better optimize system resources by reusing a connection in a TIME/WAIT state when a SYN packet is received, instead of creating a new connection.

 

 

Note: If disabled, the system will establish a new connection instead of reusing a connection that is in a TIME/WAIT state.