News for hackers. Stuff that matters.
[dead]
Re:250M-plus reserved IPv4 addresses could be released by growse on Friday February 09, 2024 @12:06PM (#39317212)
> Make them all inter-compatible and backward-compatible by modifying the packet structure to accept a variable length address.

"Simply draw the rest of the Owl".

Re:250M-plus reserved IPv4 addresses could be released by mike256 on Friday February 09, 2024 @12:09PM (#39317255)
And a real IPv6 (128 bit) address would look like 164.32.74.105.164.32.74.105.164.32.74.105.164.32.74.105
Re:250M-plus reserved IPv4 addresses could be released by Workaccount2 on Friday February 09, 2024 @12:04PM (#39317170)
Like clockwork this comment shows up...
Re:250M-plus reserved IPv4 addresses could be released by Macha on Friday February 09, 2024 @12:12PM (#39317313)
Often it's even the same users, as if all the reasons it wouldn't work were't explained to them the last times they reflexively suggested it at the mention of IPv6:

https://news.ycombinator.com/item?id=39100317

https://news.ycombinator.com/item?id=36996003

https://news.ycombinator.com/item?id=35047061

...

Re:250M-plus reserved IPv4 addresses could be released by Ekaros on Friday February 09, 2024 @12:06PM (#39317205)
Can you explain exactly how a IPv4 host would send packet to 1.2.4.5.6. What fields inside a fixed IP packet it would set to achieve such?
Re:250M-plus reserved IPv4 addresses could be released by p1mrx on Friday February 09, 2024 @12:24PM (#39317504)
You post a strawman IPv6 address to HN every month or so. Why not take a minute to learn what a real address looks like?

For example, 2eff:ff:a0ee::/54 is a prefix and 2eff:ff:a0ee::dead:beef is an address within that prefix. It is invalid for "::" to appear more than once, as that would be ambiguous.

Re:250M-plus reserved IPv4 addresses could be released by dheera on Friday February 09, 2024 @01:28PM (#39318396)
Because nobody has fixed the bad UX yet, I'm still on IPv4, and like 5 million other people, have no incentive to move to IPv6 until the consortium of PMs of IPv6 do some user research (e.g. read HN) and work together to make the UX better or invent a better successor that people actually want to use.

They're all wondering why IPv6 adoption is so slow, I'm telling them right here plain and simple.

Re:250M-plus reserved IPv4 addresses could be released by p1mrx on Friday February 09, 2024 @01:49PM (#39318694)
You're trying to close the door after the horse has left the barn and started a worldwide colony of horsepeople.

IPv6 isn't perfect, but it's not really practical to change the fundamentals of a 25 year old protocol.

Re:250M-plus reserved IPv4 addresses could be released by JackSlateur on Friday February 09, 2024 @12:16PM (#39317376)
By that logic, ipv6 would be 1.2.3.4.1.2.3.4.1.2.3.4.1.2.3.4

Easy to remember, indeed

Re:250M-plus reserved IPv4 addresses could be released by Macha on Friday February 09, 2024 @12:18PM (#39317398)
Address with patterns are indeed easy to remember, see how easy 1:2:3:4:: is to remember. So all we have to do is allocate everyone an artisanally crafted address with easy to remember patterns /s
Re:250M-plus reserved IPv4 addresses could be released by exe34 on Friday February 09, 2024 @12:33PM (#39317665)
Have you heard of domain names? They can be very memorable!
Re:250M-plus reserved IPv4 addresses could be released by dheera on Friday February 09, 2024 @01:30PM (#39318443)
- 8.8.8.8 is IPv4 google DNS

- What is IPv6 google DNS? Hell if I can remember it. 2001:4680:something?

Guess which one is going into the DNS config of a new machine that I have to bring up and am forced to deliver results on short notice.

Re:250M-plus reserved IPv4 addresses could be released by JackSlateur on Friday February 09, 2024 @02:51PM (#39319637)
And why on earth would you remember 8.8.8.8 in the first place ?

For almost all the thing, I use DNS For DNS resolvers, I use root servers

Never shall I use 8.8.8.8 : why would I ..

Re:250M-plus reserved IPv4 addresses could be released by growse on Friday February 09, 2024 @02:28PM (#39319296)
It's Google's prefix (`2001:4860:4860`) with `8888` and `8844` on the end.

If you can't remember that, the problem's not the protocol.