4 ms·
I'm fine with 16 but they should have only used the bytes as they were needed, at least for 5 and 6 byte addresses, so those who desire short addresses could bu
by apitman 6mo ago
I'm fine with 16 but they should have only used the bytes as they were needed, at least for 5 and 6 byte addresses, so those who desire short addresses could buy them.
- traderj0e 6mo agoAt least on a LAN, you can set up like fe80::3 . I think. Now I'm not sure if I got that right.
- iso1631 6mo agofe80:: is for link local. You'd want to use something starting fc00:: or fd00:: In your typical home environment, just set your ULA to fd00::12 instead of 192.168.0.12, or fd00:16:34 instead of 192.168.16.34 Yes you'll run into issues if you were to later want to merge your private IPs with someone else, and you should use fd12:3456:7890::12 instead, remembering those extra 10 digits, but its not a problem at home, and no more of a problem with business mergers than ipv4 clashes anyway.
- iso1631 6mo agoMy vrrp address for my dns server at home is 2001:8b0:abcd::53 It's about as easy to remember as 81.187.123.45//192.168.0.53 Almost all ipv6 addresses I encounter start with 2001, so I just need to remember my home prefix is 8b0:abcd, which is about the same length as my home public IP of 81.187.123.45 ::53 means subnet zero host 53, which is easier to remember than which rfc1918 range I used (and basically is the equivalent of remembering the 2001:: prefix) If I have an internal server I'd have on 192.168.4.12 I could address it with 2001:8b0:abcd:4::12 just as easily, with the "4.12" translating to "4::12", and the "81.187.123.45>192.168.x.y" translating to "2001:8b0:abcd:x::y" Just because slacc gives you an extra 64 bits of randomness doesn't mean you need to use them.