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

johns's avatar
johns
Icon for Employee rankEmployee
Jul 11, 2006

Persistence using Source IP and PORT

I have a requirement where clients log into a terminal server farm and initiate https requests to VIP on BIG-IP, and need to persist users based on their source IP and PORT. Currently, it is not poss...
application delivery
dev
devops
iRules
Kai_Wilke's avatar
Kai_Wilke
Icon for MVP rankMVP
Dec 28, 2015

Hi Joey,

since v10, I wouldn't recommend to use 

persist UIE "[IP::client_addr]:[TCP::remote_port]"
anymore.

Using a CARP based algorythm for this specific scenario would be far more elegant now, since CARP doesn't need to store a session table record for each single client_ip:port combination and doesn't have to remember any timeouts.

when CLIENT_ACCEPTED {
    persist carp "[IP::client_addr]:[TCP::remote_port]"
    pool xyz_pool
}

Cheers, Kai