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 possible to off load SSL to BIG-IP and using the Source IP option, there is a fare amount of "clumping".

 

 

Is there any plan to add SourcePort (with SourceIP) as a parameter to persistence method, or would it be possible by parsing IP header? (using Universal Persistence)

 

 

Thanks.

 

 

John
application delivery
dev
devops
iRules

1 Reply

  • 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