This is fundamentally a duplicate of T151704: Libera Chat may throttle bot connections from tools, but the problem is currently worse than it has been in the past because of the lack of public IPv4 addresses on the new Stretch job grid. We should really try T151704#3467490 before we resort to abusing public IPs like we did in the past.

I've contacted freenode to see about resolving the issue in the short term (can't say for certain they'll agree to set the i:line or not), but long term we do need a better solution.... optimally as suggested above we'll need to see about having an ident daemon running so that each individual user with access will have a unique identity for them or their bots.

Hi Alex,

I've added that IP to the list of current Wikimedia IPs, they have a shared
connection limit of 500, I believe that will be enough. If it isn't, poke me
(emerson) on IRC or reply to this ticket.

Thanks,
emerson

Have they added the whole range or just that NAT IP?
If they've just added the NAT IP, I expect problems will resume if the tools exec nodes get given floating IPs?

In T216370#4962912, @Krenair wrote:

Have they added the whole range or just that NAT IP?
If they've just added the NAT IP, I expect problems will resume if the tools exec nodes get given floating IPs?

If they've whitelisted our NAT IP, do we still need to give the exec nodes floating IPs? T141445#2600708 suggests that it was for freenode, and our own wikis. I assume we can fix any rate limiting issue on the MediaWiki side (if there still is one?). I would expect all bots to have the noratelimit userright.

In T216370#4962912, @Krenair wrote:

Have they added the whole range or just that NAT IP?
If they've just added the NAT IP, I expect problems will resume if the tools exec nodes get given floating IPs?

I believe they just added the NAT IP to the existing i:line for us.

In T216370#4965975, @Legoktm wrote:

In T216370#4962912, @Krenair wrote:

Have they added the whole range or just that NAT IP?
If they've just added the NAT IP, I expect problems will resume if the tools exec nodes get given floating IPs?

If they've whitelisted our NAT IP, do we still need to give the exec nodes floating IPs? T141445#2600708 suggests that it was for freenode, and our own wikis. I assume we can fix any rate limiting issue on the MediaWiki side (if there still is one?). I would expect all bots to have the noratelimit userright.

probably not, let's hope no other use cases for that come up in future?