New Netgate SG-1100 2.4.5-RELEASE-p1 Available Packages Empty
-
You can probably resolve it using the procedure I linked to above.
However having a copy of the firmware is always a good idea.
Steve
-
@stephenw10 - Yeah I tried all those no luck. I submitted a support ticket to get the latest version.
-
Exact same issue with a SG-1100 I received today 1/5/2021 direct from Netgate has the 2020 software.
2.4.5-RELEASE-p1 (arm64)
built on Tue Sep 15 10:30:40 EDT 2020
FreeBSD 11.3-STABLEFiled a support ticket, need that upgraded image.
-
Hmm, I tried to replicate this and couldn't. So to be clear this a was new 1100 dircelty from us that arrived with 2.4.5p1 installed.
You tried to update it during the initial deployment and it was unable to see the firmware update?
Like using the check for updates button in the setup wizard?Steve
-
Correct.
I’ve also tried from SSH using pkg-static (from link in your troubleshooting upgrade docs), it complains that the Repository pfsense-core missing. ‘pkg update’ required.
-
Using
pkg-static -d update
?Hmm it should pull in the updates if the meta file is missing. Can you get the output from that command?
Steve
-
[2.4.5-RELEASE][admin@iotfirewall.localdomain]/root: pkg-static -d update
DBG(1)[28836]> pkg initialized
Updating pfSense-core repository catalogue...
DBG(1)[28836]> PkgRepo: verifying update for pfSense-core
DBG(1)[28836]> PkgRepo: need forced update of pfSense-core
DBG(1)[28836]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense-core.sqlite'
DBG(1)[28836]> Fetch: fetching from: https://repo00.netgate.com/pkg/pfSense_factory-v2_4_4_aarch64-core/meta.conf with opts "i"
DBG(1)[28836]> Fetch: fetching from: https://repo01.netgate.com/pkg/pfSense_factory-v2_4_4_aarch64-core/meta.conf with opts "i"
DBG(1)[28836]> Fetch: fetching from: https://repo00.netgate.com/pkg/pfSense_factory-v2_4_4_aarch64-core/meta.conf with opts "i"
DBG(1)[28836]> Fetch: fetching from: https://repo00.netgate.com/pkg/pfSense_factory-v2_4_4_aarch64-core/meta.txz with opts "i"
DBG(1)[28836]> Fetch: fetching from: https://repo01.netgate.com/pkg/pfSense_factory-v2_4_4_aarch64-core/meta.txz with opts "i"
DBG(1)[28836]> Fetch: fetching from: https://repo00.netgate.com/pkg/pfSense_factory-v2_4_4_aarch64-core/meta.txz with opts "i"
pkg-static: https://repo.netgate.com/pkg/pfSense_factory-v2_4_4_aarch64-core/meta.txz: Bad Request
repository pfSense-core has no meta file, using default settings
DBG(1)[28836]> Fetch: fetching from: https://repo00.netgate.com/pkg/pfSense_factory-v2_4_4_aarch64-core/packagesite.txz with opts "i"
DBG(1)[28836]> Fetch: fetching from: https://repo01.netgate.com/pkg/pfSense_factory-v2_4_4_aarch64-core/packagesite.txz with opts "i"
DBG(1)[28836]> Fetch: fetching from: https://repo00.netgate.com/pkg/pfSense_factory-v2_4_4_aarch64-core/packagesite.txz with opts "i"
pkg-static: https://repo.netgate.com/pkg/pfSense_factory-v2_4_4_aarch64-core/packagesite.txz: Bad Request
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
DBG(1)[28836]> PkgRepo: verifying update for pfSense
DBG(1)[28836]> PkgRepo: need forced update of pfSense
DBG(1)[28836]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense.sqlite'
DBG(1)[28836]> Fetch: fetching from: https://repo00.netgate.com/pkg/pfSense_factory-v2_4_4_aarch64-pfSense_factory-v2_4_4/meta.conf with opts "i"
DBG(1)[28836]> Fetch: fetching from: https://repo01.netgate.com/pkg/pfSense_factory-v2_4_4_aarch64-pfSense_factory-v2_4_4/meta.conf with opts "i"
DBG(1)[28836]> Fetch: fetching from: https://repo00.netgate.com/pkg/pfSense_factory-v2_4_4_aarch64-pfSense_factory-v2_4_4/meta.conf with opts "i"
DBG(1)[28836]> Fetch: fetching from: https://repo00.netgate.com/pkg/pfSense_factory-v2_4_4_aarch64-pfSense_factory-v2_4_4/meta.txz with opts "i"
DBG(1)[28836]> Fetch: fetching from: https://repo01.netgate.com/pkg/pfSense_factory-v2_4_4_aarch64-pfSense_factory-v2_4_4/meta.txz with opts "i"
DBG(1)[28836]> Fetch: fetching from: https://repo00.netgate.com/pkg/pfSense_factory-v2_4_4_aarch64-pfSense_factory-v2_4_4/meta.txz with opts "i"
pkg-static: https://repo.netgate.com/pkg/pfSense_factory-v2_4_4_aarch64-pfSense_factory-v2_4_4/meta.txz: Bad Request
repository pfSense has no meta file, using default settings
DBG(1)[28836]> Fetch: fetching from: https://repo00.netgate.com/pkg/pfSense_factory-v2_4_4_aarch64-pfSense_factory-v2_4_4/packagesite.txz with opts "i"
DBG(1)[28836]> Fetch: fetching from: https://repo01.netgate.com/pkg/pfSense_factory-v2_4_4_aarch64-pfSense_factory-v2_4_4/packagesite.txz with opts "i"
DBG(1)[28836]> Fetch: fetching from: https://repo00.netgate.com/pkg/pfSense_factory-v2_4_4_aarch64-pfSense_factory-v2_4_4/packagesite.txz with opts "i"
pkg-static: https://repo.netgate.com/pkg/pfSense_factory-v2_4_4_aarch64-pfSense_factory-v2_4_4/packagesite.txz: Bad Request
Unable to update repository pfSense
Error updating repositories!
[2.4.5-RELEASE][admin@iotfirewall.localdomain]/root: -
Ok, thanks. Same error then.
Re-installing 21.05.2 clean will certainly get you to it fastest.
We are still looking into this.
Steve
-
One more detail. I am running the device inside of a LAN to create a secure subnet. In order to get access to the device on its default IP I disconnected the WAN port before going through the wizard and gave it a different subnet 192.168.20.0/24 - since the 192.168.1.0 subnet is already in use.
Perhaps that initial step of running the wizard when not connected to the WAN is the variation causing this issue? I’ll do the reinstall tomorrow with some fresh coffee.
-
Hmm, well it would certainly fail the check at that point but as long as the WAN was then connected and the subnets didn't conflict it should be OK.
-
I am up and running on the new firmware and all seems well. Thank you!
A couple of notes:
- Running Etcher on Windows 10. There is a known issue that causes it to fail validation of writing the flash drive. If you encounter that follow these steps.
https://superuser.com/questions/1199823/how-to-prevent-creation-of-system-volume-information-folder-in-windows-10-for/1199824#1199824
Burned an hour trying to check my stick for writing problems.
-
Had to manually install the Prolific USB serial driver for windows.
-
Install Instructions. Between Steps 6 and 7 there is ALOT of console output and reboots, this would be worth mentioning, that you should be patient (and not worry!) while it runs through these steps.
-
@stephenw10 said in New Netgate SG-1100 2.4.5-RELEASE-p1 Available Packages Empty:
https://docs.netgate.com/pfsense/en/latest/solutions/sg-1100/reinstall-pfsense.html
I am experiencing the exact same issue with a SG-1100 pfSense 2.4.5-RELEASE-p1 (arm64) ordered directly from Netgate. Received my unit about 14 days ago.
DNS is working properly for all domains except repo.netgate.com. DNS cannot resolve repo.netgate.com
*** Can't find repo.netgate.com: No answer
-
That's because it doesn't have a/aaaa records it uses SRV records, same as packages
https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html#packages-netgate-com-has-no-a-aaaa-recordYou see the same error from:
pkg-static -d update
?Steve
-
Hi @stephenw10 ,
Thanks for your reply. Any further recommendation you have would be much appreciated.The behavior is the same when using
pkg-static -d update
Here is the device output:
pkg-static -d update DBG(1)[25191]> pkg initialized Updating pfSense-core repository catalogue... DBG(1)[25191]> PkgRepo: verifying update for pfSense-core DBG(1)[25191]> PkgRepo: need forced update of pfSense-core DBG(1)[25191]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense-core.sqlite' DBG(1)[25191]> Fetch: fetching from: https://repo01.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-core/meta.conf with opts "i" DBG(1)[25191]> Fetch: fetching from: https://repo00.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-core/meta.conf with opts "i" DBG(1)[25191]> Fetch: fetching from: https://repo01.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-core/meta.conf with opts "i" DBG(1)[25191]> Fetch: fetching from: https://repo01.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-core/meta.txz with opts "i" DBG(1)[25191]> Fetch: fetching from: https://repo00.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-core/meta.txz with opts "i" DBG(1)[25191]> Fetch: fetching from: https://repo01.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-core/meta.txz with opts "i" pkg-static: https://repo.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-core/meta.txz: Bad Request repository pfSense-core has no meta file, using default settings DBG(1)[25191]> Fetch: fetching from: https://repo01.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-core/packagesite.txz with opts "i" DBG(1)[25191]> Fetch: fetching from: https://repo00.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-core/packagesite.txz with opts "i" DBG(1)[25191]> Fetch: fetching from: https://repo01.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-core/packagesite.txz with opts "i" pkg-static: https://repo.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-core/packagesite.txz: Bad Request Unable to update repository pfSense-core Updating pfSense repository catalogue... DBG(1)[25191]> PkgRepo: verifying update for pfSense DBG(1)[25191]> PkgRepo: need forced update of pfSense DBG(1)[25191]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense.sqlite' DBG(1)[25191]> Fetch: fetching from: https://repo01.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-pfSense_factory-v2_4_5/meta.conf with opts "i" DBG(1)[25191]> Fetch: fetching from: https://repo00.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-pfSense_factory-v2_4_5/meta.conf with opts "i" DBG(1)[25191]> Fetch: fetching from: https://repo01.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-pfSense_factory-v2_4_5/meta.conf with opts "i" DBG(1)[25191]> Fetch: fetching from: https://repo01.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-pfSense_factory-v2_4_5/meta.txz with opts "i" DBG(1)[25191]> Fetch: fetching from: https://repo00.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-pfSense_factory-v2_4_5/meta.txz with opts "i" DBG(1)[25191]> Fetch: fetching from: https://repo01.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-pfSense_factory-v2_4_5/meta.txz with opts "i" pkg-static: https://repo.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-pfSense_factory-v2_4_5/meta.txz: Bad Request repository pfSense has no meta file, using default settings DBG(1)[25191]> Fetch: fetching from: https://repo01.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-pfSense_factory-v2_4_5/packagesite.txz with opts "i" DBG(1)[25191]> Fetch: fetching from: https://repo00.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-pfSense_factory-v2_4_5/packagesite.txz with opts "i" DBG(1)[25191]> Fetch: fetching from: https://repo01.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-pfSense_factory-v2_4_5/packagesite.txz with opts "i" pkg-static: https://repo.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-pfSense_factory-v2_4_5/packagesite.txz: Bad Request Unable to update repository pfSense Error updating repositories!
-
Well as with the others the fastest way back to full function is to install 21.05.2 clean. Just open a ticket here: https://www.netgate.com/tac-support-request
Steve
-
For the record, I have the same issue. New SG-1100 since 5 days.
If I do a clean install, do I need to reconfigure eveyrthing? Just finished it until I noticed this issue
-
@dirkdooms I’m pretty sure you can back up your configuration to XML, do the reinstall, then restore that config.
-
Yes, back it up and restore it.
Or even pull it in from USB at first boot via the ECL:
https://docs.netgate.com/pfsense/en/latest/backup/restore-during-install.html#restore-using-the-external-configuration-locator-eclSteve
-
@dirkdooms said in New Netgate SG-1100 2.4.5-RELEASE-p1 Available Packages Empty:
I have the same issue. New SG-1100 since 5 days
Just for my own curiosity : Netgate delivers in 2022 their own devices with 2.4.5-p1 ?
-
Yep, I think the intent is you get the device, click the update firmware and that’ll bring you to current. Perhaps, they are shipping old stock, haven’t update the mfg process to flash the new image, …?
That update process is failing for folks on this thread and we had to do a manual reinstall.
That said, the device is wonderful and works very well; I’ll be getting a few more.