can't update pfsense or install packages

[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

[stephenw10]

And it's still failing with 'no route'?

It could be something upstream returning no-route. Try to ping pkg01-atx.netgate.com directly.

[mrrobot]

@stephenw10 the ping works fine

[2.6.0-RELEASE][admin@xxxx]/root: ping pkg01-atx.netgate.com
PING pkg01-atx.netgate.com (208.123.73.209): 56 data bytes
64 bytes from 208.123.73.209: icmp_seq=0 ttl=49 time=129.098 ms
64 bytes from 208.123.73.209: icmp_seq=1 ttl=49 time=133.544 ms
64 bytes from 208.123.73.209: icmp_seq=2 ttl=49 time=129.804 ms
^C
--- pkg01-atx.netgate.com ping statistics ---
4 packets transmitted, 3 packets received, 25.0% packet loss
round-trip min/avg/max/stddev = 129.098/130.815/133.544/1.951 ms

[stephenw10]

And it's still failing with 'no route'?

Try pkg-static -d4 update at the CLI.

[mrrobot]

@stephenw10 i see a permission denied now

[2.6.0-RELEASE][admin@pfSense.xxxx.local]/root: pkg-static -d4 update
DBG(1)[49613]> pkg initialized
Updating pfSense-core repository catalogue...
DBG(1)[49613]> PkgRepo: verifying update for pfSense-core
DBG(1)[49613]> PkgRepo: need forced update of pfSense-core
DBG(1)[49613]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense-core.sqlite'
DBG(1)[49613]> Request to fetch pkg+https://packages.netgate.com/pfSense_v2_6_0_amd64-core/meta.conf
DBG(1)[49613]> opening libfetch fetcher
DBG(1)[49613]> Fetch > libfetch: connecting
DBG(1)[49613]> Fetch: fetching from: https://pkg00-atx.netgate.com/pfSense_v2_6_0_amd64-core/meta.conf with opts "i4"
DBG(1)[49613]> Fetch: fetching from: https://pkg00-atx.netgate.com/pfSense_v2_6_0_amd64-core/meta.conf with opts "i4"
DBG(1)[49613]> Fetch: fetching from: https://pkg00-atx.netgate.com/pfSense_v2_6_0_amd64-core/meta.conf with opts "i4"
DBG(1)[49613]> Request to fetch pkg+https://packages.netgate.com/pfSense_v2_6_0_amd64-core/meta.txz
DBG(1)[49613]> opening libfetch fetcher
DBG(1)[49613]> Fetch > libfetch: connecting
DBG(1)[49613]> Fetch: fetching from: https://pkg00-atx.netgate.com/pfSense_v2_6_0_amd64-core/meta.txz with opts "i4"
DBG(1)[49613]> Fetch: fetching from: https://pkg00-atx.netgate.com/pfSense_v2_6_0_amd64-core/meta.txz with opts "i4"
DBG(1)[49613]> Fetch: fetching from: https://pkg00-atx.netgate.com/pfSense_v2_6_0_amd64-core/meta.txz with opts "i4"
pkg-static: https://pkg00-atx.netgate.com/pfSense_v2_6_0_amd64-core/meta.txz: Permission denied
repository pfSense-core has no meta file, using default settings
DBG(1)[49613]> Request to fetch pkg+https://packages.netgate.com/pfSense_v2_6_0_amd64-core/packagesite.pkg
DBG(1)[49613]> opening libfetch fetcher
DBG(1)[49613]> Fetch > libfetch: connecting
DBG(1)[49613]> Fetch: fetching from: https://pkg00-atx.netgate.com/pfSense_v2_6_0_amd64-core/packagesite.pkg with opts "i4"
DBG(1)[49613]> Fetch: fetching from: https://pkg00-atx.netgate.com/pfSense_v2_6_0_amd64-core/packagesite.pkg with opts "i4"
DBG(1)[49613]> Fetch: fetching from: https://pkg00-atx.netgate.com/pfSense_v2_6_0_amd64-core/packagesite.pkg with opts "i4"
pkg-static: https://pkg00-atx.netgate.com/pfSense_v2_6_0_amd64-core/packagesite.pkg: Permission denied
DBG(1)[49613]> Request to fetch pkg+https://packages.netgate.com/pfSense_v2_6_0_amd64-core/packagesite.txz
DBG(1)[49613]> opening libfetch fetcher
DBG(1)[49613]> Fetch > libfetch: connecting
DBG(1)[49613]> Fetch: fetching from: https://pkg00-atx.netgate.com/pfSense_v2_6_0_amd64-core/packagesite.txz with opts "i4"
DBG(1)[49613]> Fetch: fetching from: https://pkg00-atx.netgate.com/pfSense_v2_6_0_amd64-core/packagesite.txz with opts "i4"
DBG(1)[49613]> Fetch: fetching from: https://pkg00-atx.netgate.com/pfSense_v2_6_0_amd64-core/packagesite.txz with opts "i4"
pkg-static: https://pkg00-atx.netgate.com/pfSense_v2_6_0_amd64-core/packagesite.txz: Permission denied

.......
Error updating repositories!

[stephenw10]

Aha! Well that is almost always something blocking it.

Are you running Snort or Suricata? pfBlocker maybe? Check it's not blocking that traffic.

[mrrobot]

@stephenw10 i had to google all this tools to know about em, i don't have any of these
the router had only the os installed, i have been unable to install nothing else