19 Jul
2019
19 Jul
'19
10:01 a.m.
On 7/19/19 01:04, Tony Langdon 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.
Yes, that's exactly
my thinking too.
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.
Yup. What you
said.
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. ;)
Probably. I'm a fan of stateless autoconfiguration mainly because It
Just Works, but DHCPv6 isn't that hard either.
I haven't looked, but I don't see any fundamental reason why stateless
autoconfiguration can't be used with smaller host fields (particularly
one only 48 bits wide).
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.
Side question: do you know a good
public VPN provider who supports IPv6?
I'd like to recommend one to those who are stuck behind CGNs or can't
otherwise use HE's tunnel broker.
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.
Right. And having both IPv4 and IPv6 has saved my bacon more than once.
E.g., if I do something remotely that accidentally breaks an IPv4
interface address, firewall rule or routing entry, I can often get back
in with IPv6 and fix the problem. Or vice versa.
The requirement that every interface support multiple IPv6 addresses can
also come in very handy here. It's one of the reasons I still use my HE
tunnels alongside native Spectrum IPv6 addresses.
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.
I have long built all my own routers from scratch with Linux, so I don't
closely track commercially available home routers. But I'm pleased to
see that the newer ones among friends and family members do support IPv6
-- but only if it's enabled. Often the only real problem is getting the
firewall rules set properly since by default many disable inbound
sessions to provide the same sort of false security as IPv4 NAT...
Phil