If I've never heard anyone else use a specific pronoun for someone new or I otherwise don't know, I try to use they/them. Otherwise I use what others do.
And if someone does let you know that a person/themselves prefer a specific one, always say thanks (you can't be sorry for something you didn't know!) and do your best to remember for next time.
I also try to use genderless terms like "folks" or just "everyone" instead of "guys"
The bottom of a kitchen cabinet at the air gap of the skirting (licking it). Only ever when I'm getting his food ready. Never any other time.
It's a weird appetiser, I guess
Instead of nat and port forwards that rewrite, your firewall is set to only forward specific traffic, exactly how'd you'd configure outbound forwarding on a nat network (but opposite directions)
Open forwarding is a router, not a firewall
It should only be needed if your ISP is brain-dead and only gives you a /64 instead of what they should be doing and also giving you a /56 or /48 with prefix delegation (I.e it should be getting both a 64 for the wan interface, and a delegation for routing)
You router should be using that prefix and sticking just a /64 on the lan interface which it advertises appropriately (and you can route the others as you please)
Internal ipv6 should be using site-local ipv6, and if they have internet access they would have both addresses.
🧓
Also for routing table reasons. Ipv6 needs to use prefixes to do link aggregation or it just gets too bjg
And if you want static ips either use dhcp6 or disable the randomisation of eui64 addresses
Weird! Though I guess a lot of these would be sitting behind load balancers / reverse proxies anyway (so ipv4 is fine) and unlikely to up and change isps very often? Lol
If I had to, I'd be trying to add an extra cidr to one of the options listed at https://kubernetes.io/docs/concepts/services-networking/dual-stack/#configure-ipv4-ipv6-dual-stack But as you say, probably doesn't work!
Even if you give it multiple ip6 cidrs to allocate?
A 7th gen i5-7500 is enough to handle hardware transcoding, though generally you want to be downloading media that can be direct played rather than needing transcoding
Not sure on the history of that. It would make things like that easier
Indeed, that's correct ula usage, but shouldn't need nat rewriting. The global prefixes just need to be advertised by RA packets
I use openwrt on my home network which uses dnsmasq for dhcp. It can give a static suffix which just works with the global prefix on the interface and the site local / ula prefix it uses
Ehh, I've seen both. Perhaps not in a home router context though, never really bothered to check
Yup indeed. That's why it advertises both dhcp and slaac
Address space is so huge that iirc the only global addresses in use are 2xxx::
Its so huge that it's not needed to use anything else is the goal as far as I see. If it starts with 2, it's global.
Point is, you should be able to have them have both. Or stick a reverse proxy in front that can translate. Unless they're somehow meant to be directly internet reachable the public addresses could be autogenerated
Full disclosure though I don't know anything about kubernetes.
It certainly looks like you can give it a prefix to assign out, possibly even multiples
Fire bad, change scary