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

cvitale_103614's avatar
cvitale_103614
Icon for Nimbostratus rankNimbostratus
Jul 16, 2014

Specify use specific custom persistence profile in iRule

We currently have this iRule association on LTM VIP service. It does a conditional check and if it meets criteria then it says to use (persist cookie) else it will use (persist source_addr). We would...
cvitale_103614's avatar
cvitale_103614
Icon for Nimbostratus rankNimbostratus
Jul 16, 2014

ok thanks. So if I wanted to specify (ANY) source address would the mask be 255.255.255.255.

 

Steve_M__153836's avatar
Steve_M__153836
Icon for Nimbostratus rankNimbostratus
Jul 16, 2014
Yes you are correct. I would be careful with that. It's not uncommon to do that, but one issue I have seen is a customer using NAT on their end so their IP would change sometimes and then they could get load balanced to a different server in the pool if the persistence mask is set to 255.255.255.255. With a stateful application this is a problem. You may want to consider a Class C mask to avoid that. There are pros/cons for either mask. All depends on your customers and your application.