Closed Bug 436370 Opened 18 years ago Closed 18 years ago

Report of problems accessing www.mozilla.org

Categories

(mozilla.org Graveyard :: Server Operations, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: davidwboswell, Assigned: mrz)

Details

The following came in on the webmaster at mozilla dot org list recently and I wanted to report it here in case this is a legitimate issue. ------------------------ Howdy. We've recently been assigned 114.30.96.0 - 114.30.127.255 via APNIC. (See http://puck.nether.net/pipermail/inet-ops/2007-October/000042.html for the ICANN announcement of 114/8 being allocated to APNIC). Customers on this range have complained of being unable to access mozilla.org - would you mind checking for bogon filters / prefix-lists / ACLs that may need updating to permit access to mozilla.org? Here's an example traceroute of how far we get on a 114/8 IP: Tracing route to mozilla.org [63.245.209.11] over a maximum of 30 hops: 1 9 ms 15 ms 15 ms lo5000.bras6.adl1.adnap.net.au [122.49.191.20] 2 15 ms 15 ms 15 ms g3-16.cor1.adl1.adnap.net.au [219.90.143.193] 3 15 ms 14 ms 15 ms vlan444.o5rxc76f000.optus.net.au [59.154.56.1] 4 202 ms 202 ms 202 ms ge-0-1-0-0.plapx-dr2.ix.singtel.com [203.208.149.253] 5 202 ms 202 ms 202 ms ge6-0-128.ir1.paloalto-ca.us.xo.net [206.111.12.45] 6 202 ms 202 ms 202 ms te-3-1-0.rar3.sanjose-ca.us.xo.net [65.106.1.58] 7 202 ms 202 ms 202 ms ge7-0-0d0.rar1.sanjose-ca.us.xo.net [65.106.1.57] 8 202 ms 202 ms 202 ms p0-0-0.MAR1.Fremont-CA.us.xo.net [65.106.5.134] 9 202 ms 202 ms 202 ms p0-0.CHR1.Fremont-CA.us.xo.net [207.88.80.178] 10 202 ms 202 ms 202 ms 207.88.3.58.ptr.us.xo.net [207.88.3.58] 11 * 69.80.192.70 reports: Destination net unreachable. Trace complete. Whereas here is an example from another IP range (in this case 122.49.*) Tracing route to mozilla.org [63.245.209.11] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 122-49-128-1.corp.adam.com.au [122.49.128.1] 2 <1 ms <1 ms <1 ms fa1-0.corpgw1.adl1.adam.net.au [219.90.129.173] 3 <1 ms <1 ms <1 ms gi0-0-795.busco1.adl1.adnap.net.au [219.90.129.141] 4 <1 ms <1 ms <1 ms g3-17.cor1.adl1.adnap.net.au [219.90.143.165] 5 <1 ms 1 ms 1 ms vlan444.o5rxc76f000.optus.net.au [59.154.56.1] 6 191 ms 191 ms 191 ms ge-0-1-0-0.plapx-dr2.ix.singtel.com [203.208.149.253] 7 191 ms 192 ms 192 ms ge6-0-128.ir1.paloalto-ca.us.xo.net [206.111.12.45] 8 192 ms 192 ms 192 ms te-3-1-0.rar3.sanjose-ca.us.xo.net [65.106.1.58] 9 192 ms 192 ms 192 ms ge7-0-0d0.rar1.sanjose-ca.us.xo.net [65.106.1.57] 10 192 ms 192 ms 192 ms p1-0-0.MAR1.Fremont-CA.us.xo.net [65.106.5.158] 11 192 ms 192 ms 192 ms p0-0.chr1.fremont-ca.us.xo.net [207.88.80.178] 12 189 ms 189 ms 189 ms 207.88.3.58.ptr.us.xo.net [207.88.3.58] 13 187 ms 186 ms 186 ms 69.80.192.70 14 186 ms 186 ms 186 ms v8.core2.sj.mozilla.com [63.245.208.50] 15 186 ms 186 ms 186 ms moz.org01.nslb.sj.mozilla.com [63.245.209.11] Trace complete.
Assignee: nobody → server-ops
Component: www.mozilla.org → Server Operations
QA Contact: www-mozilla-org → justin
Assignee: server-ops → oremj
Matthew, ideas?
Assignee: oremj → mrz
Out of date bogon acl, don't know how I missed that! Updated, should work now.
Status: NEW → RESOLVED
Closed: 18 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.