Forum Discussion
Looking for Setup Advice
- Feb 12, 2023
You need a first match strategy here. And while it is technically possible to forward to another VS, forwarding directly to the pool member is sufficient here unless you have reasons to forward to a secondary VS.
The flow is: client --> VS (with policy attached) --> pool (selected by policy)
Example:
Hi,
This is not an uncommon scenario. You can have one public IP and use it for a bunch of applications as long as you use different hostnames for your apps.
The best solution here is to use a local traffic policy which checks the HTTP hostanme and forward the request to the relevant pool, one rule per application, plus a default rule which either denies traffic or forwards it to a default pool.
Note that in this scenario you don't need to use different ports for your published apps, because the differentiator is the hostanme. Also whether your public IP is on your firewall (NATed to F5 vip) or directly configured on F5, this also doesn't matter.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com