Forum Discussion

J_Pizzolato_207's avatar
J_Pizzolato_207
Icon for Nimbostratus rankNimbostratus
Jun 24, 2016

CLIENT_CONNECTED still supported in 11.5.3

I have a simple irule, my first:

 

when CLIENT_CONNECTED { after 15000 { reject } }

 

and I am wondering why I am getting this error message:

 

01070151:3: Rule [/part/customTCP-timeout] error: /part/customTCP-timeout:1: error: [unknown event (CLIENT_CONNECTED)][when CLIENT_CONNECTED { after 15000 { reject } }]

 

I have checked for trailing spaces and have checked the {} are in the right position. Is CLIENT_CONNECTED no longer supported on 11.5.3?

 

application delivery
iRules

8 Replies

Sort By
  • Vernon_97235's avatar
    Vernon_97235
    Historic F5 Account
    Jun 24, 2016

    The event is CLIENT_ACCEPTED (rather than _CONNECTED). Since the matching server-side event is SERVER_CONNECTED, I'll admit that I often transpose that trailing part into the client-side event, too.

     

    • Vijay_E's avatar
      Vijay_E
      Icon for Cirrus rankCirrus
      Jun 24, 2016
      These are the valid iRule events and their function: https://clouddocs.f5.com/api/irules/Events.html
  • VernonWells's avatar
    VernonWells
    Icon for Employee rankEmployee
    Jun 24, 2016

    The event is CLIENT_ACCEPTED (rather than _CONNECTED). Since the matching server-side event is SERVER_CONNECTED, I'll admit that I often transpose that trailing part into the client-side event, too.

     

  • VernonWells's avatar
    VernonWells
    Icon for Employee rankEmployee
    Jun 25, 2016

    As @Odaah suggests, there is no CLIENT_CONNECTED event. The CLIENT_ACCEPTED event fires when the client traffic is accepted for processing (for TCP, on completion of a successful three-way handshake with the client; for UDP, on receipt of a segment; and so forth). The SERVER_CONNECTED event fires when the layer4 session setup completes toward the destination (for LTM, that's usually a pool member). In other words, for TCP, it's when the server-side three-way handshake successfully completes; for UDP, it's when the first segment in the flow has been transmitted; and so forth.

     

  • VernonWells's avatar
    VernonWells
    Icon for Employee rankEmployee
    Jun 25, 2016

    As @Odaah suggests, there is no CLIENT_CONNECTED event. The CLIENT_ACCEPTED event fires when the client traffic is accepted for processing (for TCP, on completion of a successful three-way handshake with the client; for UDP, on receipt of a segment; and so forth). The SERVER_CONNECTED event fires when the layer4 session setup completes toward the destination (for LTM, that's usually a pool member). In other words, for TCP, it's when the server-side three-way handshake successfully completes; for UDP, it's when the first segment in the flow has been transmitted; and so forth.