I would love if standard IP addresses used hex by default. C0.A8.1.1 or 7F.0.0.1
Comment on What is the deal with IPv6?
False@lemmy.world 10 hours ago
V4 is easier to work with (not using long hex addresses and it’s concepts are more familiar) and works fine for most everyone’s use cases. So if it ain’t broke don’t fix it and low return on investment for most businesses. If you switch you have you do some awkward stuff where you maintain both.
What are these many advantages you speak of, other than global address space? If I’m an average business and may need one to three external ipv4 addresses, which are around $30/yr each, how much labor is it going to cost to migrate and when will I break even? Surely my sysadmin’s time is better spent on things like security hardening?
antlion@lemmy.dbzer0.com 6 hours ago
twkm@programming.dev 44 minutes ago
They are: ping 0xC0.0xA8.1.1 or 0x7F.1
Standard scanf number parsing is generally used though some OSes reject that.
Randelung@lemmy.world 8 hours ago
One of the main issues I think is holding IPv6 back is that we keep needing to memorize IPs and type them by hand. 192.168.0.16, 172.16/12, and 10.0.0.0/8 are easy to remember, and usually it’s just the last number that’s important, anyway, because we all use 192.168.1.0/24 by default.
But then IPv6 comes along with /48 prefixes and endless numbers to read, analyze (same subnet? typos?), memorize or write down. Ain’t nobody got time for that.
IPv6 would have to integrate some sort of DNS resolver on a network level so that people can work with computer names. That would make the hostname actually relevant and not have every Windows be called DESKTOP-W38D6M5P. If you already have a separate DNS service, it’s only the registration step that has slightly more friction, but still.
AA5B@lemmy.world 5 hours ago
This is a bigger deal than you may think. Those of us stubborn enough to use one of the other defined internal network ranges already hit more obstacles than we should, and that difference should be trivial to non-existent.
For me the latest is a smart home device that hard-coded 192.168.1.x, so I am not able to connect it to my network
False@lemmy.world 4 hours ago
Most network devices can have multiple IPs. Assign 192.168.1.1 to your router (in addition to your normal up) and it should probably start routing traffic to that device
False@lemmy.world 4 hours ago
You should see the unfinished proposal for ipv8. The authors think yes to a large degree, though not how you’re thinking.
www.ietf.org/archive/id/draft-thain-ipv8-00.html