cablespaghetti.dev is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
Part 3 of my hobby AS series is up: connecting my AS201379 to LocIX Düsseldorf via a dedicated FreeBSD edge router.
Covers route server peering, IPv6-in-IPv6 GIF tunnels, PF on a shared peering LAN, and iBGP back to the core.
https://blog.hofstede.it/running-your-own-as-joining-an-ixp-with-a-third-edge-router/
Mission: Connect to a device on the LAN (Local Area Network)
Scenario: #IPv6mostly network - supported clients get only #IPv6 addresses due to DHCP option 108 -> #464XLAT
Roku app:
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
@tschaefer eigentlich ist das 1&1 Internet im Mobilfunk für #Android User immer kaputt, weil #PMTUD kaputt und zu kleine #MTU
Leider ist das #AS8881 Betreibern egal. Tickets werden ohne Lösung geschlossen.
Testet selbst https://test-ipv6.com
There's no way to do both SLAAC GUAs plus ULAs using DHCPv6 is there?
I need all the machines to have ULA for Wireguard reasons but I don't want to give up the GUAs.
I finally have IPv6 support from my mobile provider - TalkHome Mobile (UK)!
I woke up this morning to see a new 'VoLTE' icon on my phone. Checked the status and see an IPv6 address on the mobile interface for the first time, and it works. Woohoo!
On the downside, I currently cannot receive SMS messages and the provider's app is broken. Hopefully this is just over-running maintenance.
ooh, the rdap CLI I'm using resolves IPv4 addresses in v6-mapped format. Handy for copypasta out of nat64 stats:
$ rdap ::ffff:9765:c1c2
IP Network:
Handle: NET-151-101-0-0-1
Start Address: 151.101.0.0
End Address: 151.101.255.255
IP Version: v4
...
Ironic considering their Metronet Fiber division doesn’t offer IPv6 addresses at all.
“T-Mobile USA leads with 93% IPv6 adoption on mobile networks.”
Aus einer Petitionsantwort vom 7. August 2023 des Bayerischen Staatsministerium der Finanzen und für Heimat:
"Einführung von IPv6 für Webangebote des Freistaats Bayern
Da der IPv6-Standard zunehmend Verbreitung findet, ist die Anbindung der Webangebote des Freistaats Bayern an IPv6 (zusätzlich zu IPv4) im Rahmen der operativen Projektplanung im Gange und soll bis Ende des Jahres 2027 abgeschlossen sein. Entsprechende Konzepte und Grundlagen dazu wurden bereits erstellt."
| ja sicher: | 2 |
| nein, beim WLAN hats ja auch schon nicht geklappt: | 15 |
Closed
Es gibt Dinge, die will man einfach nicht sehen müssen.
Wenn solche Fragen gestellt werden, ist leider schon in der Ausbildung der Ausbilder etwas schief gelaufen 🤨
(Frage ist geklaut von Gutefrage.net)
I was using adsb.fi for aircraft tracking, but tonight I was pointed to adsb.lol which has some extra features and works on my #ipv6 only network.
Dabbled with enabling #IPv6 on my #cilium based #k3s cluster this morning. Seems that it /is/ possible to enable without a full cluster/node rebuild*.
Mostly went fine, prefix, prefix mask, masq set to off. After poking a couple of the Cilium Pods new Pods got an IPv6 addr. ...but couldn't ping anything. Traffic made it out based on what Hubble was showing, but not the reverse.
Enabled v6 masquerading, and it all started to work, yay. Suspect I need to try setting up a static route on my router for this to work.
I have a couple pods w/ quirky networking so they got unhappy. v6 IP, dns query replying w/ AAAA but no dice as they really only have v4 connectivity.
Back off for now but promising that it could work.
*.spec.PodCIDR(s) are immutable on v1.Node resources, but cilium in it's default configuration doesn't get it's PodCIDR from there in the default config.
"If you have a website and it's not v6 reachable, it's not on the Internet."
https://blog.flyingpenguintech.org/2013/10/arin-32-call-to-content-providers.html
Where are my #ipv6 experts at?
My #guixrouter is having problems where when I restart its networking, it can respond to neighbor discovery, but after some time... it stops receiving neighbor discovery requests (they don't appear in tcpdumps). I think this must be either something to do with my switch or something to do with the linux bridge on the proxmox host... why would this happen? I can see the ndp snooping entry disappears on switch, but it happens even if ndp snooping is off
@doachs ?
https://lore.kernel.org/lkml/20260310153506.5181-1-fmancera@suse.de/
If any distro kernel ships CONFIG_IPV6=n after this they don't belong on the 'net.
If you are using an online shop and the checkout requires PayPal, Stripe or else, please make shure to send a Feature Request to the online shop to ask their payment processor for #IPv6 support.
Happy Eyeballs has been a disaster for #IPv6 transition. We've trained a whole generation of admins that it's OK if your v6 doesn't work, the client will just fall back to IPv4. What if the client has no legacy connectivity to fall back on? That was (and still is) the goal.
If you believe that AI is inevitable but #IPv6 is not, well, you're probably not even reading this since we don't live in the same reality.
RE: https://wandering.shop/@xgranade/116193578562763150
In light of ntfy.sh becoming the latest den of slop code, I have stopped using it.
For UnifiedPush I am now using Conversations. There's something ironic about one messaging client (Element X) using another for its notifications. Now we need to get #IPv6 enabled on up.conversations.im.
Last night instead of going to bed I forgot about daylight saving time and added a statically defined #ipv6 #wireguard mesh between my #homelab servers.
Now I can use that instead of #tailscale for the secure data plane. Tailscale is great and I'll probably keep it for the management plane. The way it aggressively idles connections combined with the first packet seemingly always hitting a DERP server makes stuff feel a lot slower than it should.