Closed
Bug 1394633
Opened 7 years ago
Closed 7 years ago
IRC connection limit bump for *.hashbang.sh
Categories
(Infrastructure & Operations Graveyard :: Infrastructure: IRC, task)
Infrastructure & Operations Graveyard
Infrastructure: IRC
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: vandor2012, Assigned: daveio)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.90 Safari/537.36
Steps to reproduce:
Connect to the IRC server from a hashbang.sh server
Actual results:
When connecting to the server, the following message is given:
> =!= Closing link: (unknown@104.245.37.138) [Too many connections from your IP (global class). If you have a Mozilla LDAP account, you can get a temporary exemption here: https://iplimit.irc.mozilla.org/]
Expected results:
Connection to the server should be established
*Note:* Users can be identified on a per-user basis by using the `ident` protocol. Because each user are all required to use a shared IP (on a per-server basis, with currently four servers), the `113` port (as well as any port under 1024) is reserved for the `oidentd` daemon, configured to disallow spoofing.
Assignee | ||
Comment 1•7 years ago
|
||
Each node listed on https://hashbang.sh/server/stats now has an IP limit matching its maxusers. # hashbang.sh, bug 1394633, IPs listed in https://hashbang.sh/server/stats <connect parent="main" allow="45.58.35.111" localmax="500" globalmax="500" limit="500" modes="+x"> <connect parent="main" allow="45.58.38.224" localmax="500" globalmax="500" limit="500" modes="+x"> <connect parent="main" allow="104.245.35.240" localmax="500" globalmax="500" limit="500" modes="+x"> <connect parent="main" allow="104.245.37.138" localmax="500" globalmax="500" limit="500" modes="+x">
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•7 years ago
|
Assignee: infra → dwilliams
Updated•4 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•