Packet radio was a big lure to me when I was in high school in the 1990's. The mainstream internet hadn't yet blossomed, and I was always looking to tap into information networks (voice and data) so I could learn and build stuff. At the same time I read an article by Larry Kollar, KC4WZK on the Amateur Packet Radio Network that was floating around on dial-up BBS's and really caught my attention. One of my Elmer's gave me a pile of NE2000 coax LAN ethernet cards. That combined with watching the trace screen on the various NOS programs really helped my learn how it worked. So I was a young person back then, I can say it helped me immensely understand how the internet works.
And I am still learning. (As that is what ham radio is to me). A few years back my internet provider started handing out IPV6 addresses. So on my personal network I started to implement dual stack. And then wondered what good this really does as you are still using a V4 address for the sites you connect to that don't yet support ipv6. Not like you are saving an IPv4 address. Then I learned the next phase would be carrier grade NAT. Fortunately or unfortunately (depending on how you look at it), we are not to that point yet where I live. But you can experiment with the Google NAT64 gateway etc.
Since I have some legacy ipv4 radios., I wouldn't mind trying to run my own NAT64 gateway on Linux. But I haven't gotten that far yet. And the documentation out there is a bit foreign to me yet.
Another thing I have been meaning to try and do is some sort of 10.x.x.x to 44.x.x.x. 1 to 1 NAT thing for the folks doing Broadband Hamnet/AREDN.
My experience is that they don't want it. We offered them a substantial chunk of net 44 space to use instead and they turned it down. The reason is unclear but I suspect it wasn't a technical one. - Brian
On Sun, Sep 03, 2017 at 10:57:11AM -0500, Steve L wrote:
Another thing I have been meaning to try and do is some sort of 10.x.x.x to 44.x.x.x. 1 to 1 NAT thing for the folks doing Broadband Hamnet/AREDN.