3 ms·
I think this is probably the main issue, too complex to set up on the server. But I agree with what AWS is doing. For example, when I do an ifconfig, I get 3
by jmclnx 3y ago
I think this is probably the main issue, too complex to set up on the server. But I agree with what AWS is doing.
For example, when I do an ifconfig, I get 3 ip6 addresses but 1 ip4 address.
'?' indicates a unique value, 'x' means values match between the IP addresses. That alone indicates the complexity of ip6 on setting up the server.
inet6 ????::????:????:????:???? prefixlen 64 scopeid 0x20<link>
inet6 xxxx:xxx:xxxx:xxxx::???? prefixlen 128 scopeid 0x0<global>
inet6 xxxx:xxx:xxxx:xxxx:????:????:????:???? prefixlen 64 scopeid 0x0<global>
- Hikikomori 3y agoWhy is this even relevant in AWS?
- jmclnx 3y agoI am showing why I think setting up an IP6 server is harder than IP4. With IP4 I get 1 IP address, IP6 I get 3
- Hikikomori 3y agoWhen do you deal with ip addresses at all in AWS?
- jeroenhd 3y agoMy IPv4 server has 127.0.0.1/8, 10.64.78.37/32, 172.17.2.1/16, and a public IP hidden somewhere. The 172/12 networks I see are usually Docker doing Docker things but I'm still left dealing with three different IP addresses. Not that it matters much, because they all just appeared on the right interfaces and started working. You may need to know some basic things about IPv6 for your firewall ("fe* means local link") but the same is true for IPv4 ("10.* means local network"). I think they're equally difficult to manage, but I can understand how daunting it may look to someone whose been taught networking by outdated textbooks lacking IPv6 like so many other people.