A tale in 3 screenshots, without comment.

http://rip.psg.com/~randy/071022.v6-op-reality.pdf

https://www.google.com/intl/en/ipv6/statistics.html

https://circleid.com/posts/20230817-ipv4-prices-supply-and-demand-in-2023

#ipv6 #ipv4

@meesj Ik zag deze presentatie en dacht dat je dit misschien interessant zou vinden.

https://youtu.be/vCgJj5r1kWk

#ipv4 #ipv6 #arpanet

Liebes Fediverse, vielleicht weiß hier ja zufällig, ob das überhaupt klappt und wenn ja, wie.

#vodafone Internet per Kabel (ehemals #kabeldeutschland), #kabelmodem im #bridgemodus, dahinter ein #router mit #openwrt

#ipv4 klappt wunderbar. Aber ich kriege kein #ipv6 egal was ich mache. DHCPv6 tut halt nicht.

Hat jemand einen ähnlichen Aufbau im Einsatz? Wenn ja, wie ist euer Router für IPv6 konfiguriert?

Und nein, ich meinen keinen IPv6-Tunnel 🙂

Spent the last ~week debugging and trying to understand MTU issues with WireGuard on DS-Lite and PPPoE connections with ICMP "black holes", MSS clamping and nftables. Quite the ride! Think I managed to sort of understand things now...

#networking #wireguard #ipv6 #ipv4 #pppoe #dslite

Out of 42, 43, 44, 45, which 2 adjacent numbers would be the worst possible to choose for a combined x.y.#.0 grouping if you wanted them to be "logically" one "availability zone" spread across 2 physical locations in a private cloud? And which do you think the "agile" "we know better than security" group chose? #networks #ipv4

Granted that's just the "core" system: with only #linux, #toybox and #dropbear as #ssh client...

Nothing else...

It can barely get on #Ethernet and #SSH to #IPv4-reachable hosts.

Not much more.

So it'll turn your #i486 and up into a SSH-Terminal not dissimilar from classic terminals like the #VT320...

https://www.youtube.com/watch?v=RuZUPpmXfT0&t=357s

AARRRGGGHHH - having a tough day today! This morning my #VPS provider sent me an email that they are shutting down TODAY, and I'm left looking for a VPS provide that supports #FreeBSD AND can provide #IPv4 + #IPv6, AND is inexpensive...
Any VPS provider not supporting IPv6 nowadays is really lagging behind.

Even tho that's likely the only thing it'll be able to do: Password-based #SSH login to #IPv4-reachable hosts...

That's still something to get started with...

basically a bootable SSH #terminal...

@beforewisdom
Not that I don't think #Floppinux is bad - far from it.

But considering that #TinyCore #Linux can do 17 MB apparently with default userland and 23 MB with #Xorg + #Desktop I do want to get things to just work without being able to at least have #IPv4 #Ethernet working and being able to mount #SMB shares or at least #SSH into things using #Dropbear.
http://tinycorelinux.net/downloads.html

Pinging ipv4 addresses works while ipv6 doesn't #ipv6 #ping #kali #ipv4

https://askubuntu.com/q/1483500/612

See you in #Hamburg for #ICANN78 👋🙂
https://meetings.icann.org/en/icann78
Special thanks the hosts eco, DENIC and Hamburg
#DNS #DNSSEC #IPv4 #IPv6

@doachs @noipv6 I don't see a reason to not deploy #IPv6, no matter where. The longer we keep sticking with the legacy protocol #IPv4, the more slowdown of the future development of the internet.

Meh. Die #Hetzner Storage Shares sind zwar via #IPv6 erreichbar, outbound geht aber scheinbar weiterhin nur #IPv4.

Ah yes, that #Canada moment where you can't get a static #IPv4 IP without paying at least twice as much (and need to register yourself as a business to get the "privilege" of doing so) and you can't get #IPv6 either.

And of course most conventional DNS registrars have garbage support for dynamic IP because of a bunch of unrealistic assumptions.

At least they mostly have APIs now so I can code up a smol daemon to handle that for me, but still obnoxious.

New #VyOS install is done!
Everything seems to be working: #IPv4, #IPv6, Mesh #Wireguard VPN, #BGP over WG, #BFD to quickly detect VPN connection loss and re-route via other peer within a second, #QoS with Cake to eliminate Upload Bufferbloat.
And by learning the new Firewall syntax I also made a better / stricter firewall config.

Now lets see if the setup is also stable. It should in theory, it's my first bare-metal VyOS install after all and most issues I've had were to to virtualization.

@russss In comparison that's what @freifunkMUC looks like.

Traffic volume is even higher for #IPv6 than #IPv4 but flows are less.

Even the FTP server list consists of mainly #IPv4
https://events.ccc.de/camp/2023/hub/camp23/en/info/ftp/

Go #cccamp23 enable #ipv6

@f2k1de Well it means Happy Eyeballs decided #IPv4 wins over #IPv6. Mostly related to worse latency.

ugh. this is bs.

So #ipv6 is great cause you can hook up #lxd directly to the router and get public addresses directly on each one. Nice.

But then since half the internet isn't on it I gotta support #ipv4, on which the single address already has the host's web server. So I gotta proxy from that to the container.

But then acme challenge goes to the ipv6 instead of the ipv4 🤦‍♂️

It ought to be easy-peasy to provision an #AWS #EC2 instance, point a domain name at it, and start serving a website. But friends, it is not. For who knows what reason, #AmazonLinux2023 makes it nearly impossible to use #LetsEncrypt, and AWS's alternative solution (#NitroEnclaves and such) is beyond overkill.

Scaling an instance up or down fails as often as it succeeds for me. The new policy of charging for #IPv4 addresses basically doubles the price for a small website. ☹️

(3/8) 🧵