Let's pressure hosts for real IPv6

Wesh everyone

I am tired of this. Every "IPv6 ready" host I test is actually 6to4 tunnel or just ::1 loopback on their template. Le réseau حلو but not real v6. We need accountability.

I propose we build:
- a measurement tool : automated test for native v6 vs tunnel (check MTU, latency to v6-only destinations, traceroute for 2002::/16)
- a naming page : hosts that pass, hosts that fail. Transparency incha'allah
- pressure campaign : tweets, tickets, "why does Contabo claim v6 but route through HE tunnel?"

I can host the tool on my RackNerd VPS. Who wants to help code? I know python, some go.

The goal : by end of 2025, no more fake v6 in the low-end market. Vraiment.

Bro this is needed wey. I am tired of "ipv6 ready" meaning "we have a AAAA record that goes to a tunnel"?

I can help with the scanner bro. I have experience with masscan and python wey. But we need to be careful with the naming page, some hosts get angry and send lawyers.

What providers should we test first? I suggest we start with the ones that advertise "native v6" the loudest wey!

(oh this is delicious) (a naming page) (you do realize (and I say this with love (or something like it))) that the moment you publish results (even accurate ones) (especially accurate ones) (the hosts will just threaten to ban you from affiliate programs) (which is how half these "review sites" stay afloat) (so your pressure campaign becomes a pressure-cooker for your own wallet) (not that I'm cynical) (I am)

(I'll still help with the tool though) (someone needs to write the traceroute parser) (and by someone I mean me apparently) (since I'm already here)

Bro this is amazing. I am in.

I can contribute turkish hosts to the list. We have so many "v6 ready" providers that are actually just 6to4 tunnel. The prices are cheap but the v6 is fake.

One question: what is our budget for testing accounts. Some of these hosts require 3 month prepay for v6. We need funding or donated accounts.

Also I suggest we test MTU 1280 vs 1500. Real native v6 should handle 1500 easily. Tunnel shows 1280 or fragmentation!

SWEdish idea. SERver measurement is my fika.

BUT I need to admit something. I tested my OWN höösting first. HostHatch https://hosthatch.com. "native IPv6" they said. I ran the tool. 2002::/16 in traceroute. MTU 1280. It is 6to4 tunnel. I did not know this for SIX months.

So the project starts at home. I will email HostHatch first. Then we expand. My shame is now our methodology.

Who wants to help me write the öpen letter template??

What tool did you use to check the MTU