Closed Bug 749798 Opened 12 years ago Closed 12 years ago

flow from l10n dashboards to arecibo1.dmz.phx1.mozilla.com

Categories

(Infrastructure & Operations Graveyard :: NetOps: DC ACL Request, task)

Product:
Infrastructure & Operations Graveyard
Component:
NetOps: DC ACL Request
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: cturra, Assigned: arzhel)

References

Details

we need to setup a the following flow:

source:
 l10n-dashboard1.webapp.scl3.mozilla.com (10.22.81.129)

destination:
  arecibo1.dmz.phx1.mozilla.com (10.20.74.19)
  443/tcp
  80/tcp
Depends on: 749375
No longer depends on: 749375
Blocks: 749375
You want arecibo1.dmz.phx1.mozilla.com (10.8.74.137)
or
arecibo1.dmz.corp.phx1.mozilla.com (10.20.74.19)
?
the request from bug 749375 is for: arecibo1.dmz.phx1.mozilla.com
Assignee: network-operations → cransom
root@bm-l10n-dashboard01:~# nc -zv arecibo1.dmz.phx1.mozilla.com 80
Connection to arecibo1.dmz.phx1.mozilla.com 80 port [tcp/www] succeeded!
root@bm-l10n-dashboard01:~# nc -zv arecibo1.dmz.phx1.mozilla.com 443
nc: connect to arecibo1.dmz.phx1.mozilla.com port 443 (tcp) failed: Connection refused

flows open
Assignee: cransom → arzhel
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
:XioNox can you confirm 443/tcp is open? comment 3 indicates connection refused.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
yeah it's open, when it's close I get a connection timeout (try any other port). Here is means the packets are reaching the server, but the server refuses them, so probably nothing listening on that port or iptables, etc...
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
Product: mozilla.org → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.