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

JoeReid's avatar
JoeReid
Icon for Nimbostratus rankNimbostratus
Sep 20, 2019

client timeout

I have an issue the 3 way handshake and MTU/MSS. When client initiates connection, the LB, pushes this request to the Webserver (configured to use Performance L4). The Webserver responds with a HTTP ...
application delivery
BIG-IP
LTM
Rodrigo_Albuque's avatar
Rodrigo_Albuque
Icon for Cirrocumulus rankCirrocumulus
Sep 23, 2019

Hi JoeReid? What do you mean by "agreed MSS"? Client advertises its MSS to BIG-IP and BIG-IP is supposed to honour it. Each side can have a different MSS. Do you have a packet trace?

  • JoeReid's avatar
    JoeReid
    Icon for Nimbostratus rankNimbostratus
    Sep 25, 2019

    I do have a packet trace, but due to corporate policy, am unable to share this. My understanding that the lower MSS is used, whether that be the server or the client, which is what we see from packet traces. What we are experiencing is the client MSS is 'honored', as you say, by the load balancer, but this is too high to be accepted through the client side encryptors. This all manifests after a HTML 202 from the server.