How did you upgrade to 23.05.1 if repo is missing
-
I have exactly the same issue!
I installed 2.6CE via USB install on my Intel v226 box - which does not work due to missing drivers (I forced the install with an USB NIC workaround).
So I upgraded to pfsense plus which landed me on 23.05 including Intel v226 support.
I did that last week. Now my package mangement and my branch is both missing and broken.
Any news on that?!
Screenshot from todays: https://firmware.netgate.com/pkg/
-
@sttwebs Exactly the same experience and the same hw. Intel 226 2.5g. Installed pf 2.6, upgraded to 23.05 for hw support. Branch is empty now and the repo is wrong.
I don't know how people managed to update to 23.05.1 on amd64 arch and with what type of repo or packages.I think maybe they use different servers and there is some sort of difference between files hosted on america or europe.
firmware.netgate.com has 2 a records: 208.123.73.207 and 208.123.73.209 -
@xgiovio it looks like their "inplace upgrade to plus" is very bugged. I had a quick VM installation with 2.7 CE which points to a new repo which is located at "pkg.pfsense.org" - SADLY you can't browse it.
Since this is getting a bit strange to me, I will go the extra mile and reinstall my pfSense with 2.7 - which is FreeBSD 14 based - WHICH includes the v226 drivers ;-)
This is very frustrating, but oh well. I will gladly keep you posted how this will turn out.
-
@sttwebs the repo you sais is only for resolving srv records.
The srv records for _https._tcp.pkg.pfsense.org are
https://pkg00-atx.netgate.com/
https://pkg01-atx.netgate.com/They are browsable and contain 2.x branch.
Even the srv records for firmware.netgate.com are the same so i can't uderstand where is the repo for 23.05 and 23.05.1.
-
@sttwebs I talked with the support. I think i uderstood what happened.
When you upgraded to the 23.05 it recognized a new network interface. This changed the nid (netgateid). I think this is important when you go to the update section to select the new branch.So when you go to the update section, now it says there is no new update because the nid you have now is different from the nid it was registered on their server when you did the converstion to the plus.
Not seeing a valid nid, it doesn't propose a branch update.If you ask the support to update your nid (you can find it on the pfsense home dashboard) they will replace it remotely and now you can do the update.
I think this update works in this way because they have to monitor what device updates with the ce or plus license.
-
@xgiovio oh this is VERY interessting! Thank you. I opened a ticket now.
-
@xgiovio Thanks for this guidance. I switched out my network card and couldn't figure why I couldn't update the version or get any packages to install. Getting a new activation token and then choosing the Previous Stable Version of 23.01 and then the Latest Stable Version 23.05.1 showed up as an installation option. This also fixed my package manager not allowing me to install any packages.
-
@kjacques1 yes, getting a new activation token creates a new plus license entry in their server database and so it works. The alternative is to ask to replace the old nid with the new one. I lost different days to understand why but now it is all clear also for me.
-
@xgiovio said in How did you upgrade to 23.05.1 if repo is missing:
The alternative is to ask to replace the old nid with the new one. I lost different days to understand why but now it is all clear also for me.
We will update records for TAC Pro and TAC Enterprise subscribers once TAC Lite and Home/Lab users can request new licenses from https://shop.netgate.com/products/pfsense-software-subscription.
An NDI can change from the following causes:
- User added a NIC
- ... removed a NIC
- ... swapped a NIC (new MAC address)
- ... moved a VM from one host to another
- ... exported and re-imported a VM on the same host
- ... installed pfSense CE and then Plus on a system with i226 NICs and upgraded to 23.x where those NICs are now visible to pfSense Plus
- ... user installed/removed/lost a USB-based NIC
-
@rcoleman-netgate So if someone updates anything from that list shouldn't contact support but buy a new free license each time?
-
@xgiovio Sure but as I noted we will move Professional and Enterprise subscriptions one time during the subscription period. But the terms on those subscriptions do dictate no transfers.
If you are not a TAC Professional or TAC Enterprise subscriber... the TAC Lite license is still free (at the time of commenting) so there's no reason to get a new one. It's the least painful path.