On Fri, 19 Jul 2019, Phil Karn wrote:
On 7/18/19 23:12, Holger Baust wrote:
Is there a IPv6 Block registered to HAMs?
...
Most ISPs that natively support IPv6 also support prefix delegation. They'll typically give you a /64 that you can hand out on your LAN with DHCPv6 or stateless autoconfiguration (e.g., advertise with the Linux radvd daemon). Some will give you more than one /64 if you ask, but nothing actually says you must use a /64 only on a single LAN. You can always divide it further if you like, and with twice as many bits in the host part of an IPv6 /64 as in the entire IPv4 address space, this can't be hard.
Some home router firmwares seem to insist on /64 for using the delegation, so it might be tricky on some setups. But should be possible to put together at least on a Linux box with some creative configuration.
The usage of IPv6 has some problems. First a lot of software has to be recompiled or completedly rewritten,
I don't think so. IPv6 has been out for a very long time.
Right, for most applications "completely rewritten" is not true; just some small parts need to be rewritten in software which uses older low-level network socket APIs.
Applications using higher-level networking APIs (such as "fetch this URL for me please" APIs in libraries and operating systems) don't need to be touched as the code behind those APIs has already been fixed years ago. I've got a lot of experience in IPv6 support validation and configuration at $work, and with my hobby systems too, so I know this from practice.
Applications specifically dealing with things as IP address allocation or DNS data manipulation: yes, those need a lot more work. Such as the amprnet address allocation portal. Not a small task.
the other problem sits between several chairs and keyboards. (as in a lot of other internet companies)
Right, but this thing needs to be done eventually. The world is moving on.
Some developers, admins and ops do not understand the new addressing or routing and some hardware vendors do not give IPv6 a priority in developing...
As I said, IPv6 is much more widely supported than many people realize and the only problem is just getting people to turn it on.
It's a good idea to check this graph yearly, stare at the growth between 2015 and today for a while, do a little mental extrapolation from there, and think of the consequences:
https://www.google.com/intl/en/ipv6/statistics.html
Some 25% to 30% of client traffic to Google use IPv6 *today*. Up from 5% at the beginning of 2015. There's some weekly variance due to office/home use if you zoom in (weekends: more IPv6 traffic towards Google).
It's getting turned on a lot right now. The wheel is rolling, the momentum is there.
As for the difficulty: I didn't find it that hard. The addresses are harder to remember. More cut-n-paste work, but a lot of it can be automated, and DNS help once you bother to set it up. But the routing is... basically just the same as IPv4, just with more bits!
Commercial hardware hardware and software vendors are moving pretty fast, and have mostly implemented IPv6 already. All major network operators, ISPs and such absolutely *require* IPv6 support when purchasing anything, and have done so for quite some time.
Smaller vendors are lagging more (think of the APRS iGate appliances, remoterig boxes, and other gadgets made for small audiences). But I suspect the ease of setting up direct remote access to those gadgets, thanks to the lack of NAT in IPv6-enabled residential networks, will get that ball moving soon. Just open up the firewall - the thing will have it's own public IPv6 address just like that, no need to do port forwarding!
- Hessu, OH7LZB / AF5QT
On 7/19/19 03:01, Heikki Hannikainen wrote:
Smaller vendors are lagging more (think of the APRS iGate appliances, remoterig boxes, and other gadgets made for small audiences). But I suspect the ease of setting up direct remote access to those gadgets, thanks to the lack of NAT in IPv6-enabled residential networks, will get that ball moving soon. Just open up the firewall - the thing will have it's own public IPv6 address just like that, no need to do port forwarding!
Amen! I'm amazed at the handsprings some people perform with IPv4 port forwarding when they could just use IPv6 instead. When I'm away from home, I regularly use IPv6 to reach the individual hosts beyond my home router. (Amazing how Raspberry Pis just seem to breed...)
Because I use a general purpose Linux box as my home router, I also run a lot of network-related software directly on it, e.g., Bit Torrent, Squid, OpenVPN, (formerly) TOR, and of course sshd so they can all use my one routable IPv4 address without port forwarding. That's one of the best things about building your own router.
Phil
-
Heikki Hannikainen -
Phil Karn