Feature Requests

Add the ability to cleanup from the top level of the MSP console.

Ability to filter the list of roaming client by entering in multiple roaming client ID's/Hostnames

In the Manage Roaming Clients window, it would be very helpful to have a column for (last known) IP Address of the client. For us, we split our clients out into the multiple Sites we have, and we have to use a totally separate platform to view the IP address of the host to thereby identify what Site it belongs to (based on subnet), and then manually put it there.

It would be very beneficial to to able to install a roaming client on windows devices that are set with a static IP address. right now it will work for a period of time and then stop working. there are many scenarios were a static is needed internally and they don't have a static IP from their ISP for the forwarding option to work.

That would be a "nice to have" feature that allow us to list devices and have the date of installation for Windows clients

When is the DNSFilter chrome extension going to be upgraded from manifest v2 to v3? Hopefully before Google completely depreciates V2.

Apple has introduced new possibilities for content on-device filtering on iOS, iPadOS, and macOS. Because traffic is filtered on device there is no network impact. There is already solutions like jamf Safe Internet on the market which have integrated Apples new technology. Performance is a huge factor for us with Roaming clients and it is crucial for our success that DNS Filter is monitoring Apples development and best practices so we can succeed with filtering Apple devices with the solution of DNSFilter. Here is the documentation from Apple about plug-ins for adavanced content filtering of web and socket traffic: https://developer.apple.com/documentation/networkextension/content_filter_providers

We would like to see automatic Site/Policy and roaming client association implemented based on the IP of a roaming client. For example, if a roaming client connects from a private network (IP SMARTWORKING) it should be automatically associated with the “IP SMARTWORKING SITE.” Conversely, if a roaming client connects from a corporate network (IP CORPORATE Y) it should be automatically associated with the “IP CORPORATE Y SITE” site. This would help to figure out which site each roaming client is in and then define site-specific policies for each site. A default site could also be created if the roaming client does not connect from a defined IP. Currently, there is no automatic association between a roaming client's IP and a site defined in DNSFILTER.

Website history

Similar to https://dnsfilter.canny.io/feature-requests/p/duplicate-roaming-clients-in-dashboard and the merged post in that thread: We still see duplicate macOS devices which leads suspicion that agents are not using any unique identifiers tied to a host? I recently uninstalled the package on my own device, reinstalled it and now theres an offline host and an online host in my inventory. How do we ensure that the 'Clean Up Roaming Clients' feature knows which host by hostname to clean up if it only shows 1 host out of the duplicate roaming clients and does not harm the other host which has the same mac address for example?