4 ms·
Even already, I think you can get away with doing almost everything v6 with a much smaller number of ipv4s for legacy traffic. I say that but still largely use
by andrewstuart2 3y ago
Even already, I think you can get away with doing almost everything v6 with a much smaller number of ipv4s for legacy traffic. I say that but still largely use v4 for everything, so maybe I'm not one to talk.
- pantalaimon 3y agoUnless you need to pull anything from GitHub…
- kccqzy 3y agoThen direct your anger at Microsoft, not Amazon.
- doublerabbit 3y agoWhy not both? Both are dominating the internet-cyberspace and both are screwing it over for everyone else.
- tmpX7dMeXU 3y ago[flagged]
- dundarious 3y agoThere's a collective action problem around IPv4 vs IPv6. Talking about Azure/Microsoft/GitHub and its lack of IPv6 support is very much an interrelated problem. It's ridiculous to think of noting downsides/trade offs as just kvetching.
- duped 3y agoWhy do you need a public IPv4 address to pull from GitHub?
- ripdog 3y agoGitHub has no modern IP support, so a system without a legacy IP is unable to pull anything from GitHub.
- GoblinSlayer 3y agoThat's the idea, you route github through a legacy route and use normal route for everything else.