Please move cm-bbot-linux-002/003 from the build network to community network. They don't need public IPs; nat is fine if you can do it. I will need ssh access to them via MPT though. They should have no incoming access allowed from the internet, and outgoing access can be fairly limited as well. They will need to access buildbot.net:9989 though.
We don't have NAT infrastructure in place for the community build network. Every host will have a public IP. If public IPs aren't necessary, what was the reasoning for using the community build network in the first place?
(In reply to comment #1) > We don't have NAT infrastructure in place for the community build network. > Every host will have a public IP. > > If public IPs aren't necessary, what was the reasoning for using the community > build network in the first place? They need to be in a place that doesn't have access to any of mozilla's infrastructure.
Works for me. jdow, For these minis: address: 18.104.22.168 & 49 gateway: 22.214.171.124 netmask: 255.255.255.192 vlan: 20
changing this remotely didn't work out very well. I'll get these online at MPT Thursday morning.
The one with IP 126.96.36.199 is online, although I'm not sure if that is 002 or 003. I don't have a password that will let me into the box, so I can't configure the network on either of them.
Both are now online: cm-bbot-linux-002.sj.mozilla.com 188.8.131.52 cm-bbot-linux-003.sj.mozilla.com 184.108.40.206
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.