IPv6 Support for Roaming Clients
in progress ( live <90 days )
Mark Porter
Carl Levine When do you expect IPv6 support for the macOS RC? I heard from support we should disable IPv6 as part of our troubleshooting and I'm interested to know when you fully expect to support it and if there's anything we need to do manually to implement it once it hits prod.
Jarrod Higgins
Is IPv6 support GA in 1.15.3? If so, does it still require a registry change?
Carl Levine
Jarrod Higgins: Still requires a registry change. UpstreamIpVersion registry key can be changed in HKLM\Software\DNSFilterAgent\Agent to prioritize it. The default is empty on UpstreamIpVersion, which defaults the agent to IPv4. To set IPv6 as default, put the following value into the field for this key:
ipv6 / ipv6-ipv4 / ipv4
This will prioritize IPv6, then fall back to an auto-detect, and finally IPv4.
Thomas J Sweet
Carl Levine How about on iOS?
Sam Rankl
Guys, this is starting to cause more issues for us. Comcast and others are moving to IPv6. We can't have our employees having to disable DNSFilter roaming client when working remote. This feature has been showing as "Live in 90 days" for months now. A little more clarity would be good. We had access to the beta IPv6 client sometime ago, and can no longer download it. Is there a new IPv6 beta client we can test and report back on?
Carl Levine
Sam Rankl: Your request was certainly timely. We just pushed v1.15.2 Beta of the Windows Roaming Client about 30 minutes ago. While IPv6 is not turned on by default, the UpstreamIpVersion registry key can be changed in HKLM\Software\DNSFilterAgent\Agent to prioritize it. This version fixes a number of issues that were present in prior iterations of the Windows RC specific to this function, and those details are available in the release notes (https://dnsfilter.canny.io/changelog/11-27-november-27-windows-roaming-client-1152-beta). We welcome your honest and candid feedback on this functionality in this beta version.
B
Brendon Haughey
Carl Levine: What value do we need to set the UpstreamIpVersion key to in order to prioritize IPv6?
Carl Levine
Brendon Haughey: The default is empty on UpstreamIpVersion, which defaults the agent to IPv4. To set IPv6 as default, put the following value into the field for this key:
ipv6 / ipv6-ipv4 / ipv4
This will prioritize IPv6, then fall back to an auto-detect, and finally IPv4.
Bogdan Pavel
Is this something the DNSFilter team can implement, or is it not feasible and we need to find/move to other products ?
B
Brendon Haughey
Can we get an update on this please. It's bizarre that this request has been open for 6 years with no end in sight.
C
Christopher Burrell
Need v6 support for Roaming clients on all endpoints
Steve Staden
All, I've updated this item to be focused on roaming clients while creating a new one dedicated to the IPv6 resolver here - https://dnsfilter.canny.io/feature-requests/p/ipv6-support-for-dnsfilter-resolvers. We've moved all the voters on this post to that one so it has the same vote count. I wanted to separate them out as we have customers who have different needs ultimately and wanted to be transparent.
Shaun Bentzen
Hi, It's been a long long while on this specific issue and it's holding me back for some projects.
I can't imagine that enabling DNSFilter to have IPv6 resolver addresses is altogether that difficult, what's the timeline on getting this going?
Malinda Rathnayake
I reached out to support, same response, we deployed a new site with IPV6 dual-stacked without DNS filter, FortiDNS seems to be working fine with V6 via the UTM, but it sucks we still dont have this on the roaming clients
Dirk Van den Abbeele
I am comparing several companies with dns filtering as a core business. Most of them support ipv6. This could become a dealbreaker for me (and probably also for others).
Load More
→