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

    Upgrade issue from 2.1-RC1 to 2.1-RELEASE

    Problems Installing or Upgrading pfSense Software
    1
    3
    1.3k
    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.
    • T
      tenortim
      last edited by

      I just upgraded from 2.1-RC1 (Sept 4 IIRC) to 2.1-RELEASE (Alix system).
      The gateway came back and is routing traffic fine, but the package system appears to be broken.
      Previously, I had pfBlocker installed, now it shows no packages installed.

      When I try to go to the Available Packages tab on packages page, it fails with the following error:
      Unable to communicate with www.pfsense.com. Please verify DNS and interface configuration, and that pfSense has functional Internet connectivity.
      and I see this in the logs
      php: /pkg_mgr.php: XML_RPC_Client: Connection to RPC server www.pfsense.com:80 failed. Operation timed out 103

      Yet I can connect to www.pfsense.com just fine.
      Also, the old package remnants are there e.g. I see this in the logs too:
      php: rc.filter_configure_sync: The command '/usr/bin/fetch -T 5 -q -o '/var/db/aliastables/pfBlockerTopSpammers.txt.tmp' 'https://127.0.0.1:443/pfblocker.php?pfb=pfBlockerTopSpammers'' returned exit code '1', the output was 'fetch: https://127.0.0.1:443/pfblocker.php?pfb=pfBlockerTopSpammers: Not Found'

      Any thoughts on how to clean this all up?

      –--
      update, I think something went slightly awry with my ipv6 setup. Logging into a shell on the gateway and trying to
      connect:
      [2.1-RELEASE][root@fw.internal.splhi.com]/root(2): telnet www.pfsense.com 80
      Trying 2610:160:11:3::26…

      So it's trying to use the ipv6 address and when I look at the gateway status, it shows my WAN_6TO4 gateway as down.
      I'll poke a bit here.

      1 Reply Last reply Reply Quote 0
      • T
        tenortim
        last edited by

        So, delete 6to4 settings, reboot and I can now get to the package manager (the timeout is way too short - when I left
        the telnet test going, it eventually gave up and tried the ipv4 address, but the packages PHP code times out long before
        that happens.

        Hmmm, is www.pfsense.com's ipv6 address down?

        I re-enabled ipv6 on WAN and LAN.
        I can get to other sites via ipv6 e.g.
        [2.1-RELEASE][root@fw.internal.splhi.com]/root(6): telnet ipv6.test-ipv6.com 80
        Trying 2001:470:1:18::119…
        Connected to ipv6.test-ipv6.com.
        Escape character is '^]'.

        But when I try to get to www.pfsense.com as an ipv6 address, it fails:
        [2.1-RELEASE][root@fw.internal.splhi.com]/root(5): telnet www.pfsense.com 80
        Trying 2610:160:11:3::26…
        telnet: connect to address 2610:160:11:3::26: Operation timed out
        Trying 192.207.126.26...
        Connected to www.pfsense.org.

        1 Reply Last reply Reply Quote 0
        • T
          tenortim
          last edited by

          The other oddity with 6to4 is that the apinger gateway monitor thinks it's down:

          | Name | Gateway | Monitor | RTT | Loss | Status | Description |
          | WAN_6TO4 | 2002:c058:6301:: | 2002:c058:6301:: | 0ms | 100% | Offline
          Last check:
          Sun, 15 Sep 2013 15:06:14 -0700 | Interface WAN_6TO4 Gateway |

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.