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

    Packages not working in 2.1 - SOLVED

    Scheduled Pinned Locked Moved 2.1 Snapshot Feedback and Problems - RETIRED
    1 Posts 1 Posters 1.0k 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.
    • C
      Criggie
      last edited by

      Posting for others to find a possible solution.

      I upgraded from 2.0 to 2.1 to get IPv6 support.  My ISP dishes out a /64 prefix and I wanted to use it.
      WAN gets a v6 address but it doesn't work yet.

      However packages would not list.  Available packages said "none available, can't contact www.pfsense.com, check DNS and gateway etc etc"

      A quick

      tcpdump -i pppoe0 port 443 or port 80
      

      while clicking "available packages" showed that the firewall was attempting to connect to pfsense.com's v6 address

      10:11:29.886561 IP6 2400:6900:3000:2:20d:b9ff:fe13:a364.25237 > 2605:8000:d:1::113 ecr 0], length 0
      

      which failed because ISP doesn't officially support it yet.

      However the package manager was not failing back to v4 mode.

      So the fix was to go to Services -> DNS then create a Host Override for www.pfsense.org and .com

      www  pfsense.com  69.64.6.21   
      www  pfsense.org  Alias for www.pfsense.com

      Once applied, the package manager was happy to use v4 IPs.

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