Forum Discussion
Irule for restricting access
- Feb 28, 2022
Hello, you should be able to do this either with iRule or with LTM policy.
F5 recommends using options available in standard configurations / GUI / traffic profiles over iRule syntax where possible, as they typically perform faster.In your case however using data group lists might be easier to mantain. One IP type data group to list restricted networks, and one string type data group to list restricted URI's.
if { class match [HTTP::path] ends_with restricted_uri_class && class match [IP::client_Addr] equals restricted_ip_class } { reject }
Thanks for the suggestion neewbie. Will check on it.
What we are looking for is that https://domain.com/admin/tools/index.html should only be accessible via private network, so thinking of using a Data Group List.
/tools/index.html is the extra add-on URI to be restricted.
However this main URL https://domain.com/admin should be accessible as is over both public and private.
I guess you need add virtual server better than add the irule
F5 can make same dst ip virtual server if source ip address difference between exist virtual server
below url is explain order of precedence for virtual server matching
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