No route to host

Cool_Corona

Installing pfSense-pkg-bandwidthd...
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pkg-static: https://files00.netgate.com/pfSense_v2_5_1_amd64-pfSense_v2_5_1/meta.txz: No route to host
repository pfSense has no meta file, using default settings

Cool_Corona

Nothing in available packages running 2.5.0.

Cool_Corona

Installing pfSense-pkg-darkstat...
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pkg-static: https://files01.netgate.com/pfSense_v2_5_1_amd64-pfSense_v2_5_1/meta.txz: No route to host
repository pfSense has no meta file, using default settings

Gertjan

@cool_corona said in No route to host:

Nothing in available packages running 2.5.0.

It should be known by now that ;

Made easy :
First you assure yourself that you have the latest pfSense.
Only then you take a look at packages.

I guess "update" (a package) can be interchanged by "install", as these are identical actions.
The side effect of upgrading is that you will have a copy of your config, you did a pre reboot to start with a clean system, the upgrade, and the post reboot to have the dust settled in.
On the other side, if the package system is complaining, upgrading isn't probably an option neither.

The issue "No route to host" can be as simple as : your uplink is down, or anything else from this list.

This one is very popular : Troubleshooting a Broken pkg Database.

Cool_Corona

@gertjan I wont update to 2.5.1 since it has the MultiWAN issue.

Normally the same branch of releases has access to package repository

JeGr

@cool_corona said in No route to host:

@gertjan I wont update to 2.5.1 since it has the MultiWAN issue.

Normally the same branch of releases has access to package repository

It does:

Check your update path under System/Update (should be latest stable 2.5.x).

Also check your internet/DNS connectivity, as

pkg-static: https://files01.netgate.com/pfSense_v2_5_1_amd64-pfSense_v2_5_1/meta.txz: No route to host

"No route to host" clearly is an error that is local to you. Could perhaps be DNS related as the file-servers for packages are resolved via SRV records. Also check out via console:

[2.5.0-RELEASE][root@mirage.nt.ops.to]/root: pkg-static update
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pfSense repository is up to date.
All repositories are up to date.

pkg-static update should run without problem. I assume it doesn't for you?

Cheers