@nrb mobile network of #AS8881 or #IPv6only setup local network?
@hallunke23 Btw, there are already plenty of #IPv6only websites (see https://www.vypiname.cz/en/ for a list of those I’m aware of). And Czech Republic has a policy in place that demands the state to work on fully deploying #IPv6 (this is centrally coordinated and monitored, annual reports are available to the public) and to *shut down* #IPv4 on 2032-06-06 (this concerns all state services).

@tschaefer Ah the fruits of the @nlnet #NGI0 funding #ipxlat

https://codeberg.org/IPv6-Monostack/ipxlat
This one is aiming for inclusion in the kernel.

Depending on the deployment you need one or the other or two components.

e.g. with NAT46 kernel module as CLAT and Jool/TAYGA as PLAT one can build a #IPv6only deployment stack for running an ISP.

ipxlat

Kernel SIIT device for building 464XLAT, NAT64 and SIIT-DC networks

Codeberg.org
@generalx I use bunny so people that are stuck on #IPv4 can access my #IPv6only only content. I’ve moved on having to support legacy protocols and port redirection cludge. #IPv6

Habe soeben meine Liste, der mich am meisten nervenden Internetmängel aktualisiert.
Vodafoneroaming als großes Problem habe ich runtergenommen, da es bei den letzten Reisen funktioniert hat.
Samknows (die Whitebox) habe ich verschrottet. Das Cisco-Projekt stirbt schon seit Jahren vor sich hin.
WLAN-Call habe ich auch runtergenommen, weil ich ja nun weiß, woran es gelegen hat. Der Workaround ist zwar hässlich aber er funktioniert wenigstens.

https://tschaefer.dynv6.net/m%C3%A4ngelliste.txt

#ipv6only

Yes and No.
#IPv6 rollout is going way to slow. Reason for that is the network effect which is still stronger on legacy #IPv4 than on #IPv6. Still, we have almost reached the 50% mark and at some point in the next few years, we will reach the point where it will become politically feasible for some actors to go #IPv6only. When that happens, the network effect will tip. I'm not sure when exactly that tipping point is going to happen but I think it will happen (1/2)
@ironicbadger @Tubsta
Hi @webmontagkiel @sabrinkmann,
scheitert an #IPv6Only Servern wie z.B. @marcus. Das https://Seppo.mro.name/aseppototry/apchk.cgi kann's und sagt, was es macht.
Neugierdehalber: Was ist der UseCase für Non-Admins?
#1107302 - New upstream fork - Debian Bug report logs

ugh so i've managed to go 2 evenings with #ipv4 disabled on my laptop (#ipv6 only) but now I need to read tickets and commits on #btrfs repo on github so I can learn what support there is or will be in the future for disk groups.
So I managed two days of #ipv6only.

Hi @admin and @grunfink
trying to follow from @marcus has no effect and a closer look via console yields

```sh
$ fgrep eupolicy /var/log/daemon.log
r 12 10:38:16 n0 snac[60728]: 10:38:16 output message: sent to inbox https://eupolicy.social/inbox (503 Service Unavailable) [{"error":"Fetching attempt skipped because of recent connection ...]
```

Is there anything I can do about it? (It's a #IPv6Only host)