(Solved) Packages list will not populate

pi

Ive just purchased & received a Netgate 1100. I followed the initial walk-through to get comms from my LAN to the ISP. I’m having trouble getting packages. When I select Available Packages and search for anything the GUI button is not responding or is responding with an empty search.

I’m on a Windows PC and have tried several browsers (Firefox, Edge, and IE) but they respond the same.

How do I troubleshoot this further?

———————————————

From the client device I can resolve the package URL.

 Start DNS Lookup
 Host: packages.pfsense.org
 packages.pfsense.org.	5M IN A
 208.123.73.88
 packages.pfsense.org.	5M IN AAAA
 2610:160:11:11::88

But I am not able to successfully ping the Package URL.

 PING 208.123.73.88 (208.123.73.88):
 56 data bytes 
 Request timeout for icmp_seq 0
 Request timeout for icmp_seq 1
 Request timeout for icmp_seq 2
 --- 208.123.73.88 ping statistics ---
 4 packets transmitted, 0 received,
 100.00% packet loss

When I run a trace route to 208.123.73.88 it fails after 208.123.73.4

 traceroute to 208.123.73.88
 5 relative hops max, 52 byte packets
 1  192.168.3.1  12.773 ms
 2  192.168.2.1  5.937 ms
 3  192.168.1.1  4.499 ms
 4  72.31.XXX.185  12.235 ms
 5  71.46.9.YYY  13.230 ms
 6  72.31.193.55. 19.407 ms
 7  72.31.220.176  19.903 ms
 8  72.31.188.176  21.312 ms
 9  66.109.6.128  25.499 ms
 10  4.68.111.185  19.819 ms
 11  * * *
 12  4.14.49.2  59.467 ms
 13  64.20.229.158  53.127 ms
 14  66.219.34.194  54.090 ms
 15  208.123.73.4  53.025
 16  * * *

————————————————-

From Pfsense GUI I can resolve the URL

DNS Lookup
Hostname: packages.pfsense.org
208.123.73.88 A
2610:160:11:11::88 AAAA
Name serverQuery time
45.90.XX.129 17 msec
45.90.YY.129 43 msec

I can’t ping the URL from the GUI

PING packages.pfsense.org
(208.123.73.88) 56 data bytes 36 bytes
from fw1-zcolo.netgate.com
(208.123.73.4): Destination Host
Unreachable
36 bytes from fw1-zcolo.netgate.com
(208.123.73.4): Destination Host
Unreachable
36 bytes from fw1-zcolo.netgate.com
(208.123.73.4): Destination Host
Unreachable
3 packets transmitted, 0 packets received, 100.0% packet loss

And trace route fails at the same place as the client device.

 1  192.168.1.1  0.583 ms
 2  72.31.XXX.185  8.244 ms 
 3  71.46.9.YYY  8.201 ms
 4  72.31.193.55  14.427 ms
 5  72.31.220.176  14.537 ms
 6  72.31.188.176  15.182 ms
 7  66.109.6.98  17.567 ms
 8  4.68.111.185  19.261 ms
 9  * * *
 10  4.14.49.2  46.204 ms
 11  64.20.229.158  48.574 ms
 12  66.219.34.194  47.599 ms
 13  208.123.73.4  49.289 ms
 14  * * *

Thanks for reviewing!

pi

I guess I headed down the wrong path with tracing the comms. The solution was updating the existing software in the Netgate. Although it showed I was on the latest build with 2.4.4 and no updates available there was an update that my device was not seeing, 2.4.5. I had to SSH into pfsense and force it to update. Now I see the catalog of packages.

Gertjan

Read - example - also https://forum.netgate.com/topic/115789/pkg-pfsense-org-appears-to-be-dead

Finding the A or AAAA and thus an IP .... would put you on the wrong track.

pi

@Gertjan
Very educating... thank you!