• 0 Votes
    6 Posts
    868 Views
    planedropP
    @markchen Awesome, glad that solved it!
  • 0 Votes
    8 Posts
    2k Views
    S
    @rhammondwtg It sounds like they're working on adding a check to look for routers with the small partition (referenced in your link) and stopping the upgrade. That will let everyone else upgrade safely. But in the meantime it's off, so those of us with early-release models aren't left with a non-functioning router. So, manual (re)install, or wait.
  • 0 Votes
    4 Posts
    987 Views
    bmeeksB
    @araujovitorpaulo said in Help trying to get a new repo on my 2.4.4 p1: @NollipfSense that was an alternative at the beginning, but when I search for updates, it says that the server is up to date (http://prntscr.com/rrnrc0). The only way to recover it is making a brand new server with the 2.4.4p3 installation? 2.4.5 is the new current version. Unless you have an existing copy of the 2.4.4_p3 install media, it is no longer available from official sources. You may find unofficial copies out there someplace on the web, but I would be wary of such things. You can do a frresh install using 2.4.5 media and import your existing configuration. There are instructions for doing that in the Netgate docs.
  • 0 Votes
    6 Posts
    2k Views
    kiokomanK
    it's the unofficial repos for e2guardian you need to uninstall e2guardian you need to restore /etc/inc/pkg-utils.orig or revert the 244_unofficial_packages_list.patch from System_Patches and delete /usr/local/etc/pkg/repos/Unofficial.conf to remove that
  • 0 Votes
    7 Posts
    2k Views
    W
    Hi jimp, some good news here. Your statement that "pkg can't reach the pfsense servers" pointed me to the right direction; I haven't understood it fully, but I found a way at least to unlock the pkg issue. In my case, it was due to a double stack IPv4/IPv6 issue: to solve it, I had to temporaly disable the network interface linked to the GIF port; removing IPv6 name resolution plus removing the IPv6 default gateway and firewall rules to route IPv6 traffic didn't suffice. I don't like to be so inaccurate in test results, but as IPv6 connectivity was actually working, defining this problem will require some more tests and I meant to find a quick workaround for everybody experiencing this kind of issue. Let me know if this rings a bell.