Having an odd issue, I am unable to access http://files.pfsense.org/
Every 'is it down' service says the site is up.
I tried to access the site through a friends connection, same ISP & area; no problems.
Any idea what the issue might be?
Here is the traceroute
traceroute to files.pfsense.org (188.8.131.52), 30 hops max, 38 byte packets
1 cpe-107-184-48-1.socal.res.rr.com (184.108.40.206) 4203.306 ms 24.754 ms 32.390 ms
2 tge7-1.wmnsca1502h.socal.rr.com (220.127.116.11) 9.531 ms 18.527 ms 14.100 ms
3 tge8-1.wmnsca1501h.socal.rr.com (18.104.22.168) 10.271 ms 24.323 ms 13.905 ms
4 tge0-8-0-11.grgvcabt01r.socal.rr.com (22.214.171.124) 12.917 ms 30.706 ms 19.923 ms
5 agg23.lsancarc01r.socal.rr.com (126.96.36.199) 15.870 ms 12.696 ms 15.903 ms
6 bu-ether16.lsancarc0yw-bcr00.tbone.rr.com (188.8.131.52) 15.245 ms 12.958 ms 16.434 ms
7 184.108.40.206 (220.127.116.11) 11.428 ms 18.104.22.168 (22.214.171.124) 11.981 ms 126.96.36.199 (188.8.131.52) 24.257 ms
8 184.108.40.206 (220.127.116.11) 12.657 ms 12.420 ms 17.708 ms
9 vl-3602-ve-226.ebr2.Tustin1.Level3.net (18.104.22.168) 94.807 ms 110.689 ms vl-3601-ve-225.ebr2.Tustin1.Level3.net (22.214.171.124) 122.630 ms
10 ae-7-7.ebr3.LosAngeles1.Level3.net (126.96.36.199) 95.740 ms 94.986 ms 91.995 ms
11 ae-12-12.ebr1.Washington1.Level3.net (188.8.131.52) 98.723 ms 91.927 ms 95.128 ms
12 ae-4-4.ebr2.Newark1.Level3.net (184.108.40.206) 98.626 ms 93.544 ms 97.515 ms
13 ae-2-52.edge2.Newark1.Level3.net (220.127.116.11) 100.872 ms 93.391 ms 101.104 ms
14 THE-NEW-YOR.edge2.Newark1.Level3.net (18.104.22.168) 81.672 ms 97.045 ms 83.468 ms
15 cs20.cs59.v.jfk.nyinternet.net (22.214.171.124) 155.481 ms 168.097 ms 86.241 ms
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
You're not being blocked by us. Though that is odd, as the traceroute stops one hop up from our network. Our firewalls and servers will respond to UDP traceroute, so you should see the last hops. I presume the IP in question is the same one you're using here on the forum? I grepped the logs for that IP and came up empty, haven't seen anything from that address at NYI. Can you reach http://updates.nyi.pfsense.org?
Ah, updates.nyi.pfsense.org is unreachable as well.
Yeah, I tried a traceroute from a friends connection (same area/ISP) and it reports back just fine, so I thought maybe I somehow got accidentally blacklisted or something. Any idea what might be causing this? (or maybe a trusted mirror I can use instead?)
updates.nyi.pfsense.org cuts out in exactly the same place:
10 ae-7-7.ebr3.LosAngeles1.Level3.net (126.96.36.199) 82.335 ms 95.509 ms 85.629 ms
11 ae-12-12.ebr1.Washington1.Level3.net (188.8.131.52) 89.671 ms 89.388 ms 86.166 ms
12 ae-4-4.ebr2.Newark1.Level3.net (184.108.40.206) 85.063 ms 84.170 ms 85.515 ms
13 ae-2-52.edge2.Newark1.Level3.net (220.127.116.11) 82.438 ms 84.306 ms 84.892 ms
14 THE-NEW-YOR.edge2.Newark1.Level3.net (18.104.22.168) 82.726 ms 82.524 ms 82.637 ms
15 cs20.cs59.v.jfk.nyinternet.net (22.214.171.124) 88.010 ms 95.087 ms 89.923 ms
16 * * *
17 * * *
18 * * *
Any help here would be appreciated. It's my first time trying out pfSense but I can't seem to get anywhere if I can't install packages (and future updates)
Old IP: 126.96.36.199
New IP: 188.8.131.52
cmb, any idea?
Update: opened a ticket at NYI to see what the problem might be.
Got a response from NYI (great response time), they are saying it's a problem within the pfsense lan, copy/pasting what they said then attaching screen shot.
I've been trying to access one of the servers hosted by NYI but there seems to be an issue…
"We are looking into this case. "
"Hmm, we've traced from several locations and all looks fine in terms of the network config. We have no rules blocking access and the trace route you pasted seems to make it to our switch, which is an indication the issue exists within the LAN. "
Just a heads up, I also just tried from 184.108.40.206 and got the same result.
Yeah, it looks like you make it to the pfsense network from both locations. We don't have any insight into their network, so I think they have to take it from here. If you have someone that you are talking to from there that you want to add to this ticket in case there are any further steps we can provide to help with the trouble-shooting, let us know.
Can you run a constant ping to one of those IPs, and leave it running? I'll be able to see whether or not it's reaching us that way.
No problem, I left a ping open to 220.127.116.11
Thanks, you were in a black list that I missed. I see you're getting replies now, should be all good.
Yep! All is well now. Thanks for your help cmb