Earlier quoted context omitted.
Latin1 to UTF8
And I still, to this day, see mojibake from time to time.
The exception that proves its success
IPv6 traffic crosses the 50% mark
511–520 of 643 posts
Re: IPv6 traffic crosses the 50% mark
#512Been waiting for this for years! Now I just wish my local ISP (rural Canada) supported it.
Re: IPv6 traffic crosses the 50% mark
#513Earlier quoted context omitted.
I don't see how this generalizes into a security hole caused be lack of IPv6 knowledge. It just sounds like a random bug in Snapcast (great program!). If a user configures a program to only bind to loopback, but the program binds to other interfaces as well, that's a bug in the program.
There are sure to be dozens or hundreds of vulnerabilities like this, that's what I'm saying. I'm not even sure it's a bug in snapcast - very possible I configured it wrong without realizing.
Without knowing exactly what happened here, it could be hundreds, dozens, or zero other such vulnerabilities.
The usual convention for configuring listening interfaces usually involves listing IP addresses or interface names. There's very little room for misconfiguration here, although it's possible. More likely to be a bug in Snapcast (it's almost certainly not an issue in the Linux kernel).
Moreover, this general problem (i.e. configuring listening interfaces) is not/should not be different between IPv4 and IPv6. So introducing IPv6 should not™ incur any additional risk at this level.
But as said, it's hard to get more concrete without knowing exactly what happened in your case.
Re: IPv6 traffic crosses the 50% mark
#514Earlier quoted context omitted.
I mean Azure doesn't really support IPv6 well either for a lot of the big-ticket services.
That seems weird given NIST, and the US Government, set a requirement for IPv6 Only back several years ago, and it sort-of became part of the JWCC requirements (It wasn't in the requirements, IIRC, because it came after those were set, but the government wouldn't fully approve use for JWCC if you didn't meet it). You'd think they'd have sprinted for that feature as fast as they could go.
Microsoft gets special treatment.
USG also set a whole bunch of security requirements under FedRAMP that Microsoft can never meet, but they received an ATO anyway because they are so heavily entrenched in government.
Re: IPv6 traffic crosses the 50% mark
#515Earlier quoted context omitted.
If a single machine gets /64 and you rate limit by /64, what doesn't work? >Linode and others that do /64 for a whole data center That's how it's supposed to work.
> That's how it's supposed to work. According to who? It could fit best practices if your datacenter has one tenant and they want to put the entire thing on a single subnet? In general I would expect a datacenter to get something like a /48 minimum. Even home connections are supposed to get more than /64 allocated. And Linode's default setup only gives each server a single /128. That's not how it's supposed to work.…
If the OS uses SLAAC by default, then it will just work, but SLAAC is for humans and makes less sense for web servers (yet can make sense for vpn servers). For web servers /128 is more meaningful.
Re: IPv6 traffic crosses the 50% mark
#516Earlier quoted context omitted.
How far below is the question. It could level out at 60% - that is believable. However it can't level out at 99% - Somewhere around 95% major sites will decide IPv4 isn't worth supporting and they will just ignore that final 5% of customers, which will force them to upgrade - which in turn will give others confidence to remove their final 4% of customers - until IPv4 dies.
There are still ascii dialup bulletin boards out there. and operating model T’s. IPv4 will be around for longer than you or I.
> IPv4 will be around for longer than you or I.
That's a matter for the legacy network on the other side of the internet to handle, as it converts my IPv6 packets to IPv4.
Re: IPv6 traffic crosses the 50% mark
#517Earlier quoted context omitted.
Nearly all ISPs these days are deploying IPv6 for their mobile networks and core service networks, especially in less developed markets^1. The reason is simple, a cost justification. What doesn't exist is a cost justification for Enterprises to deploy IPv6, and for ISPs to deploy Residential / Corporate Internet IPv6. IMO with the right market conditions, IPv6 could spread really fast within 6-24 months. For example,…
Hetzner makes you pay 1 € per IPv4, while IPv6 is free. I'd gladly get rid of all IPv4's given that I have many servers.
I don't even know why clouds offer public IP addresses. In my opinion all clouds should only have a gateway that routes via host header for millions of customers. IPv4 should be a special priv for special situations at a higher price. Then these clouds could own maybe 20 IPs total instead of millions.
Re: IPv6 traffic crosses the 50% mark
#518Earlier quoted context omitted.
Your work is probably all exiting through the same IP, you competing with others on the same IP is causing the rate limit.
I've considered this, but the company is small enough that the number of people who would be on GitHub at any moment (instead of our internal git forge) can be counted on one hand, and when I'm the first one there in the morning it still rate limits me.
Hm, I've also noticed sites being more aggressive about verifications after I started using LLMs locally. They think I'm a bot (which... fair), even on completely unrelated sites I seem to be getting prompted for human verification much more often.
Re: IPv6 traffic crosses the 50% mark
#519Earlier quoted context omitted.
I’ve worked for a company that was barely using its /16. I know several individuals, including myself, with personal /24s.
A /24 is currently worth between $5,000 and $9,000 USD. Did you get them a long time ago?
Yes, over 32 years ago. It was before ARIN and is considered a legacy block.
Re: IPv6 traffic crosses the 50% mark
#520Earlier quoted context omitted.
I’ve worked for a company that was barely using its /16. I know several individuals, including myself, with personal /24s.
I recently released a /24 that I registered in 1992 and I hadn’t realized it was still mine. ARIN was gonna charge me $100 to authenticate and recover the account, but once I asserted and notarized my letter of relinquishment, the process went real quick!
You could've recovered it and sold it for $7K, or rented it out for $500/month.