Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 37 subscribers
  • Views 1144 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

WAF rule on 18.1.5 does not block in firewall level but in waf (403)

RaNd_gr

Hi,

I created a WAF rule, to allow only specific IPs, but they are blocked in WAF level displaying  403 error on the client 

(Forbidden, You don't have permission to access this resource), instead in firewall level (drop/reject) as it used to be the case so far.

Is this configurable somewhere ?



This thread was automatically locked due to age.
Parents
  • 0

    Update:
    1. Created a blackhole NAT same as WAF.

    2. Created a NAT with source the allowed IPs, and all others default.

    I needed to allow only Cloudflare IPs to access a WebServer protected by a WAF rule.

    Blackhole NAT

    Allow NAT

Reply
  • 0

    Update:
    1. Created a blackhole NAT same as WAF.

    2. Created a NAT with source the allowed IPs, and all others default.

    I needed to allow only Cloudflare IPs to access a WebServer protected by a WAF rule.

    Blackhole NAT

    Allow NAT

Children
No Data
Unfiltered HTML