Upgrade to 2.4.2_1 fails if IPv6 used in WAN



  • Noticed that I could not upgrade to 2.4.2_1 if using ipv6 in wan
    the upgrade fails with message:
    [1/45] Fetching pfSense-kernel-pfSense-2.4.2_1.txz: ….... done
    pkg-static: https://pkg.pfsense.org/pfSense_v2_4_2_amd64-core/All/pfSense-kernel-pfSense-2.4.2_1.txz: Operation timed out
    Failed

    tried with to boxes and then I thought that what if the reason is the ipv6.
    Checked the netstat and noticed that the pfsense connects to the address 2610:1c1:0:6::40.443 (ipv6 address of the host files01.netgate.com) but not ipv4 address of the files00 or files01 servers.

    Disabled temporary the ipv6 and I was able to upgrade to the 2.4.2_1.

    The reason might be that while upgrading using ipv6 the request for some packages to the servers files00.netgate.com and files01.netgate.com is done by using the ip-addresses instead of hostname and web servers returns different folder to the client or then just that the web server returns a different folder upon ipv6 request...


  • Rebel Alliance Developer Netgate

    I have quite a few test boxes here that upgrade over IPv6 all the time. Perhaps your IPv6 connectivity is what's broken?



  • @jimp:

    I have quite a few test boxes here that upgrade over IPv6 all the time. Perhaps your IPv6 connectivity is what's broken?

    I wouldn't be surprised if there would be something fishy with my ISPs IPv6 implementation. The IPv6 Configuration Type for the WAN interface is dhcp6 and there's nothing special in the configuration itself… However the gateway monitoring reports latency issues with the wan_dhcp6 but that seems to be quite normal issue with the ipv6 and pfsense...


Log in to reply