Closed Bug 701531 Opened 14 years ago Closed 14 years ago

increase freenode IRC connection limit from SF guest network

Categories

(mozilla.org Graveyard :: Server Operations, task)

All
Other
task
Not set
minor

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: warner, Assigned: bkero)

Details

I'm hosting a small external-project developers meeting in the SF office, about 6 people, and they're running into connection-limit problems when trying to attach to the freenode IRC network. They're all using the MozillaGuest wifi network, of course. I chatted briefly with one of the freenode staff, and they said: <jbroome> To increase your connection limit, please email ilines@freenode.net with the IP, expected number of connections, and an abuse contact. Also consider running an identd. Could we do that? I could figure out the IP and mail them, but 1: the abuse contact should probably be someone in Ops who can track down abusers if necessary, and 2: running identd or some other scheme makes sense but is beyond my purvue. I assume that the MozillaGuest network uses a different external IP, and that we've already talked freenode into accepting lots of connections from the staff-only IP, and the problem is that we haven't done the same for the Guest IP. I don't know what number of connections to recommend, maybe 10 or 20? (I don't see any other non-staff groups in the office today, so I assume that we managed to run into the per-IP quota with just 4 or 5 connections). (I also imagine we've run into this problem before with the MV office, and it's just that this is the first time we've encountered it for the SF office). thanks!
Sure, I'll drop Freenode an email and see what we can do.
Assignee: server-ops → shyam
Group: infra
Ben got this taken care of at Freenode. Feel free to re-open if you run into issues.
Assignee: shyam → bkero
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
thanks!
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.