LeeEdwards
MIS
I am investigating a TCP/IP problem and would like to confirm proper behavior following a connection abort (RST flag set) for selecting the next available source port on the client.
Following graceful termination (FIN, ACK, FIN ACK), the client starts the next conversation using the next available source port.
However...
The server I am connecting to sometimes does not terminate the connection gracefully and aborts the connection with a RST packet. The client then starts up the next conversation using the SAME source port. This is causing me a problem as the firewall I am using (Firewall-1 NG FP3) drops the packet because it believes the packet is from an already established connection. I have worked round the problem by altering a parameter on the firewall, however could someone possibly confirm if the client (Windows XP) is behaving correctly by reusing the same source port following a connection abort?
Many thanks,
Lee
Following graceful termination (FIN, ACK, FIN ACK), the client starts the next conversation using the next available source port.
However...
The server I am connecting to sometimes does not terminate the connection gracefully and aborts the connection with a RST packet. The client then starts up the next conversation using the SAME source port. This is causing me a problem as the firewall I am using (Firewall-1 NG FP3) drops the packet because it believes the packet is from an already established connection. I have worked round the problem by altering a parameter on the firewall, however could someone possibly confirm if the client (Windows XP) is behaving correctly by reusing the same source port following a connection abort?
Many thanks,
Lee