• Resolved pdwmb

    (@pdwmb)


    We’ve been using this plugin for a while, but unfortunately it does not work with IPv6. If you have blocked IPs at all, then all connections from IPv6 addresses will be blocked.

    We’ve got a fixed version in our github repository here:

    https://github.com/mythic-beasts/login-lockdown-mb

    It would be great to see the changes integrated into the main code base.

Viewing 3 replies - 1 through 3 (of 3 total)
  • @pdwmb – thank you. I am not sure why I did not get a notification on this post. Working on an update now.

    -Michael

    @pdwmb – question… in your code, when calculating a net block, how many addresses is that, and is it a meaningful block? When doing ipv4 it makes sense to block an entire subnet, since that is often how the blocks were historically assigned, and if I restrict access to a whole /24 block that was usually just one source/server, and only affected 254 ip addresses total. However, with ipv6 I am unsure how they are assigned, or in what blocks. For instance, if an iPhone user on ATT attempts to log in 3 times and fails, how many other devices would be affected by that block? If they cycle their IP address, will they still come back within the same block, or will they be able to attempt to log in again?

    Thanks.

    -Michael

    The core plugin now has this bug fixed as well as a couple of other changes, thanks.

    -Michael

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘IPv6 support’ is closed to new replies.