2024-10-31T00:14:29  <acidsys> about:config => network.http.fast-fallback-to-IPv4 => false
2024-10-31T00:16:48  <matrix-o-o> <Firstyear (Firstyear)> Thanks, will try that.
2024-10-31T00:53:02  *** teepee_ is now known as teepee
2024-10-31T15:18:41  *** teepee_ is now known as teepee
2024-10-31T19:22:21  <matrix-o-o> <Emma [it/its]> is matrix.o.o okay?
2024-10-31T19:24:05  <matrix-o-o> <Emma [it/its]> nevermind, seems all is good
2024-10-31T22:06:33  *** teepee_ is now known as teepee
2024-10-31T23:12:34  <matrix-o-o> <Firstyear (Firstyear)> acidsys: "2a07:de40:b27e:64::/96 dev vtun4 metric 1024 pref medium" I smell someone trying nat64
2024-10-31T23:25:24  <acidsys> what do you mean trying? this has always been there and is the route needed to reach sites using legacy IP.
2024-10-31T23:33:38  <matrix-o-o> <Firstyear (Firstyear)> https://blog.apnic.net/2024/10/22/the-ipv6-transition/ acidsys I think you'll find this interesting from one of the most senior people at apnic
2024-10-31T23:37:53  <acidsys> good read
2024-10-31T23:38:29  <matrix-o-o> <Firstyear (Firstyear)> Yeah, I got to see the "live version" when he presented that talk at a conf here
2024-10-31T23:38:57  <matrix-o-o> <Firstyear (Firstyear)> It's interesting to see them transition from ipv6/dnssec evangelist to dnssec basher and ipv6 apathist.
2024-10-31T23:40:11  <matrix-o-o> <Firstyear (Firstyear)> Here we have a mobile telco that is ipv6 only to phones, but runs massive nat64 gateways so people can get to v4 content. And we have plenty of ISP's with CGNAT for v4 too.
2024-10-31T23:40:45  <acidsys> yes, it's annoying that popular services run by big companies are still not reachable over IPv6. the biggest use case for NAT46 in our infra is for machines needing access to github.com
2024-10-31T23:41:22  <matrix-o-o> <Firstyear (Firstyear)> That would be nat64 not 46
2024-10-31T23:41:31  <matrix-o-o> <Firstyear (Firstyear)> But also, does that matter? If it works, it works.
2024-10-31T23:41:43  <acidsys> we have both directions
2024-10-31T23:41:52  <matrix-o-o> <Firstyear (Firstyear)> I used to run nat64 and tried to do v6 only, but after my ISP changed my prefix twice in a year, I cracked the shits
2024-10-31T23:42:03  <matrix-o-o> <Firstyear (Firstyear)> Very hard to operate anything if your prefix changes.
2024-10-31T23:42:27  <acidsys> that's also annoying ISPs which give dynamic prefixes or much smaller prefix sizes than recommended by standards
2024-10-31T23:42:45  <matrix-o-o> <Firstyear (Firstyear)> I wish there was better support for ipv6 nat so I could do ULA for internal stuff without having to worry about prefix changes.
2024-10-31T23:42:48  <acidsys> my ISP gives me 2 /48's :)
2024-10-31T23:42:52  <matrix-o-o> <Firstyear (Firstyear)> My prefix is large at least, and static now.
2024-10-31T23:43:03  <matrix-o-o> <Firstyear (Firstyear)> But if I move house, it'll chang.
2024-10-31T23:45:07  <acidsys> yes that's one use case I also have not found a good solution for. if you have a company who is partner with a RIR, they can sponsor to get a static GUA allocation. but it's not really approachable for the average home user
2024-10-31T23:45:30  <acidsys> static as in one that can move. but then the next challenge is to find a ISP who allows you to bring your own GUA
2024-10-31T23:45:41  <matrix-o-o> <Firstyear (Firstyear)> Not many
2024-10-31T23:46:37  <matrix-o-o> <Firstyear (Firstyear)> So within my home, I mostly do ipv4 internally, I have v6 for internet and stuff that needs it. I dropped nat64, since I have dual stack anyway,
2024-10-31T23:46:48  <matrix-o-o> <Firstyear (Firstyear)> I used to try to do v6 only, but it's such a hassle in the end.
2024-10-31T23:47:58  <acidsys> in a server infrastructure I think it works well
2024-10-31T23:48:15  <matrix-o-o> <Firstyear (Firstyear)> v6?
2024-10-31T23:48:23  <acidsys> single stack v6 yes
2024-10-31T23:48:41  <matrix-o-o> <Firstyear (Firstyear)> docker :P
2024-10-31T23:48:48  <matrix-o-o> <Firstyear (Firstyear)> royally ruins that.
2024-10-31T23:49:16  <acidsys> docker I have a bug since ages that when you have IPv6 nameservers in /etc/resolv.conf on the host, inside the container it will write google nameservers and send your queries there
2024-10-31T23:49:31  <acidsys> with podman it works well
2024-10-31T23:49:55  <acidsys> our gitlab.i.o.o runners have their own container prefixes
2024-10-31T23:50:04  <matrix-o-o> <Firstyear (Firstyear)> podman has other issues that make it impossible for me to use
2024-10-31T23:58:06  <matrix-o-o> <Firstyear (Firstyear)> Anyway acidsys next kanidm update has support for custom icons etc. So no more mounting the images in :)
2024-10-31T23:58:25  <acidsys> good stuff)
2024-10-31T23:59:36  <matrix-o-o> <Firstyear (Firstyear)> Faster ui loading too
2024-10-31T23:59:45  <matrix-o-o> <Firstyear (Firstyear)> Once I can get it into leap that is.
2024-10-31T23:59:48  <matrix-o-o> <Emma [it/its]> bleh i should restart my matrix client