No Available Packages - Package Manager
-
Hi @Gertjan Sorry for late response. Just back from holiday..
This is my pfsense DNS.
This is my DNS resolver Settings.
Can you show Status > System Logs > System > DNS Resolver Can you find the word 'start' on that page ? Often ?
Nope. I dont find "start" on the page.
I have ping using CMD and this is the result.
-
-
That all looks good. Are you still seeing the same issues updating?
-
@stephenw10 Yes.
Still same. No package manager. -
Like
pkg-static -d updatestill fails? -
@stephenw10 Hi..
Still same..
What else should I do ?
![2023-12-18_13-16.png] -
I had a same issue. I didnt find way how to resolve that. For me the main things worked, so I keep router for few days, as I dont have time. After 4 days when I logged back, everything was working and I was able to install packages.
I do not know why that happen, I tried everything what was found on phorum without any luck. @stephenw10 can you check if there arent really some package service issues on your side? Maybe thats why there is also so many issues with upgrades..?
-
I FOUND A SOLUTION !!
I go to System > General Setup
I untick the DNS Server overide.
I add cloudflare dns.
Then save
At the system information, the button check for update appear.
Then I try revisited the package manager. It work fine !!
-
@linuxstudent1990 said in No Available Packages - Package Manager:
Nope. I dont find "start" on the page.
I presume you have this :
set to level 2 or 3. That means that every dns request will get flogged, and this flushes out the log fil really fast - like the line you've showed : just one second.This :
says your one 2.7.2
This :
says the same thing - the prompt says 2.7.2.
Then why the 2_7_1 repository is requested ?I stephenw10 doesn't know a correct command line solution for this one, I'll vote for the fast way out that will succeed without a hitch : get a copy of the config.xml, re install, import the copy of the config.xml and call it a day.
-
@GeorgeCZ58 I think I have solve this issue. It happen because of the DNS.
-
DNS did its work :
But true : never understood what these do on a firewall
pfSense doesn't need "them" to work.
You need public (company owned) DNS servers if your own company forces you make your DNS records public or you have a special uplink with high latency to root or tld DNS servers, and a more close by servers speeds things up a little bit.
pfSense doesn't need the DNS server it got from the upstream DHCP server (most probably it well send the IP of the ISP router, itself being a forwarder to an ISP DNS router).
Remember : public DNS servers, your ISP DNS servers are revolvers that use the Internet's root and DNS tld servers, something that pfSense also does with the resolver.Anyway, the issue right now is : pfSense is on 2.7.2. It's internal package database 'thinks' it's on 2.7.1.
-
Yes that^. Make sure you set the update branch to 2.7.2 because it appears you are running 2.7.2 but pulling packages from 2.7.1.
-
@GeorgeCZ58 I think I have solve this issue. It happen because of the DNS.
@Gertjan said in No Available Packages - Package Manager:
pfSense doesn't need the DNS server it got from the upstream DHCP server (most probably it well send the IP of the ISP router, itself being a forwarder to an ISP DNS router).
Remember : public DNS servers, your ISP DNS servers are revolvers that use the Internet's root and DNS tld servers, something that pfSense also does with the resolver.I also feeling weird. That dns are from my isp. After remove the DNS override. Its fix the problem.
-
Yes strange because you have the resolution behaviour set to use localhost (Unbound) by default and only fall back to remote servers.
It implies Unbound is failing yet you specifically tested that and it resolved OK.
