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

Kai_Wilke's avatar
Kai_Wilke
Icon for MVP rankMVP
Jan 19, 2016

Hi JBengtsson,

I'm aware of two circumstances that may break the functionality of writing/reading [table] data.

1.) The [table] data isn't shared across different traffic-groups. So if you write [table] data on a virtual A in traffic-group A, then it can't be access on virtual B in traffic-group B. For further information see...

https://devcentral.f5.com/articles/big-ip-114-behavior-change-global-data-now-partitioned-by-traffic-group

2.) The [IP::client_addr] command may resolve differently across virtual servers. Using different route domains may cause your code to store data for TABLE_KEY=IP%1 (virtual server A in route domain %1) and query data for TABLE_KEY=IP%2 (virtual server B in route domain %2). But this issue could be easily resolved by stripping the route domain suffix before passing it to the [table] command (e.g. using [getfield [IP::client_addr] "%" 1]).

Cheers, Kai