19 Jul
2019
19 Jul
'19
9:04 a.m.
On 19/07/19 17:26, Phil Karn wrote:
IPv6
was discussed in detail a year or two ago in here. The consensus
was that a 44net like block was unnecessary and may even cause issues.
Instead it was proposed that hams use parts of their (in many cases)
existing IPv6 allocation, and the subnets reserved for ham radio use go
into database that can be used to generate firewall rules. For example,
I have a /56 allocated by my ISP, but I'm currently only using one /64.
I will eventually use a couple of /64s for other things as IoT and smart
devices become more commonplace, but the vast majority will be unused.
I can allocate one or more of those to ham radio use. Similarly, those
who get tunnels from he.net will have more than ample address space to
allocate for ham radio.
As hams are supposed to be leaders in technology, I would like to see
IPv6 adopted as much as possible. Like the wider world, there's no
reason we can't run dual stack alongside our 44.x IPv4 addresses.
Pretty much all my mainstream
software (web browser, email client, etc)
supports IPv6 and it all "just works". As for getting addresses, if
you're stuck behind CGN with no IPv6, there are ways to get an IPv6
address to you. Old favourites like OpenVPN can do it, if you have a
VPS or know someone who can route a block to you.
As do I, and same thing. It just works, it's
only if I look up what
address I'm connecting to that I can tell if I'm running IPv4 or IPv6.
Australia still
lags behind at the ISP customer level, but there are
ISPs (like mine!) who offer IPv6 and have it enabled by default. Pity
they don't enable it by default on the routers they provide. Easily
done fr us tech people though. If IPv6 is on ovver, I will enable it on
both my equipment and those of others I help out.
--
73 de Tony VK3JED/VK3IRL
http://vkradio.com
Is there a
IPv6 Block registered to HAMs?
If there isn't, I'm sure there could be. But
this isn't strictly
necessary just to run IPv6 over ham radio. Hurricane Electric (HE) still
runs their free IPv6 tunnel broker service, which I still use at home
alongside native IPv6 from my own ISP (Spectrum Cable, formerly Time
Warner Cable). By default they'll give you a /64 that you can have
tunneled to any routable IPv4 address you like. To optimize routing you
can choose the closest from a long list of tunnel gateways around the
world and if you pass a few quizzes to show that you know what you're
doing, they'll also give you a /48. I sub-delegated a /64 from my /48 to
the Mt. Carmel HS ham club network (W6SUN) where I am a mentor. HE will
even delegate PTR zones, again if you can show you know what you're doing.
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.
I think you'd have to use static addressing or DHCPv6 to assign
addresses if you split a /64 but don't quote me on that. ;)
While in theory these delegated prefixes can change, in my experience
this is very rare. Also, a major design consideration in IPv6 was to
make large-scale readdressing as painless as possible. (I wasn't
personally involved in IPv6 development but I was active in the IETF
during that time and I did follow the discussions.)
My native prefix is static,
that is an option that my ISP offers for a
small fee.
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. Every major OS
has had it for years, and it is stable and well supported. More and more
ISPs support it natively, and even if yours don't you can still use a
tunnel broker like HE, provided you have a single routable IPv4 address
for tunneling (i.e., you're not on carrier-grade NAT). The one ISP I use
that does have carrier grade IPv4 NAT is Verizon Wireless but they also
support native IPv6 so there's no problem. the other
problem sits between
several chairs and keyboards. (as in a lot of other internet companies)
If by this
you mean we have to convince people to simply turn it on, you
are correct. In my personal experience, the biggest practical drawback
to IPv6 is that it is enabled on very few public WiFi hotspots. Since
many of them are too overloaded to be useful anyway, probably by
automatic iOS and Android app updates, I generally just fall back to the
hotspot in my Verizon iPhone. But at home, I use IPv6 quite heavily. It.
Just. Works. Really, it does. 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. I think