TCP & ICMP session are not resumed after Auto reconnect

TCP & ICMP session are not resumed after Auto reconnect

book

Article ID: CTX492902

calendar_today

Updated On:

Description

TCP & ICMP session are not resumed after Auto reconnect

TCP Expectation by Customer
When the Citrix Gateway client is disconnected and reconnect itself automatically, we expected the TCP communications to be resumed through the retransmission capacity of TCP


 

Resolution

Expected Behaviour:

ICMP detailing

In case of ICMP as we saw, client A   [ where the VPN session is established ] is doing a ICMP ping to client B  [ a backend resource hosted in intranet and currently being tunnelled over the VPN session ]. At the same time, client B i.e. the backend resource tried to do a ICMP ping to client A i.e. the IIP where VPN is connected. Now, as the 4 tuple for these two scenarios i.e. Src IP, Dest IP, Src port and Dest port are all same, VPN plugin merges the two ICMP based connections to one i.e. if one connection closure happens it will die the other one too. This is as per VPN plugin design and there's nothing we can do about changing the design. 

TCP detailing 

when client disconnects and reconnect we expect to start new TCP connection. We have no plan yet to make change in this behaviour any time soon. 


Problem Cause

Expected behaviour