If you or your users rely on Windows Subsystem for Linux (WSL) and have the DNSFilter Roaming Client installed, you might have run into an issue where WSL works fine at first but eventually throws a "no route to host" error. Restarting WSL temporarily fixes it, but the problem keeps coming back.

The Fix: Use Mirrored Networking

The issue comes down to how our roaming client handles networking, which can interfere with WSL's default settings. Fortunately, we’ve found that switching WSL to mirrored networking mode resolves the conflict.

Here's what to do:

1. Create or edit a .wslconfig file in your Windows user directory (C:\Users\YourUsername\.wslconfig)

2. Add the following lines:

   [wsl2]
   
   networkingMode=mirrored

3. Save the file and restart your WSL distros

Once you do this, WSL should be able to access the network without running into the "no route to host" issue.

For more details on .wslconfig settings, check out Microsoft’s documentation.

Let us know if you have any questions or if this fix helps! 🚀