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.
with IPv6 deployment reaching 80%+ in many places, we can probably remove IPv4 support from FreeBSD 17.0.
i'm sure this won't cause any issues for users because people constantly say that FreeBSD users are super evolved and up-to-date with the latest technologies, unlike those awful Linux users.
The most recent encounter is https://adsb.fi/
> These endpoints are accessible for people contributing to adsb.fi by hosting a receiver. Your feeder IP address is automatically given access.
src: https://github.com/adsbfi/opendata/blob/main/README.md
adsb.fi is fronted by Cloudflare, so they could enable #IPv6 relatively easily, but they would have to revamp their feeder authentication.
The first such system I encountered was https://tgif.network/ , a #hamradio DMR network. Users would log in to the website and their hotspots would be shown based on whether they were connected from the same IPv4 address. They've moved away from this mechanism as all hotspots are now credential authenticated as well. Unfortunately, even with this change, the underlying software does not have any #IPv6 support.
I'm still running into websites that grant access based on your IPv4 address, presuming some other authenticated device coming from the same network. This image clearly has not clicked with the admins of these systems yet.
(image source https://chrisgrundemann.com/index.php/2011/nat444-cgn-lsn-breaks/ )
ChatGPT was released a mere two years ago and people will not shut up about it.
But I'm the weird one because I won't stop talking about #IPv6.
Mit dem iPhone geht es auch. Allerdings erst nach manueller Änderung des Profils. (Standardeinstellungen: Fehlanzeige!)
Persönlicher Hotspot funktioniert auch.
verwendetes Profil:
https://www.thomas--schaefer.de/roaming/Vodafone.mobileconfig
Cisco's IPv6 evangelist and stroopwafel queen, Nicole Wajer, reports that the event wireless at Cisco's Global Sales Experience this year was 76.5%.
I feel like this casts some doubt on the nay-sayers' fEeLiNgS about how nobody is using #IPv6. 👀
I didn't have the script under version control, but by virtue of my having migrated it across machines I had enough breadcrumbs to re-create some of the version history. If you'd like to see what I've been working on: https://git.home.nivex.net/nivex/jool-clat
I got down a rabbit hole this evening of tweaking my Jool CLAT script. More parameter checks, support for the internal bridge I use for my VMs, and a proper wait loop for SLAAC to finish when determining the CLAT v6 address. It leverages jq to parse iproute2 JSON output to make things easier.
#AWS Directory Service introduces #ipv6 support for Managed Microsoft AD and AD Connector
Posted on: Oct 3, 2025
https://aws.amazon.com/about-aws/whats-new/2025/10/aws-directory-service-ipv6/
@armbian blog not reachable from #IPv6 network:
$ curl -Iv https://blog.armbian.com/
* Host blog.armbian.com:443 was resolved.
* IPv6: 2a0a:4cc0:2000:34a5::1
* IPv4: 152.53.81.238
* Trying [2a0a:4cc0:2000:34a5::1]:443...
* connect to 2a0a:4cc0:2000:34a5::1 port 443 from 2605:a601:a63f:7c02:caa3:e8ff:fe76:98ff port 59006 failed: Permission denied
* Trying 152.53.81.238:443...
* Immediate connect fail for 152.53.81.238: Network is unreachable
* Failed to connect to blog.armbian.com port 443 after 42 ms: Could not connect to server
* closing connection #0
curl: (7) Failed to connect to blog.armbian.com port 443 after 42 ms: Could not connect to server
Whelp back I go down into the IPv6 mines wish me luck (I need to get Cilium/Talos running in dual stack before I get these remote nodes working) The nodes are getting ipv6 addresses but it isn't propagating into k8s/Cilium for some reason...
Amazon ECS announces IPv6-only support
Posted on: Sep 29, 2025
https://aws.amazon.com/de/about-aws/whats-new/2025/09/amazon-ecs-ipv6-only-support/
Amazon EC2 Auto Scaling now supports Internet Protocol Version 6 (IPv6)
Posted on: Sep 29, 2025
https://aws.amazon.com/about-aws/whats-new/2025/09/amazon-ec2-auto-scaling-ipv6/
i know have a little Gemini pod in the Geminispace :-) Of course, hosted on a FreeBSD server and securely running inside a Jail
and with native IPv6.
More content there will follow 🙂
Gemini is a lightweight, privacy-focused alternative to the web.
To browse Geminispace, you'll need a dedicated Gemini client (like a browser but simpler).
This sounds like an awful question: Can I "port forward" an ipv6addr:port pair to an internal ipv4 address?
Ok so after a bunch of searching for a good tool to track down what is running on the network I settled on: * Security onion ingesting NetFlows from the router. This catches all traffic that crosses subnets. Traffic within the subnets isn't as much of a concern at this stage. From those sources I can pretty easily setup sensible firewalls at the router level, and potentially at the host level as well. After that I can work on intra-kubernetes traffic rules. Also I used some of the initial data to sort hosts a little better and cleanup DHCP/static DNS entries Lastly I'm going to back away slowly from ipv6 again. I did learn a bit and made some progress but getting that cluster properly talking dual stack is less of a priority at the moment I think?
* Nmap plus a stylesheet I found was able to generate a pretty digestible html doc enumerating ports and hosts
AWS Site-to-Site VPN now supports IPv6 on the outside IPs
by Ruskin Dantra, SaiJeevan Devireddy, and Scott Morrison on 24 SEP 2025
If I use openresolv in place of resolvconf I don't run into the timing issue, but it has no notion of interface-order so it gleefully puts IPv4 resolvers ahead of #IPv6 with no apparent way to change this.
Being thankful is important, esp. when you use opensource software.
I'm thankful to the coder(s) of gping a command which sends a nice graphical output in *sh when you invoke it of the ping reponses of your favourite server
In the same line I again want to thank the coder(s) of httping which can send you ping responses in an awsome way
I had spoken about httping before
Thank you all
🖋️ #bash #sh #zsh #ksh #csh #ping #IPv6 #IPv4 #gping #httping #Linux #POSIX #OpenSource #Programming
Ok so more IPv6 thoughts: I was thinking a bit more about the idea to move the dnsmasq service onto the router: So the entire reason for switching to dnsmasq was because it creates DNS entries for DHCP clients, and it even can assign a different subdomain per subnet. However, there was something I had yet to get functional: mapping IPv6 to those same DNS names. I'm not even sure how that is possible! Certainly not with dnsmasq because I don't have it handling anything? Or maybe there is some stateless DHCP option? Which got me to thinking that maybe it is possible with Mikrotik's scripting? On a related note I saw a script to update IPv6 prefix if that updates which looks super useful and might put me at ease. I could use ULAs for internal traffic and have that prefix updater script update firewalls if anything changes.
Cooking or cooked: link shortening edition
URLs are compressed but rather than a path they become a subdomain.
Server-side for creation:
A DNS entry is created with a unique, globally addressable IP address from the host's delegated v6 /64, and adds that IP to the main interface.
Client-wise:
The dynamic subdomain is delegated out to the host. The host DNS server responds with the unique IP for that link shortening. When it receives HTTP for that IP it responds with the usual redirect/301 to the full address.
| Cooking 👀: | 1 |
| Cooked 🤡: | 9 |
| Y tho 🤷♀️: | 9 |
Closed
IPv6 Deployment at APNIC 60
By George Michaelson on 18 Sep 2025
https://blog.apnic.net/2025/09/18/ipv6-deployment-at-apnic-60/
#blog #ipv6 #apnic
#notbyGeoffHuston (except one presentation)