@laird I had working #IPv6 with a delegated /48 way back in 2016. Then the Charter/Spectrum takeover of TWC in my area completed, and they ripped it all out.

I started getting an IPv6 address from Spectrum a few months ago, but was never receiving a default route. Finally started seeing one this morning.

Talking to some people in IT about #IPv6 is like trying to reason with religious conservatives about their, "firmly held beliefs."

It is halfway through 2025, and this is how little I trust my new ISP provided IPv6 space.

nuintari@fam-gw1> show configuration security nat source rule-set inet-snat rule inet6-snat-all
match {
source-address 2001:0db8:0f00::/48;
destination-address ::/0;
}
then {
source-nat {
interface;
}
}

When it works for the next year or so, I'll trust it enough to explore prefix delegation.

#ipv6

Holy shit again!

I have native #IPv6 at home for the first time since 2017, when Spectrum ripped a perfectly good working IPv6 stack out of the former TWC network in my area.

@nuintari Yesterday I learned that #Vodafone #DSL in Germany, which notoriously lacks #IPv6 support at most places, was spotted with IPv6 at a new location. That would be another ISP in Germany with IPv6. Not seeing a dent in the statistics yet, but maybe they just started. There are not that many ISPs left.

RE: https://mastodon.bsd.cafe/@nuintari/114891560130768537

Một lý do khác khiến IPv4 vẫn còn tồn tại: Các nhà cung cấp dịch vụ đám mây/Internet mới cần một lượng lớn địa chỉ IPv4. Các công ty cũ thì đã sở hữu sẵn IPv4 từ trước khi cạn kiệt và chỉ việc trả tiền duy trì. Việc các công ty từ chối triển khai IPv6 cũng làm chậm quá trình chuyển đổi. #IPv4 #IPv6 #internet #côngnghệ #IPv4cạnkiệt

https://news.ycombinator.com/item?id=44632525

IPv6 Based Canvas

Link: https://canvas.openbased.org/
Discussion: https://news.ycombinator.com/item?id=44629962

#ipv6

Another #IPv6 win: https://github.com/testssl/testssl.sh/pull/2852

ntfy.sh now has full #IPv6 support!

#aws #ipv6

Amazon SNS expands IPv6 support to VPC endpoints in AWS commercial Regions
Posted on: Jul 18, 2025

https://aws.amazon.com/about-aws/whats-new/2025/07/amazon-sns-ipv6-vpc-endpoints-commercial-regions/

As much as I wish #IPv6 was an option, even I, a rabid ISP employee who has been successfully deploying IPv6 to carrier grade networks for well over 15 years now has to admit, most big ISPs SUCK at IPv6.

Spectrum is no longer advertising me a default route in IPv6. WTF? It was working in 2016 when I subscribed to TWC.

Then Charter bought them, became Spectrum and IPv6 was ripped out of the entire network.

It has reappeared, been broken, and reappeared several times since.

It was working three weeks ago.

And no, tunnel brokers are not an option. First of all, we can't scale the entire IPv6 Internet through Hurricane's network, and secondly, most tunnel broker blocks are blocked damn near everywhere useful.

#aws #ipv6

Amazon SQS expands IPv6 support to VPC endpoints in AWS commercial Regions
Posted on: Jul 18, 2025

https://aws.amazon.com/about-aws/whats-new/2025/07/amazon-sqs-ipv6-vpc-endpoints-aws-commercial-regions/

A Large-Scale IPv6-Based Measurement of the Starlink Network.

https://arxiv.org/pdf/2412.18243

#Starlink #IPv6

so it turns out you can use Apache mod_proxy to proxy to an IPv6 link-local address, but it's a bit roundabout.

in /etc/hosts:

fe80::2%vm.cgit cgit-backend.internal

in Apache:

<Location />
ProxyPass http://cgit-backend.internal:80/
</Location>

i feel like there should be a better method to do this. any suggestions?

trying to ProxyPass to "http://[fe80::2%vm.cgit]:80" doesn't work:

AH01083: error parsing URL http://[fe80::2%vm.cgit]:80: Invalid host/port

#ipv6

paper about #ipv6

( maybe boring )

https://www.arxiv.org/abs/2507.11678