Sujet : Re: Anybody Using IPv6?
De : bowman (at) *nospam* montana.com (rbowman)
Groupes : comp.os.linux.advocacyDate : 16. May 2025, 20:13:04
Autres entêtes
Message-ID : <m8ph1vFm3lmU3@mid.individual.net>
References : 1 2 3 4 5
User-Agent : Pan/0.160 (Toresk; )
On Fri, 16 May 2025 08:44:53 -0400, CrudeSausage wrote:
On 2025-05-15 21:20, rbowman wrote:
On Thu, 15 May 2025 21:01:16 -0400, CrudeSausage wrote:
Why the IPx6 hatred?
You can remember 192.168.1.2. Good luck with fe80::261:5f21:d38a:aa02.
Would you like to predict the IPv6 address of 192.168.1.3?
Good point.
The problems are not insurmountable but there will be pain. I did a
browser based map so a dispatcher would only see the units and incidents
they were responsible for. That was determined by the GUIs on their
machine.
The back end node.js server matched by IP. When a browser connected you
could query to find its IP. Similarly, when one of the GUIs sent
information, you could get its IP. So, if a GUI sent a list of active
units from 192.168.1.222 it would be sent to the browser on
192.168.1.222.
It worked for years until browsers started identifying with their IPv6
addresses and there was no way to get from IPv6 to IPv4 to match them up.
Browsers do have a configuration setting to use IPv4.
In this case the GUI code did not support IPv6 and that would have caused
difficulties with other backend services.
Considering all our clients were on Windows LANs using IPv4 that wouldn't
have worked anyway.
Going to IPv6 sounds good by there's a hell of a lot of technical debt.