• Resolved Jamesits

    (@jamesits)


    Wordfense do not block LAN segments like 192.168.0.0/16 by default; however, 100.64.0.0/10 is not included by default. These IPs are not public routable too.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Hi jamesits,
    That’s correct! However, it’s a shared address space and not a private one. Could you perhaps elaborate a bit on the issue you’ve run in to?

    Thanks in advance,

    Thread Starter Jamesits

    (@jamesits)

    I use the segment in LAN (I guess it is totally legit since I run an Autonomous System), then Wordfense blocked my reverse proxy (gateway for all websites to the public internet) 🙁

    Hi jamesits,
    Thanks for elaborating! I’ll forward your information to our developers and they’ll review the case and make a decision as to whether we can safely whitelist that range or not.

    Thanks for reporting your issue.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Treat 100.64.0.0/10 as private address’ is closed to new replies.