rule
4 TopicsAFM Default drop counter
I would like to know the purpose of the default drop/reject rule under global context, i.e. what circumstance is this incremented? Creating policies within global/virtual or self IP context do not seem to affect the counter (any accept/deny counters are all incremented within those polices). Reset stats does not affect the counter value (example below 423 remains the same). Thankyou in advance.501Views0likes1CommentPEM Policy Rule - Custom Syntax
Hello I want to change a PEM policy rule. Instead of adding source or destination IPs in the flow section, I want to use the custom option to point to a data group of the IP addresses. This is due to the fact I have lots of IP addresses in the source\dst and some repetitive rules that the protocol and action differentiate one from another, so pointing to a shared data group of IP addresses from a single point makes sense to me, to avoid mistakes. The thing is, I couldn't find anywhere the syntax of pointing to a data group Thanks in advanced for any help.371Views0likes1CommentMajor error when saving LTM rules
Trying to put in place the http-to-https redirection as described in https://support.f5.com/kb/en-us/solutions/public/14000/900/sol14996.html When saving the rule, got a white page "Major application error, please see logfile". It looks like LTM does not like "getfield" in the expression below. https://[getfield [HTTP::host] ":" 1][HTTP::uri] Without "getfield", the rule is saved without issues. Are there any restrictions on using this syntax in 11.4?233Views0likes1CommentAFM / Configuring rules within a rule list through REST
Hey guys, Unfortunately I have to configure some AFM rule lists and rules, respectively. My first attempt was to add a new rule list with the whole rule set in one piece with a single POST request. I got this error message { "code": 400, "message": "Rule entries that are being added with the \"add\" option must specify either \"place-before\" or \"place-after\"", "errorStack": [], "apiError": 26214401 } I then tried to add new empty rule lists through REST which worked. After that I wanted to add several rules within that new rule list. That failed again with the error message mentioned above. Even POSTing a single rule in the this rule list fails with the same error message. It seems that the this message has been copied from the tmsh refrence documentation (see here: https://clouddocs.f5.com/cli/tmsh-reference/v15/modules/security/security_firewall_rule-list.html) . I am a bit confused now how to add rules to a list. However, I added "ruleNumber" in the JSON body and experimented with different numbers (i.e. 0) but it did not work. Configuring rules within rule lists and refrencing the list within a policy is the way to go here at my company. While writing this post I found out that it is possible to just configure rules within a policy (we rarely use the AFM module). So here are my questions: Do you have any ideas what I am doing wrong when using REST configuring rules within a rule list? The mentioned way to go seems odd to me. Is it enough for simple packet filtering ("look at the source and allow only port 443" for example) to configure rules within a policy? What is your good practice?Solved30Views0likes1Comment