It'd be rude of me not to test out @_msw_ and company's fine work.
A thread.
A thread.
https://twitter.com/_msw_/status/1463215340536614912
Had to add a route table to the subnet that spoke ipv6. Had to also force traffic over @tailscale since @sonic doesn't offer ipv6 natively without tunneling yet, but then it "Just worked" since the emergence node has ipv6 on it. I'm in!
Let's start with security and update the thing. apt says "working" but it's been a suspiciously long time for that to be, y'know. Accurate.
The DNS resover is set to 127.0.0.53 and is also nonresponsive. Back into subnet settings I go!
And with no changes suddenly it starts working. That seems... suspicious.
Welp, it turns out that github.com doesn't have an ipv6 record. That'll be... fun.
So many things just assume there's a working ipv4 stack lying around somewhere...
Yeah, still a (non-functional) ipv4 stack since this AMI hasn't been... altered.
I’m disappointed that while I can copy the number of available ipv4 IPs in the subnet (0), nowhere is it displayed how many ipv6 IPs remain available for my use.
“You’re not going to run out of them” claim the clowns who haven’t yet realized that I can use Lambda functions and container IPs as a database.
Why am I the one telling AWS this? They're the ones that charge for everything customers stand up! When I hit the limit through resource exhaustion, you'll feel pretty silly...
• • •
Missing some Tweet in this thread? You can try to
force a refresh
