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

HenryX_171845's avatar
HenryX_171845
Icon for Nimbostratus rankNimbostratus
Sep 26, 2014

Problem of TCP editing in BIG-IP VE

I'm running AWS m3.large instance of VE: BIG-IP 11.5.1 Build 0.4.110 Engineering Hotfix.   It is okay to run HTTP::header insert in iRule, but TCP::option set, or TCP::payload replace, ... always ...
HenryX_171845's avatar
HenryX_171845
Icon for Nimbostratus rankNimbostratus
Sep 28, 2014

Using TCP profile, I could insert to either SERVER or CLIENT per connection.

 

An example iRule of concept would be:

 

when CLIENT_ACCEPTED { set clientip [IP::client_addr] TCP::payload replace 0 0 $clientip log local0. "Inserting TCP DATA to SERVER" TCP::release log local0. "Releasing TCP DATA - necessary" }

 

when SERVER_CONNECTED { set serverip [IP::server_addr] TCP::payload replace 0 0 $serverip log local0. "Inserting TCP DATA to CLIENT" TCP::release log local0. "Releasing TCP DATA - necessary" }

 

My original idea was to argument TCP::option per packet for the connection, it seems I'm out of luck here with VE.