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

steelplate_8766's avatar
steelplate_8766
Icon for Nimbostratus rankNimbostratus
May 25, 2010

sNAT to Windows server and port collision

Hi, I have an F5 doing sNAT, and the problem I face is that the windows server keeps the port in time_wait (currently default 240 seconds windows 2003 server). The F5 will attempt to reuse the client...
config
design
steelplate_8766's avatar
steelplate_8766
Icon for Nimbostratus rankNimbostratus
Jun 10, 2010
tcp_close timer shouldn't make any difference in my case anyway

 

 

http://tools.ietf.org/html/rfc793section-3.5

 

 

has this diagram

 

 

TCP A TCP B

 

 

1. ESTABLISHED ESTABLISHED

 

 

2. (Close)

 

FIN-WAIT-1 --> --> CLOSE-WAIT

 

 

3. FIN-WAIT-2 <-- <-- CLOSE-WAIT

 

 

4. (Close)

 

TIME-WAIT <-- <-- LAST-ACK

 

 

5. TIME-WAIT --> --> CLOSED

 

 

6. (2 MSL)

 

CLOSED

 

 

The problem I have is the server goes to point 6, and within the 2MSL period incomes a new syn. (150ms , close_wait timer is 5 seconds by default i think)