No available packages or branches - 23.09.1
-
The list in
System / Package manager / Available packages
is empty.I'm running pfSense + 23.09.1 .
I searched the forums and found a few commands that were suggested, but they did not work. Also references to IPv6 . The ISP I am using at the moment only supports IPv4.
I see a notice that "Package reinstall process was ABORTED due to lack of internet connectivity" . But that is not the case. I'm typing this on a wired PC connected to the Internet through pfSense.
I also cannot see any branches in the "branch" drop-down list at
System / Update / System UpdateHow can I refresh the package list ? Or see branches ?
-
@madbrain is your Plus license still active?
-
@SteveITS does it expire? How would I check ? I upgraded from pfSense to + last year for free.
-
@madbrain I found the activation token in my email from last year. Registered again. It's working fine now.
It is quite a surprise to see that there is no longer a free version of pfSense +. -
@madbrain fyi https://www.netgate.com/blog/addressing-changes-to-pfsense-plus-homelab
-
@SteveITS yes, I just read that. Disappointing. I guess my license got unregistered when I restored my settings from backup.
I'm using pfSense at home. What is the downgrade path from Plus to CE ? -
@madbrain I don’t know if there’s a way to downgrade yet without installing CE.
https://docs.netgate.com/pfsense/en/latest/backup/restore-different-version.html
-
Hmm, you just re-registered using the existing token? Interesting. That shouldn't ever be required if it had previously been registered.
-
@stephenw10 Yes, that's what I did. No idea why I had to, but it was required to fix my issue.
-
@stephenw10 said in No available packages or branches - 23.09.1:
Hmm, you just re-registered using the existing token? Interesting. That shouldn't ever be required if it had previously been registered.
I think I know what happened. Before installing pfSense, I disabled the motherboard 1Gbe NIC in the UEFI. I only needed 2 NICs and those needs were served by an Intel X550-T2.
Earlier this week, I experimented with dual WAN. This required a third NIC. So, I enabled the motherboard NIC in the UEFI.It's pretty lame if a BIOS setting change can invalidate the license ...
-
@madbrain said in No available packages or branches - 23.09.1:
It's pretty lame if a BIOS setting change can invalidate the license ...
Microsoft can invalide a Windows license when you change hardware of your device ...
-
@madbrain the NDI is calculated at least partly by the NICs, and the license is tied to the NDI.
-
@Gertjan Yes, they can, but I have only seen it happen when the CPU / motherboard changes. Not adding or removing a NIC through a BIOS setting.
-
@SteveITS I see. Today, I added a 4th NIC, a PCI-E I-225V (B3). The NIC works great. However, my Plus license has been invalidated again. And unlike the last time 12 days ago when I added a NIC with a BIOS setting change, using the activation token I got a year ago did not work, unfortunately.
Is there anything that can be done to fix ? My understanding was that existing users of pfSense Plus Home+Lab would be able to continue using the software. Not being able to update or install packages is a pretty big problem.
-
@madbrain You can reach out to Netgate TAC and ask but I wouldn’t get my hopes up. If you expect to be changing hardware I would just use CE and avoid this problem.
-
Send me the order number and NDI in chat and I can check it.
