• Resolved ragrant0

    (@ragrant0)


    Firstly, thanks for a very useful and user-friendly plugin!

    For whitelisting, I saw in your documentation an example of an IP range that includes 23 IPs. Something like this: 123.123.123.0/22

    How can I increase this range to include all IPs in the third and fourth (out of four) parts of the IP?

    I’ve tried:
    123.123.0.0
    and
    123.123.0/255.0/255

    But they didn’t work.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Proxy & VPN Blocker

    (@rickstermuk)

    To include everything between 123.123.0.0 and 123.123.255.255 that would be 123.123.0.0/16

    To include everything between 123.123.123.0 and 123.123.123.255 would be 123.123.123.0/24

    This resource should be helpful: https://www.vultr.com/resources/subnet-calculator/

    Thread Starter ragrant0

    (@ragrant0)

    I see. Thanks for that!

    For future users, I recommend you add that first example to the documentation. At least I couldn’t find it in the docs.

    By the way, I’ve never seen a slash + number (/16 or /24) to mean 0-255. Is there any particular reason to use those numbers instead of the usual 0 or asterisk for a wildcard?

    Plugin Author Proxy & VPN Blocker

    (@rickstermuk)

    No problem!

    It’s how the proxycheck.io API handles this kind of filtering for whitelist/blacklist.

    Please see https://www.ripe.net/about-us/press-centre/understanding-ip-addressing for some decent information on how the prefixes work, there is also a chart showing how many IP’s are in each prefix.

    I can perhaps update the description on those pages in the Plugin for more clarity.

    Your alternative is the Rules feature on your proxycheck.io dashboard, this is an extremely powerful tool. and here you can represent your IP ranges like 123.123.0.0-123.123.255.255 and set it up as this example: https://i.imgur.com/LoEByk7.png

    Thread Starter ragrant0

    (@ragrant0)

    Thanks for the extra info.

    ip addressing looks more complicated than I thought!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘For whitelisting or blacklisting, what is the syntax for a broader IP range?’ is closed to new replies.