What a fine day for things to break due to #IPv4 This time user complains that he can't use captive portal on some WiFi when his #WireGuard VPN connection is enabled. The IP address of the captive portal overlaps with one of our real networks within 10.0.0.0/8, which we route over VPN. Sadly I can't make the VPN #IPv6 -only yet.
I’m looking at the #37c3 traffic dashboard and I’m wondering why is the #ipv6 traffic such a tiny fraction of the total? At my job #ipv6 makes way bigger fraction of the traffic, even majority for some services, like our VPN server.
Another morning wasted thanks to #IPv4 and #CGNAT. Multiple users could not connect to VPN because they had #IPv6 disabled and their ISP suddenly started doing *something* to their packets. I can't even tell what. The VPN server recognized incoming connections but the authentication phase was never reached.
I've fixed my live Russian natural gas flows page - almost all pipelines are now down or blown up, and their statistics are disappearing. This has allowed me to restore the original color scheme. https://berthub.eu/gazmon/
Vernetzte Spielzeuge und Smartwatches gefallen nicht nur Kindern, sondern auch Eltern, die sich um ihre Kinder sorgen, sie schützen möchten und dabei Datenschutz und Privatsphäre eher hintanstellen. ...