If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

takes two minutes to connect to IRC server



Infrastructure & Operations
NetOps: DC ACL Request
3 years ago
3 years ago


(Reporter: dbaron, Assigned: XioNoX)



Since the new IRC server a week or two ago, it's taken about two minutes to connect to IRC from the SF office.  (I don't think I see this problem from home.)

For example, what I saw just now was:
[2014-10-10 13:09:42 -0700] --- Looking up irc.mozilla.org..
[2014-10-10 13:09:42 -0700] --- Connecting to belew.mozilla.org (2620:101:8016:74::143) port 6697..
[2014-10-10 13:11:50 -0700] * * Subject: /C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert Global Root CA
[2014-10-10 13:11:50 -0700] * * Issuer: /C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert Global Root CA

(note the timestamps).

I think I see this at least a significant portion of the time -- not sure if it's all of the time, though.
Assignee: server-ops → infra
Component: Server Operations → Infrastructure: IRC
Product: mozilla.org → Infrastructure & Operations
QA Contact: shyam → dparsons


3 years ago
Assignee: infra → dparsons
Thanks for bringing this to my attention. I'm wondering if this might be an ipv6 issue - can you try connecting to from the same location and let me know how it goes?

Actually, never mind on testing for me, it looks like this is a known ipv6 issue between sfo1 and scl3, and is being worked on right now. In the mean time, feel free to connect to and you should have no problems.
Doing some very preliminary testing, it looks like it's ipv6 related...

shyam@katniss ~ $ telnet irc.mozilla.org 6667
Trying 2620:101:8016:74::143...
telnet: connect to address 2620:101:8016:74::143: Operation timed out
Connected to levin.mozilla.org.
Escape character is '^]'.
:levin.mozilla.org NOTICE Auth :*** Looking up your hostname...
:levin.mozilla.org NOTICE Auth :*** Found your hostname (corp-nat.p2p.sfo1.mozilla.com)

I'm working with netops to confirm, stay tuned for updates.


3 years ago
Assignee: dparsons → network-operations
Component: Infrastructure: IRC → NetOps: DC ACL Request
QA Contact: dparsons → jbarnell


3 years ago
Assignee: network-operations → jbarnell
Im looking at this its not policy (flows) .... researching

Comment 5

3 years ago
After you connect, is performance normal?
i.e. Is it just the connecting part that is slow?

Flags: needinfo?(dbaron)
Performance is normal after connecting.  It is just connecting that's slow.
Flags: needinfo?(dbaron)

Comment 7

3 years ago
That was due to a routing issue. SFO1's IPv6 routes were not propagated properly everywhere in SCL3 and thus were taking a wrong return path.
Assignee: jbarnell → arzhel
Last Resolved: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.