Forum Discussion
uni
Altostratus
AltostratusPersistent SNAT address based on session cookie
I have a client whose application is sensitive to the client IP address
changing within a session. In their environment, there is some selective
SNATting (internal clients are SNATted, public IPs ar...
Michael_Yates
Nimbostratus
NimbostratusHi Stephen,
You said that your Client's Application does not handle the Client IP Address changing within a session. Will the application work with an X-Forwarded-For Header? If so, then the application can pull the client IP Address out of the header and log/utilize it. You can see where to enable the X-Forwarded-For Header in this post.
If not, then you could create a SNAT Pool with a single IP Address in it and SNAT to it (depending on the number of concurrent users your application will have you may need more than one. SNAT IP Addresses do have a connection limit per IP Address. See SOL7820: Overview of SNAT features for additional details). This would make your SNAT IP Address constant if nothing else (but you may need to engage a OneConnect Profile to keep the TCP Sessions load balanced properly).
Hope this helps.