Forum Discussion
nitass_89166
Jun 10, 2014Noctilucent
have you tried TCP::collect in LB_SELECTED?
How to process Client side's TCP Payload after SERVER_CONNECTED?
https://devcentral.f5.com/questions/how-to-process-client-sides-tcp-payload-after-server_connected
- R_MarcJun 10, 2014NimbostratusYes. Perhaps I'm doing something wrong there, but here's what I tried as a test:
Here's what I see in the log:when CLIENT_ACCEPTED { log local0. "client ip [IP::client_addr]" } when CLIENT_DATA { log local0. "in client data" } when LB_SELECTED { TCP::collect log local0. "[TCP::payload]" TCP::release } when SERVER_CONNECTED { log local0. "[IP::server_addr]" }
I'll read that article though and see if I find anything useful.Jun 10 12:05:53 slot1/bip info tmm[10558]: Rule /Common/monitoring-rule : client ip 10.0.148.33 Jun 10 12:05:53 slot1/bip info tmm[10558]: Rule /Common/monitoring-rule : Jun 10 12:05:53 slot1/bip info tmm[10558]: Rule /Common/monitoring-rule : 10.0.145.161
- nitass_89166Jun 10, 2014Noctilucenti think you should release data (TCP::release) in CLIENT_DATA (not LB_SELECTED).
- R_MarcJun 10, 2014NimbostratusGot it working... Thanks for the tip.