Open flow from builder1.ateam.phx1.mozilla.com to brasstacks1.dmz.scl3.mozilla.com

RESOLVED FIXED

Status

RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: jgriffin, Assigned: dcurado)

Tracking

Details

(Reporter)

Description

4 years ago
We'll need to use ssh and scp from builder1 to brasstacks1, so please open this flow:

from: builder1.ateam.phx1.mozilla.com
to: brasstacks1.dmz.scl3.mozilla.com
port: 22
(Reporter)

Comment 1

4 years ago
update ping:  can I get an ETA on when this might be done?
(Reporter)

Updated

4 years ago
Assignee: vpn-acl → network-operations
Component: Mozilla VPN: ACL requests → NetOps: DC ACL Request
QA Contact: dparsons → jbarnell

Updated

4 years ago
Assignee: network-operations → adam
(Reporter)

Comment 2

4 years ago
Update ping:  any ETA on when this might be done?  Thanks!
(Assignee)

Updated

4 years ago
Assignee: aanewman → dcurado
(Assignee)

Updated

4 years ago
Status: NEW → ASSIGNED
(Assignee)

Comment 3

4 years ago
My apologies.  This request slipped by on us.
I'm really sorry about that.

The security policy should now be in place.
Please let me know if there are any problems?

Again, sorry about that.
Dave

  From zone: dc, To zone: dmz
  Source addresses:
    builder1.ateam.phx1: 10.8.120.26/32 
    cm-vpn01: 10.2.72.11/32
  Destination addresses:
    brasstacks1: 10.22.74.57/32
  Application: junos-ssh
    IP protocol: tcp, ALG: 0, Inactivity timeout: 86400
      Source port range: [0-0] 
      Destination port range: [22-22]
Status: ASSIGNED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
(Reporter)

Comment 4

4 years ago
Thanks Dave!
No worries, we originally filed it in the wrong component, so it probably missed your filters. Thanks!
You need to log in before you can comment on or make changes to this bug.