IPV6 allow-all & inconsitent with enable/disable blocking

[jacobpretorius]

Hello,

We tried the plugin and have found two issues:

1. It is not possible to add IPV6 CIDR ranges. We would like an allow-all range similar to IPV4 - to disable this plugin in production without doubt. We can add 0.0.0.0/0 for IPV4 which works fine, but IPV6 ::/0 cannot be added in the UI.
2. The plugin is inconsistent when enabling/disabling the "Block unauthorized access" checkbox in the CMS. We often have to click "save" twice to disable blocking.

These two issues leave us with concerns that IP blocking won't be disabled when we deploy to production so we'd have to recheck it every time making the plugin unsuitable for us.

[vyan024]

@jacobpretorius

Thanks for your feedback. The original idea of developing this is primarily for non production environment, I'm sorry to hear you had these issues.

#1, I don't have a solid stable IPv6 CIDR validation rule, hence this is not yet developed, and UI will use the same validation to check before allowing persisting

#2, I have got anyone reported this issue so far. The only time I noticed this could happen is when you install this to your solution and change the settings back and forth, later remove this and add it back again. I'm not sure if this is caused by DDS persistence issue or not, need a bit more time to investigate this. You should find a bit more detailed info from logs.