When using the DNSFilter Roaming Client with Windows Subsystem for Linux (WSL), some users experience recurring connectivity issues such as:

• "No Route to Host" errors
• WSL networking that works temporarily after restart, then fails again

These issues occur because the Roaming Client interferes with WSL’s default NAT networking mode.

There are two methods to resolve this issue:

Method one: Use Mirrored Networking (recommended)

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. 

🚨 Important: This solution requires Windows 11 version 22H2 or later, WSL version 2.0.9+.

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 distributions

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

Method two: Configure DNS Manually (if Mirrored method isn't supported)

1. Open the WSL distribution

2. Remove the auto-generated resolv.conf:

   sudo rm /etc/resolv.conf
   

3. Create a new resolv.conf:

   sudo nano /etc/resolv.conf
   

   Add these external DNS servers and save the update:

   nameserver 1.1.1.1
   nameserver 8.8.8.8 

4. Create an additional file to ensure the DNS server remains permanent:

   sudo nano /etc/wsl.conf
   

   Add this network command and save the update:

   [network] 
   generateResolvConf = false 

5. Restart WSL:

   wsl --shutdown
   

The WSL instance now uses alternate DNS settings. Verify the settings with this command:

cat /etc/resolv.conf

Additional Resources

• Microsoft WSL troubleshooting
• Microsoft WSL configuration

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