Forum Discussion
Different policies same destination and pool
- Jun 29, 2023
Hello,
Since the current setup now is using one virtual server IP for all services, and multiple ceritficates, you can create a LTM policy and start checking for the host header and based on this, apply the appropriate ASM polict based on this service.
For example:
Rule1:
if host header = www.abc.com when http request, Action: apply ASM policy 1.
Rule2:
if host header = www.aaa.com when http request, Action: apply ASM policy 2.
and so on, until you apply different ASM policies on all services. and then add a default rule at the end of the LTM policy, for exmaple (forward to pool x or disable ASM)
A fter finishing the policy, you must publish it and then assign the policy to the virtual server. everytime you caan to add/modify rule, you will need first to clone it and then modify the rules, and publish the policy again.
here is an example:
Thanks,
You can't use the same the destination IP on multiple virtual servers as you will need to change the port and source IP address, so better try the Mohamed_Salah_ suggestion.
Outside of that you can have a virtual server that redirects traffic to other virtual servers with a "forward action" with irules or local traffic policies and this can be based on SSL attributes like SNI as shown in https://my.f5.com/manage/s/article/K60036398 (K60036398: Configuring local traffic policies to restrict access to a virtual server using the TLS SNI extension) and then each virtual server can have a different WAF policy.
Read:
F5 has 30 day trial, so you can play on a Vware Workstation or AWS/Azure as much as you want 🙂
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