can't update pfsense or install packages

[mrrobot]

@jimp cant access any of the hosts

2.6.0-RELEASE][admin@pfSense.xxx.local]/root: host -t srv _https._tcp.packages.netgate.com
;; connection timed out; no servers could be reached
[2.6.0-RELEASE][admin@pfSense.xxx.local]/root: host pkg00-atx.netgate.com
;; connection timed out; no servers could be reached
[2.6.0-RELEASE][admin@pfSense.xxx.local]/root: host pkg01-atx.netgate.com
;; connection timed out; no servers could be reached

[jimp]

So your firewall can't resolve hosts via DNS, you need to investigate why and fix that.

[mrrobot]

@jimp any idea on how ?

[mrrobot]

@jimp i have reinstalled the system, tried different dns servers, restarted the dns resolver any of that helped

[jimp]

https://docs.netgate.com/pfsense/en/latest/troubleshooting/dns.html

[Dobby_]

@mrrobot said in can't update pfsense or install packages:

@jimp i have reinstalled the system, tried different dns servers, restarted the dns resolver any of that helped

Is your WAN Gateway the default gateway?

[mrrobot]

@jimp said in can't update pfsense or install packages:

https://docs.netgate.com/pfsense/en/latest/troubleshooting/dns.html

followed the guide, everything is ok only the last part of it where i do actually have lot of blocked traffic firewall logs

i didn't touch the firewall rules btw

[mrrobot]

@Dobby_ said in can't update pfsense or install packages:

Gateway the default gate

yes

[mrrobot]

@Dobby_ any ideas ?

[stephenw10]

You are still seeing DNS resolution errors?

Can you ping out by IP directly?

[mrrobot]

@stephenw10 yes even after a fresh install

[stephenw10]

So, yes, you are still seeing DNS errors.

Can you ping out by IP directly?

[mrrobot]

@stephenw10 dns resolution works fine though

[mrrobot]

@stephenw10

[stephenw10]

So what do you see if you run?: pkg-static -d update

[mrrobot]

@stephenw10 said in can't update pfsense or install packages:
for some reason i cant put all the code, it gets reported as spam so i put the end of it

pkg-static -d update

DBG(1)[94031]> Fetch: fetching from: https://pkg01-atx.netgate.com/pfSense_v2_6_0_amd64-pfSense_v2_6_0/meta.conf with opts "i"
DBG(1)[94031]> Fetch: fetching from: https://pkg01-atx.netgate.com/pfSense_v2_6_0_amd64-pfSense_v2_6_0/meta.conf with opts "i"
DBG(1)[94031]> Request to fetch pkg+https://packages.netgate.com/pfSense_v2_6_0_amd64-pfSense_v2_6_0/meta.txz
DBG(1)[94031]> opening libfetch fetcher
DBG(1)[94031]> Fetch > libfetch: connecting
DBG(1)[94031]> Fetch: fetching from: https://pkg01-atx.netgate.com/pfSense_v2_6_0_amd64-pfSense_v2_6_0/meta.txz with opts "i"
DBG(1)[94031]> Fetch: fetching from: https://pkg01-atx.netgate.com/pfSense_v2_6_0_amd64-pfSense_v2_6_0/meta.txz with opts "i"
DBG(1)[94031]> Fetch: fetching from: https://pkg01-atx.netgate.com/pfSense_v2_6_0_amd64-pfSense_v2_6_0/meta.txz with opts "i"
pkg-static: https://pkg01-atx.netgate.com/pfSense_v2_6_0_amd64-pfSense_v2_6_0/meta.txz: No route to host
repository pfSense has no meta file, using default settings
DBG(1)[94031]> Request to fetch pkg+https://packages.netgate.com/pfSense_v2_6_0_amd64-pfSense_v2_6_0/packagesite.pkg
DBG(1)[94031]> opening libfetch fetcher
DBG(1)[94031]> Fetch > libfetch: connecting
DBG(1)[94031]> Fetch: fetching from: https://pkg01-atx.netgate.com/pfSense_v2_6_0_amd64-pfSense_v2_6_0/packagesite.pkg with opts "i"
DBG(1)[94031]> Fetch: fetching from: https://pkg01-atx.netgate.com/pfSense_v2_6_0_amd64-pfSense_v2_6_0/packagesite.pkg with opts "i"
DBG(1)[94031]> Fetch: fetching from: https://pkg01-atx.netgate.com/pfSense_v2_6_0_amd64-pfSense_v2_6_0/packagesite.pkg with opts "i"
pkg-static: https://pkg01-atx.netgate.com/pfSense_v2_6_0_amd64-pfSense_v2_6_0/packagesite.pkg: No route to host
DBG(1)[94031]> Request to fetch pkg+https://packages.netgate.com/pfSense_v2_6_0_amd64-pfSense_v2_6_0/packagesite.txz
DBG(1)[94031]> opening libfetch fetcher
DBG(1)[94031]> Fetch > libfetch: connecting
DBG(1)[94031]> Fetch: fetching from: https://pkg01-atx.netgate.com/pfSense_v2_6_0_amd64-pfSense_v2_6_0/packagesite.txz with opts "i"
DBG(1)[94031]> Fetch: fetching from: https://pkg01-atx.netgate.com/pfSense_v2_6_0_amd64-pfSense_v2_6_0/packagesite.txz with opts "i"
DBG(1)[94031]> Fetch: fetching from: https://pkg01-atx.netgate.com/pfSense_v2_6_0_amd64-pfSense_v2_6_0/packagesite.txz with opts "i"
pkg-static: https://pkg01-atx.netgate.com/pfSense_v2_6_0_amd64-pfSense_v2_6_0/packagesite.txz: No route to host
Unable to update repository pfSense
Error updating repositories!
[2.6.0-RELEASE][admin@xxxxx]/root:

[stephenw10]

@mrrobot said in can't update pfsense or install packages:

No route to host

Ok, so it has no route. Check Diag > Routes. Make sure there's a valid default route.

Steve

[mrrobot]

@stephenw10 how do i know that the default route is valid ?

my wan interface ip is the one ending with 228 and its a public ip

looks like my isp giving me x.x.x.228 defaulting to a x.x.x.229 gateway

[stephenw10]

That looks valid. Does the gateway show as up?

Do you have an IPv6 address on any interfaces?
It could be trying to use IPv6. Try setting 'Prefer IPv4' in Sys > Adv > Networking.

Steve

[mrrobot]

@stephenw10 thank you
Gateway looks fine & Prefer IPv4 over IPv6 is checked