αxel simon ↙︎↙︎↙︎Next year, #FOSDEM will be IPv6 only.
So Github will break, as it is IPv4 only (unless they get their act together).
T_X@axx I actually misunderstood the two WiFis, I think: I had selected the "FOSDEM-Dualstack" WiFi as I thought "of course I want IPv6!". Only through the closing event presentation I realized that the "FOSDEM" WiFi (without the "-Dualstack") actually has IPv6 as well - just that it was IPv6-mostly?
@axx (and not to reduce the pressure on Github etc. But I understood that remark in the closing event as the default "FOSDEM" WLAN would be IPv6 only - but not that there wouldn't be an extra "FOSDEM-Dualstack" WiFi again? But maybe I misunderstood.)
Richard "RichiH" Hartmann@T_X @axx I made the switch to #NAT64-only on the default network of #FOSDEM 13(?) years ago. It broke So. Much. Stuff.
I knew the former maintainer of the network tooling from the Linux Kernel Summit, and ran into him by chance that year. #Ubuntu was completely broken on NAT64-only, it did not even bring up the network interfaces, and we sent people who came to the NOC to their booth.
I also sent that former maintainer over there.
They fixed things very quickly.
@T_X @axx so for #FOSDEM 2027, I had another stupid idea everyone insisted was good: it will be #IPv6-only on the main network. The dual stack will get a yearly name change to prevent auto-reconnect. We want people on v6-only and break stuff left and right. Every. Single. Year.
And if #GitHub is not on v6 by next year, trust me, they will put _something_ in place very quickly.
slamp
Julien Goodwin@LapTop006 @slamp @T_X @axx there are many options. I can't have actually broken networks visible and available to connect. It all depends on if we have access to the controller, or not. But we have almost a year to see if there's a chance