3 ms·
Comment #42069 on "HN doesn't understand the Internet Protocol". This opinion is frequently repeated here on HN but -- you CAN'T use IPv4 internally and expect
by orangeboats 3y ago
Comment #42069 on "HN doesn't understand the Internet Protocol". This opinion is frequently repeated here on HN but -- you CAN'T use IPv4 internally and expect to talk to external IPv6 hosts.
How would this IPv4 internal host (say 192.168.1.10) send a packet destined to 2001:db8::1? You can't stick a 128-bit IPv6 address into your IPv4 packet - there are only 32 bits available for the destination address inside its header.
NAT is not magic, it cannot extract a 128-bit number out of your 32-bit number.
- hitpointdrew 3y agoThis patently false, you should do more research before you make comments to inflate your ego. For your education: https://en.m.wikipedia.org/wiki/NAT64 https://en.m.wikipedia.org/wiki/NAT64
- orangeboats 3y agoIronically, you are the one who needs to do more research. I have deployed NAT64 in multiple networks before. NAT64 is used when you have _internal_ IPv6 hosts who want to reach the _external_ IPv4 hosts. In order words, 2001:db8::1 can send something to 198.51.100.1 but not vice versa. Your proposal is that we use IPv4 _internally_ since you think "internal IPv6 is overly complex" and we should "NAT to internal IPv4's". It doesn't exist since IPv4 is inherently forwards incompatible. "HN doesn't understand the Internet Protocol" strikes again.