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

No packages since upgrade to 2.1-RC1

Scheduled Pinned Locked Moved 2.1 Snapshot Feedback and Problems - RETIRED
11 Posts 7 Posters 3.1k Views
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.
  • R
    randybarth
    last edited by Aug 7, 2013, 11:57 AM

    Since upgrading to 2.1-RC1, I no longer have access to packages. I can ping www.pfsense.org from pfsense but the log shows the following:

    php: /pkg_mgr.php: XML_RPC_Client: Connection to RPC server www.pfsense.com:80 failed. Operation timed out 103

    How can I recover my packages access?

    Thanks.

    1 Reply Last reply Reply Quote 0
    • K
      Klaws
      last edited by Aug 7, 2013, 12:04 PM

      You can ping www.pfsense.ORG, but can you also ping www.pfsense.COM?

      1 Reply Last reply Reply Quote 0
      • R
        randybarth
        last edited by Aug 7, 2013, 12:09 PM

        yes, both www.pfsense.org and www.pfsense.com are pingable via IPv4. Neither are pingable via IPv6. I can ping others (e.g. www.google.com) via IPv6 however.

        Perhaps the server has lost its IPv6 connectivity?

        1 Reply Last reply Reply Quote 0
        • R
          randybarth
          last edited by Aug 7, 2013, 12:30 PM

          I can work around problem by forcing www.pfsense.com to resolve to IPv4 address (192.207.126.26) in host overrides in DNS forwarder.

          It appears package manager code is unable to fallback to IPv4 if IPv6 path is unavailable.

          1 Reply Last reply Reply Quote 0
          • K
            Klaws
            last edited by Aug 7, 2013, 12:38 PM

            Hmm…ping seems to work for me:

            
            PING 2610:160:11:3:0:0:0:26(2610:160:11:3::26) 56 data bytes 
            64 bytes from 2610:160:11:3::26: icmp_seq=0 ttl=55 time=42.3 ms 
            64 bytes from 2610:160:11:3::26: icmp_seq=1 ttl=55 time=41.5 ms 
            64 bytes from 2610:160:11:3::26: icmp_seq=2 ttl=55 time=41.5 ms 
            64 bytes from 2610:160:11:3::26: icmp_seq=3 ttl=55 time=41.4 ms 
            
            --- 2610:160:11:3:0:0:0:26 ping statistics --- 
            4 packets transmitted, 4 received, 0% packet loss, time 3002ms 
            rtt min/avg/max/mdev = 41.487/41.745/42.399/0.378 ms, pipe 2 
            
            
            1 Reply Last reply Reply Quote 0
            • Z
              zenny
              last edited by Aug 7, 2013, 12:48 PM

              I just upgraded to August 6 build of NanoBSD 1g image. It can access the packages without any problem except pfBlocker upgrade does not work during OS upgrade seems to be broken since June 18 build.

              1 Reply Last reply Reply Quote 0
              • R
                randybarth
                last edited by Aug 7, 2013, 1:16 PM

                Must be something going on with Comcast IPv6 routing then. I'll investigate further. Thanks.

                1 Reply Last reply Reply Quote 0
                • A
                  andriusst
                  last edited by Aug 7, 2013, 2:21 PM

                  If you are on multi-wan setup ensure that one of the gateways is assigned as a default gateway. It is easy to miss after deleting and re-adding interfaces.

                  1 Reply Last reply Reply Quote 0
                  • J
                    jimp Rebel Alliance Developer Netgate
                    last edited by Aug 8, 2013, 12:33 PM

                    And if you have snort installed/enabled with blocking, make sure it's not blocking you from reaching the server as well.

                    Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                    Need help fast? Netgate Global Support!

                    Do not Chat/PM for help!

                    1 Reply Last reply Reply Quote 0
                    • C
                      c0urier
                      last edited by Aug 8, 2013, 11:36 PM Aug 8, 2013, 11:34 PM

                      Mine sounds like it's related to this.

                      If I upgrade to a Snapshot from August all IPv4 traffic stops working, I can't ping any address from any clients nor directly from pfSense, but IPv6 is working just fine.

                      IPv4 is received dynamically from my ISP.
                      IPv6 is static from HE.net.

                      pfsense: 2.1.5-RELEASE, AMD64
                      Running on: MB/CPU: ASUS P8H77-I / Core i3-2120T | MEM: 8GB DDR3 | HDD: WD Blue 120GB 2.5" SATA | WAN/LAN: Fujitsu D2735-2 – Intel® chip 82576NS | WLAN: Realtek® 8111F PCIe | Connection: 1000/1000Mbit (Bredband2.com)
                      [/U

                      1 Reply Last reply Reply Quote 0
                      • D
                        doktornotor Banned
                        last edited by Aug 9, 2013, 6:27 AM

                        @c0urier:

                        Mine sounds like it's related to this.

                        Cannot see how.

                        1 Reply Last reply Reply Quote 0
                        2 out of 11
                        • First post
                          2/11
                          Last post
                        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                          This community forum collects and processes your personal information.
                          consent.not_received