Forum Discussion

12 Replies

  • Hi, where is the 3 way handshake not getting completed? (Client side or server side) Are you using default crts?

     

  • Server Side, from F5 to the server there is a [SYN], then Server sends a [SYN, ACK] & now the F5 sends [RST].

     

    • NikhilB's avatar
      NikhilB
      Icon for Employee rankEmployee
      with or without a profile? have you executed a tcpdump or an ssldump if you are indeed connecting on port 443?
  • shaggy's avatar
    shaggy
    Icon for Nimbostratus rankNimbostratus

    if you are seeing F5 [SYN], server [SYN-ACK], F5 [RST] on the server-side, the transaction isn't even making it to the SSL handshake. Are you sure that's the application traffic and not an F5 tcp-half-open monitor?

     

  • Wont the tcp-half open monitor traffic come from the Shared-IP of the guest-vCMP? Based on the IP its not the monitor traffic.

     

    • shaggy's avatar
      shaggy
      Icon for Nimbostratus rankNimbostratus
      monitor traffic will come from the non-floating self-IP of each vCMP guest based on the guest's routing-table.
  • I have taken tcp dump, I see resets in the captures, when I use firefox, it says 'Connection was reset'.

     

    • NikhilB's avatar
      NikhilB
      Icon for Employee rankEmployee
      do you have snat configured by any chance?
    • NikhilB's avatar
      NikhilB
      Icon for Employee rankEmployee
      pls respond to the comments inline so we know who your answering back to. Ensure you have address and port translation turned on the VS? have you removed the default crt on the server end? (what are the results?) Have you tried using ssldump to analyse the traffic?
  • shaggy's avatar
    shaggy
    Icon for Nimbostratus rankNimbostratus

    can you post the VS configuration and the ssl-profile configurations?

     

    • tmsh list ltm virtual (vs-name)
    • tmsh list ltm profile client-ssl (client-ssl profile-name)
    • tmsh list ltm profile server-ssl (server-ssl profile-name)

    you might try assigning the server-ssl profile "serverssl-insecure-compatible". Although, as I mentioned earlier, if you see that the server-side TCP 3-way handshake being reset before the SSL handshake occurs, then the server-side SSL handshake should make no difference.