Forum Discussion
NimbostratusCLIENT_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?
8 Replies
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.
J_Pizzolato_207So then when is CLIENT_CONNECTED used?
Vijay_ECirrus
These are the valid iRule events and their function: https://clouddocs.f5.com/api/irules/Events.html
VernonWellsEmployee
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.
- J_Pizzolato_207So then when is CLIENT_CONNECTED used?
- Vijay_EThese are the valid iRule events and their function: https://devcentral.f5.com/wiki/irules.Events.ashx
- VernonWells
As
@Odaahsuggests, 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
As
@Odaahsuggests, 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.
