Closed Bug 746023 Opened 13 years ago Closed 13 years ago

Open flow from new build-vpn to aus3-staging.m.o:80

Categories

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

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

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: nthomas, Assigned: cransom)

Details

There's a staging instance of AUSv2 on aus3-staging.m.o that we sometimes use to test configuration changes. I can reach that machine via ssh using the new vpn (vpn1.releng.scl3) it's not possible to reach port 80. I don't think the build machines will need to use 80, but users on the vpn will.
netops folks, according to casey the src address should just be the jumphost (vpn1.dmz.releng.scl3.mozilla.com) IP for this (and it should nat the traffic). I presume that covers both people sshing into the box and people using openvpn on the box. Please let me know if you need more info.
Assignee: server-ops-releng → network-operations
Component: Server Operations: RelEng → Server Operations: ACL Request
QA Contact: mrz → ravi
Assignee: network-operations → cransom
[root@vpn1.dmz.releng.scl3 ~]# nc -vz 10.8.74.30 80 Connection to 10.8.74.30 80 port [tcp/http] succeeded!
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
WFM too using the VPN. Thanks for the quick turn around.
Status: RESOLVED → VERIFIED
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.