IPv6 and CGNAT – how do we future-proof remote Flex access?

Hi all,

I’ve been running my Flex remote for a while and hit a wall with CGNAT. Some of you probably know the drill, SmartLink just doesn’t work in that situation since the client can’t reach the radio directly. Flex has a helpdesk article on it: link here

Sure, there are workarounds:

• SoftEther VPNAzure from a Pi or other device on the LAN, it does connect, but adds complexity and latency, sometimes enough to make SmartSDR unhappy.
• ZeroTier at layer-2, which some report as working fine with reasonable latency and low packet loss.

In my own case, I ended up paying extra every month just to get a public IPv4 address for my remote QTH so I could avoid CGNAT. It works, but honestly it feels like money spent on a patch for a problem that shouldn’t exist if the radio supported IPv6.

Here’s the bigger picture:

• CGNAT is getting more and more common, especially on mobile ISPs and satellite like Starlink.
• Public IPv4 addresses are scarce and in many cases you have to pay extra to even get one.
• IPv6 often just works, even when IPv4 is broken. I’ve seen this firsthand, my remote site was still reachable over IPv6 while the v4 side was dead.
• Yet Flex gear today doesn’t really speak IPv6.

I’m not saying SmartLink is bad, it’s a good service, but being 100 % dependent on it and IPv4 feels fragile. A bit of IPv6 support would open the door to more direct, simpler setups for remote operation and make the radios more future-proof.

So, questions for the group:

• Anyone here already using IPv6 with a Flex, even if only via VPN or special configs?
• Have you also run into situations where IPv4 failed but IPv6 saved the day?
• Would you also like to see Flex consider at least basic IPv6 support?

I’d love to hear other experiences. Maybe together we can put together a summary of the common pain points (CGNAT, latency, VPN options) and show Flex that this isn’t just a niche request.

73,
Mikel