Add allowed IP configuration to prevent banning certain IP's

The tricky part of this is to figure out the best way to define IP ranges.

Symphony to the rescue, yay! We can use IpUtils::checkIp(). I've created a merge-request that is ready for review.

@douggreen: Impressive work! Super helpful addition!

Did you test this manually and ensure it works as expected? Do you see any chance for tests in ✨ Write functionality tests Needs review to check this?

One more question: Should we perhaps add a link to the IpUtils documentation page to show, which formats are allowed? I think for technical people that information might be helpful?

I've been running this on a production site since making the patch. A link to IpUtils makes sense. Can you add that? And for tests, I'd prefer that someone else writes them ... if you require them and don't want to write them yourself, I'll ask someone else on my team to do it, but I'd also prefer that you do that too ... since this patch does what I need.

This is an impressive work indeed. Very short and easy to understand and maintain. I have tested the fork on a live site, and it works as expected.

I would love to mark this as RTBC, but it is not mergeable. I tried rebasing it, and it is not rebaseable as well.
I think it is easier to manually copy the changes to a new branch.

I rebased and force pushed.

Grevil → credited code-brighton → .

As discussed in ✨ An IP Whitelist / Allowlist Active , I'll adjust the code to conform with the requirements of that issue.

Alright, all done and tested! (Also the update hook).

Please review!!

Alright, all done rereview pls!

Great work once again! Thank you @Grevil! :)

Automatically closed - issue fixed for 2 weeks with no activity.

Hi great stuff,

Can someone help me with a use case where I want to whitelist this range of IPs:

59.26.62.25 > 59.56.62.128

How do i write that?

@code-brighton meta-answer: Did you ask Chat-GPT perhaps? Seems this would be a good idea ;) (but check the result)

@#23: Sorry, but could you please consider to rephrase your answer to the previous commented question with a more respectful attempt? Examples can be found at https://www.drupal.org/docs/develop/issues/issue-procedures-and-etiquett... → under #Constructive review comments

@all: testing this on Drupal 11 with the merge from the Drupal 11 compatibility issue it seems the whitelisted IP gets ignored (not whitelisted).

Also the description below the field is far too cryptic and needs work. It should also hold examples with simple IPs like 123.34.34.14 so that users are not confused by the trailing number behind a slash (/23) exaples, which is not like IPs look like in the banned ip table.

@dqd, sorry that wasn't meant disrespectful in any way. I think it's just something AI can help with very well. Of course you're right, I should have run that question and place the answer here. Thank you, @dqd