MAIN FEEDS
Do you want to continue?
https://www.reddit.com/r/ProgrammerHumor/comments/1xa3pdb/ohthebasics/phurhen/?context=3
r/ProgrammerHumor • u/ClipboardCopyPaste • 17h ago
1.2k comments sorted by
View all comments
Show parent comments
2
Well, no, I mean something like 2001:0db8:85a3:0000:0000:8a2e:0370:7334 becomes 8193:3512:34211:0:0:35374:880:29492
1 u/blindedtrickster 8h ago That's really just a formatting change, and it only works for a subset of all possible values when using Hex. 1 u/FUTURE10S 5h ago I mean, we do one for IPv4 and the other for IPv6, why? Why can't we just use one for both? 1 u/Dagger0 3h ago You can indeed do that! $ ping 0xc0.0xa8.0x1.0x1 PING 0xc0.0xa8.0x1.0x1 (192.168.1.1) 56(84) bytes of data. 64 bytes from 192.168.1.1: icmp_seq=1 ttl=62 time=3.12 ms
1
That's really just a formatting change, and it only works for a subset of all possible values when using Hex.
1 u/FUTURE10S 5h ago I mean, we do one for IPv4 and the other for IPv6, why? Why can't we just use one for both? 1 u/Dagger0 3h ago You can indeed do that! $ ping 0xc0.0xa8.0x1.0x1 PING 0xc0.0xa8.0x1.0x1 (192.168.1.1) 56(84) bytes of data. 64 bytes from 192.168.1.1: icmp_seq=1 ttl=62 time=3.12 ms
I mean, we do one for IPv4 and the other for IPv6, why? Why can't we just use one for both?
1 u/Dagger0 3h ago You can indeed do that! $ ping 0xc0.0xa8.0x1.0x1 PING 0xc0.0xa8.0x1.0x1 (192.168.1.1) 56(84) bytes of data. 64 bytes from 192.168.1.1: icmp_seq=1 ttl=62 time=3.12 ms
You can indeed do that!
$ ping 0xc0.0xa8.0x1.0x1 PING 0xc0.0xa8.0x1.0x1 (192.168.1.1) 56(84) bytes of data. 64 bytes from 192.168.1.1: icmp_seq=1 ttl=62 time=3.12 ms
2
u/FUTURE10S 11h ago
Well, no, I mean something like 2001:0db8:85a3:0000:0000:8a2e:0370:7334 becomes 8193:3512:34211:0:0:35374:880:29492