Surprised, No Available Packages
-
Well after some hiccups with not getting anything on the monitor, I finally have a cleaner installed version...available packages now normal.
-
I've done the same test on my side.
I didn't have any issues, but saw something strange while posting here :and that's new : I'm reaching the forum over IPv4 .... normally, it's IPv6 for years now.
I've checked using several tools to check my IPv6 connection, like this one https://test-ipv6.com/ and Googlev6. All well.This :
[23.05.1-RELEASE][root@pfSense.bhf.net]/root: pkg-static -4 -d update
finished in a fraction of a second.
[23.05.1-RELEASE][root@pfSense.bhf.net]/root: pkg-static -6 -d update
takes minutes ..... (I'll wait to see if it times out, or is just very slow / bad )
pfSense (GUI etc) will prefer and use IPv6 if both are declared present ...
Probably the IPv6 between the old world and the newer one.
Can some one from the US, or Texas, confirm ?[23.05.1-RELEASE][root@pfSense.bhf.net]/root: dig pfsense-plus-pkg00.atx.netgate.com A +short 208.123.73.207 [23.05.1-RELEASE][root@pfSense.bhf.net]/root: dig pfsense-plus-pkg00.atx.netgate.com AAAA +short 2610:160:11:18::207
edit :
eventually, while using the "-6" option :... Unable to update repository pfSense Error updating repositories!
again, IPv4 worked well.
Btw : where is my "sometimes, it's not DNS" t-shirt ?
-
Yeah, same here. IPv4 works fine, IPv6 is down. This is with Aussie Broadband in Australia.
-
@Vollans said in Surprised, No Available Packages:
This is with Aussie Broadband in Australia
Definitely the new world for me, but we share the same "under water" link to the destination.
Thanks for the feed back. -
@Gertjan It seems to get stuck once it gets to CoreNap’s network.
Traceroute6 to pfsense-plus-pkg00.atx.netgate.com (2610:160:11:18::207) from 2403:580d:7fff:6824:<redacted>, 64 hops max, 28 byte packets 1 * fe80::2a2:ff:feb2:c2%igc3 9.781 ms * 2 * * * 3 ae-36.a00.sydnau05.au.bb.gin.ntt.net 33.349 ms 30.772 ms 21.186 ms 4 lag-6.ear1.Tokyo4.Level3.net 25.018 ms 40.442 ms 26.179 ms 5 * * * 6 NETWORK-APP.edge1.Washington1.Level3.net 237.627 ms 237.859 ms 237.900 ms 7 2610:160::ffff:4014:e5a6 223.901 ms 215.223 ms 219.037 ms 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * *
-
G Gertjan referenced this topic on
-
Things don't get any better :
-
@Gertjan said in Surprised, No Available Packages:
Btw : where is my "sometimes, it's not DNS" t-shirt ?
Ha. Lies! It's always DNS.
Though I'm also unable to hit the pkg server over v6 from the UK. Digging....
-
@stephenw10 Appears someone has dried out the cable, as I can get updates this morning.
-
Yup, local v6 routing issue has been resolved.