Earlier quoted context omitted.
should we try going back to IPX ?
Only if we're bringing back Token Ring, too.
Arcnet for me.
IPv6 traffic crosses the 50% mark
291–300 of 643 posts
Re: IPv6 traffic crosses the 50% mark
#292Earlier quoted context omitted.
Carrier-grade NAT for home connections is pretty rare in Germany. I only know of Deutsche Glasfaser - a fairly new ISP that isn't doing too well.
It's very common. German ISPs collectively went with DS-Lite, so most of that 77% with v6 have CGNATed v4.
Somehow it's really hard to find numbers, but AFAIK at least Telekom and 1&1 don't use CGNAT for home connections, which already rules out that 77% have it.
Re: IPv6 traffic crosses the 50% mark
#293Re: IPv6 traffic crosses the 50% mark
#294Earlier quoted context omitted.
What? One nine isn’t good enough for you?
Excuse me. Zero nines. Or two nines if you relax your definition of where they are in the number. https://infosec.exchange/@0xabad1dea/116334321751266751
Excuse me, but I see 4 nines. 95 incidents in last 90 days, 89.91% uptime.
Re: IPv6 traffic crosses the 50% mark
#295I get an IPv6 address from my ISP (a /56 I believe), but I wish there was some good information on how to update my OpenWRT VLAN configuration, routing, and firewall rules to be able to support native IPv6 on my devices. Would love to be able to have direct IPv6 connections to the internet from my devices, but I want to make sure I can do it safely.
Re: IPv6 traffic crosses the 50% mark
#296Earlier quoted context omitted.
fd::1 is somewhere in the reserved ::/8 space where various stuff like old ipv4 mapped addresses and localhost reside. What you probably mean is something like fd00::1, but that is something you shouldn't use, because 'fd00::/8' is a probabilistically unique local address (ULA) block. You are supposed to create a /48 net by appending 40 random bits to fd00::/8. Of course, if your fair dice roll lands on all zeroes, a…
In home networks, the idea of merging with someone else's network is... most certainly not worth worrying about. Maybe you marry someone or become roommates with someone who also picked fd00::/8? And you still want two separate subnets? Other than that I don't see a scenario where it matters. Granted, if you're doing this in a corporate setting (where merging with someone else's address space is a lot more realistic)…
I'm having my own and my girlfriend's router (in different flats) connect to each other with a wireguard tunnel, so I can print on her printer. Non-colliding addresses make this a lot easier.
But yes, renumbering also isn't a lot of work.
Re: IPv6 traffic crosses the 50% mark
#297It has barely hit 50% and it's already plateauing. This adoption rate is ridiculous despite basically all network interfaces supporting it. I thought I would see IPv6 take over in my lifetime as the default for platforms to build on but I can see I was wrong. Enterprise and commercial companies are literally going to hold back internet progress around 60 to 75 years because it's in their best interest to ensure users…
> Also, notice how Android and iOS don't support turning off IPv4.
You can trivially connect an iOS device via IPv6 only.
Re: IPv6 traffic crosses the 50% mark
#298Good.
I think most of us know that their design failure here was a lack of backwards compatibility. But at least it's getting adopted.
Re: IPv6 traffic crosses the 50% mark
#299I get an IPv6 address from my ISP (a /56 I believe), but I wish there was some good information on how to update my OpenWRT VLAN configuration, routing, and firewall rules to be able to support native IPv6 on my devices. Would love to be able to have direct IPv6 connections to the internet from my devices, but I want to make sure I can do it safely.
You only need to set nothing and it should setup ipv6 on all downstream vlan interfaces.
For static prefix I'd you can set ip6hint per vlan interface.
For each vlan interface you need a stanza in the DHCP config file.
And regarding firewall, as with the default lan zone you might need to add new zones with the vlan interfaces and configure forwarding rules. That's it.
Re: IPv6 traffic crosses the 50% mark
#300Earlier quoted context omitted.
Do we know any technical reason for this? Or are we left to think this is somehow a political thing?
IPv6 is very difficult to implement and enforce reliable rate limits on anonymous traffic. This is something we've struggled a lot with - there is no consistent implementation or standard when it comes to assigning of IPv6 addresses. sometimes a machine gets a full /64, other times a whole data center uses a full /64. So then we need to try and build knowledge of what level to block based on which IP range and for so…
Well, even if there was a standard, that's still not a guarantee that the other side of the /64 would be following it. It's correct for you to rate-limit the whole /64.