Closed Bug 1030601 Opened 11 years ago Closed 11 years ago

unable to connect to irc.allizom.org on non-standard ports

Categories

(Infrastructure & Operations Graveyard :: Infrastructure: IRC, task)

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: glob, Assigned: dparsons)

References

Details

currently you can connect to irc.mozilla.org on ports other than 6667 and 6697. the two that i know of that currently timeout are 6668 (non-ssl) and 8443 (ssl). i'm not sure if this is an artefact of the allizom staging environment or a configuration/firewall issue to be addressed prior to go-live.
Why do you need ports other than 6667 or 6697?
Port 8443 is required due to Verizon blocking inbound ports in the 6xxx range to our networks. Apparently they very aggressively block IRC ports over the MiFi connections, and so after testing I requested and we implemented port 8443 as a clone of 6697 to circumvent third-party IRC port range blocking.
OK, so aside from 6667 and 6697(ssl), which other ports should we have? Just 6668 and 8443(ssl)?
Assignee: infra → dparsons
I'm just going to copy the ports we have set up on the current irc network, which are 6665-7000, 6697(ssl), 8443(ssl). With the exclusion of 7000, because that port is used for links between servers. I could reconfigure the servers to use a different port, but I'd have to restart the whole network, and get netops flows.
Status: NEW → ASSIGNED
Correction: the ports used on the current IRC network are 6665-6669, 6697, 7000, 8443.
Depends on: 1030902
The following ports are now open on the test network: Non-SSL: 6665-6669 SSL: 6697,8443
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Component: Infrastructure: Other → Infrastructure: IRC
QA Contact: jdow → dparsons
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.