Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Files.pfsense.org blocked?

    General pfSense Questions
    2
    10
    2.0k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • N
      nullyb
      last edited by

      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 (66.111.2.167), 30 hops max, 38 byte packets
      1  cpe-107-184-48-1.socal.res.rr.com (107.184.48.1)  4203.306 ms  24.754 ms  32.390 ms
      2  tge7-1.wmnsca1502h.socal.rr.com (76.166.13.177)  9.531 ms  18.527 ms  14.100 ms
      3  tge8-1.wmnsca1501h.socal.rr.com (72.129.29.176)  10.271 ms  24.323 ms  13.905 ms
      4  tge0-8-0-11.grgvcabt01r.socal.rr.com (72.129.29.162)  12.917 ms  30.706 ms  19.923 ms
      5  agg23.lsancarc01r.socal.rr.com (72.129.29.0)  15.870 ms  12.696 ms  15.903 ms
      6  bu-ether16.lsancarc0yw-bcr00.tbone.rr.com (66.109.6.102)  15.245 ms  12.958 ms  16.434 ms
      7  107.14.19.86 (107.14.19.86)  11.428 ms  107.14.19.138 (107.14.19.138)  11.981 ms  107.14.19.86 (107.14.19.86)  24.257 ms
      8  66.109.9.122 (66.109.9.122)  12.657 ms  12.420 ms  17.708 ms
      9  vl-3602-ve-226.ebr2.Tustin1.Level3.net (4.69.158.85)  94.807 ms  110.689 ms  vl-3601-ve-225.ebr2.Tustin1.Level3.net (4.69.158.81)  122.630 ms
      10  ae-7-7.ebr3.LosAngeles1.Level3.net (4.69.153.225)  95.740 ms  94.986 ms  91.995 ms
      11  ae-12-12.ebr1.Washington1.Level3.net (4.69.132.82)  98.723 ms  91.927 ms  95.128 ms
      12  ae-4-4.ebr2.Newark1.Level3.net (4.69.132.102)  98.626 ms  93.544 ms  97.515 ms
      13  ae-2-52.edge2.Newark1.Level3.net (4.69.156.41)  100.872 ms  93.391 ms  101.104 ms
      14  THE-NEW-YOR.edge2.Newark1.Level3.net (4.30.130.234)  81.672 ms  97.045 ms  83.468 ms
      15  cs20.cs59.v.jfk.nyinternet.net (64.147.125.126)  155.481 ms  168.097 ms  86.241 ms
      16  *  *  *
      17  *  *  *
      18  *  *  *
      19  *  *  *
      20  *  *  *
      21  *  *  *
      22  *  *  *
      23  *  *  *
      24  *  *  *
      25^C

      1 Reply Last reply Reply Quote 0
      • C
        cmb
        last edited by

        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?

        1 Reply Last reply Reply Quote 0
        • N
          nullyb
          last edited by

          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 (4.69.153.225)  82.335 ms  95.509 ms  85.629 ms
          11  ae-12-12.ebr1.Washington1.Level3.net (4.69.132.82)  89.671 ms  89.388 ms  86.166 ms
          12  ae-4-4.ebr2.Newark1.Level3.net (4.69.132.102)  85.063 ms  84.170 ms  85.515 ms
          13  ae-2-52.edge2.Newark1.Level3.net (4.69.156.41)  82.438 ms  84.306 ms  84.892 ms
          14  THE-NEW-YOR.edge2.Newark1.Level3.net (4.30.130.234)  82.726 ms  82.524 ms  82.637 ms
          15  cs20.cs59.v.jfk.nyinternet.net (64.147.125.126)  88.010 ms  95.087 ms  89.923 ms
          16  *  *  *
          17  *  *  *
          18  *  *  *

          1 Reply Last reply Reply Quote 0
          • N
            nullyb
            last edited by

            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)

            1 Reply Last reply Reply Quote 0
            • N
              nullyb
              last edited by

              Just to add an update, I forcibly got a new IP address from my ISP and I still can't access files.pfsense.org (or anything beyond cs20.cs59.v.jfk.nyinternet.net)

              Old IP: 107.184.49.173
              New IP: 107.184.61.183

              cmb, any idea?

              Update: opened a ticket at NYI to see what the problem might be.

              1 Reply Last reply Reply Quote 0
              • N
                nullyb
                last edited by

                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 107.184.61.56 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.

                nyi.png
                nyi.png_thumb

                1 Reply Last reply Reply Quote 0
                • C
                  cmb
                  last edited by

                  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.

                  1 Reply Last reply Reply Quote 0
                  • N
                    nullyb
                    last edited by

                    No problem, I left a ping open to 66.111.2.167

                    1 Reply Last reply Reply Quote 0
                    • C
                      cmb
                      last edited by

                      Thanks, you were in a black list that I missed. I see you're getting replies now, should be all good.

                      1 Reply Last reply Reply Quote 0
                      • N
                        nullyb
                        last edited by

                        Yep!  All is well now.  Thanks for your help cmb

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post