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

Jibinpv_254622's avatar
Jibinpv_254622
Icon for Nimbostratus rankNimbostratus
Feb 28, 2017

F5 sends TCP RST after handshake

We have implemented an Client authentication on one of our services to client. Post that client is getting authenticated fine however ,a TCP RST has been send to client by F5 after the handshake. W...
application delivery
LTM
Nicholas_P__308's avatar
Nicholas_P__308
Icon for Cirrus rankCirrus
Feb 28, 2017

Any iRules in use? Access Policy?

 

Ran into a similar issue, everything was normal, client - server connect went fine but still recieved a 404. Ended up being misplacement of a splash page iRule. It was placed ahead of the information gathering and resulted in error.

 

  • Jibinpv's avatar
    Jibinpv
    Icon for Nimbostratus rankNimbostratus
    Mar 15, 2017

    Hi Nicolas - thanks for the response.

     

    Yes - we did have the irules in place for the pool selection.

     

    The issues here was the SSL persistence on VS. I have that removed and the issues set to fixed.

     

    Now the SSL persistence is enabled via irule as recommended by F5.