29 Nov
2022
29 Nov
'22
2:51 p.m.
On 11/29/22 2:56 PM, Scott Gillins via 44net wrote:
I was wondering if you had considered looking at a 4
in 6 tunnel support. I
know that it may seem backwards with a lot of things moving to native v6
but the 44 net is a great resource for hams. One example of why I can see
needing this is a lot of providers, specifically wireless, are doing a
double or triple NAT of their own ipv4 address space. While this is OK for
most internet activities it is not good to support inbound connections. You
do however get a native IPV6 address that is not nated and fully routable.
Having a headend location to support a 4 in 6 tunnel would help a lot of
folks. I do support large networks as part of my day job and would be
willing to help set up and support if you wanted to take this on.
So I've done something like this as part of a dmvpn setup here for another ham
from Mexico. We discovered UDP 4500, 500, IPinIP and any GRE was blocked due
to their provider on their CGN. I setup a static on one side IPv6 GRE tunnel
and routed the IPv4 44net over it for him. Worked great.
Our HamWan remote site setup is a well known way of getting some IPv4 ham net
(and ipv6) space out to poorly connected sites and anyone can set it up (or I
can provision you out of our Tampa site if you don't have a head end).
https://wiki.w9cr.net/index.php/HamWAN_Remote_Site
The 44net IP encap crap needs to die and it's all proprietary so there's no
hope to update it.
73s
--
Bryan Fields
727-409-1194 - Voice
http://bryanfields.net