Wsl network settings for wifree3: הבדלים בין גרסאות בדף
| (3 גרסאות ביניים של אותו משתמש אינן מוצגות) | |||
| שורה 1: | שורה 1: | ||
| − | When connected to the filter using the WiFree3 software, typically (with default WSL settings), internet access is unavailable in WSL. | + | {{עמוד בעברית|הגדרת רשת wsl לוויפרי3}} |
| + | <br> | ||
| + | {{קישור אנגלית לתצוגת קריאה}} | ||
| + | <br> | ||
| + | When connected to the filter using the WiFree3 software, typically (with default WSL settings), internet access is unavailable in WSL.<br> | ||
| − | To try and resolve this issue, you can configure the network mode in WSL to virtioproxy. | + | To try and resolve this issue, you can configure the network mode in WSL to virtioproxy.<br> |
| − | See [https://wiki.netfree.link/ | + | See [https://wiki.netfree.link/wiki/Bugs_and_their_solutions#No_Internet_Access_in_WSL_.2B_WiFree3 here] how to do it using the WSL Settings tool.<br> |
| + | If you don’t have the WSL Settings software, here’s a manual guide (credit: grock) to configure it manually:<br> | ||
| − | + | '''Prerequisites'''<br> | |
| − | + | Ensure you are using WSL 2, as virtioProxy is specific to WSL 2.<br> | |
| − | Prerequisites | + | You need administrative privileges to modify WSL configuration files.<br> |
| − | Ensure you are using WSL 2, as virtioProxy is specific to WSL 2. | + | Verify your WSL version by running wsl --version in a Windows Command Prompt or PowerShell. Ensure you have a recent version (e.g., WSL 2.0.14 or higher).<br> |
| − | You need administrative privileges to modify WSL configuration files. | + | Back up any important data or configurations before making changes.<br> |
| − | Verify your WSL version by running wsl --version in a Windows Command Prompt or PowerShell. Ensure you have a recent version (e.g., WSL 2.0.14 or higher). | + | '''Steps to Change Network Mode to virtioProxy''' |
| − | Back up any important data or configurations before making changes. | + | *Open or Create the .wslconfig File: |
| − | Steps to Change Network Mode to virtioProxy | ||
| − | Open or Create the .wslconfig File: | ||
The .wslconfig file is used to configure global WSL 2 settings and is located in your Windows user profile directory (%UserProfile%.wslconfig). | The .wslconfig file is used to configure global WSL 2 settings and is located in your Windows user profile directory (%UserProfile%.wslconfig). | ||
| − | Open a text editor (e.g., Notepad, VS Code) and navigate to C:\Users<YourUsername>.wslconfig. | + | *Open a text editor (e.g., Notepad, VS Code) and navigate to C:\Users<YourUsername>.wslconfig. |
If the file does not exist, create a new file named .wslconfig. | If the file does not exist, create a new file named .wslconfig. | ||
| − | Edit the .wslconfig File: | + | *Edit the .wslconfig File: |
Add or modify the following section in the .wslconfig file to set the networking mode to virtioProxy: | Add or modify the following section in the .wslconfig file to set the networking mode to virtioProxy: | ||
| − | + | [wsl2] | |
| − | [wsl2] | + | networkingMode=virtioProxy |
| − | networkingMode=virtioProxy | + | Save the file and close the text editor.<br> |
| − | Save the file and close the text editor. | + | '''Shut Down WSL:''' |
| − | Shut Down WSL: | ||
To apply the changes, you need to stop all running WSL instances. | To apply the changes, you need to stop all running WSL instances. | ||
Open a Command Prompt or PowerShell and run: | Open a Command Prompt or PowerShell and run: | ||
wsl --shutdown | wsl --shutdown | ||
| − | This ensures that the WSL engine fully stops and will respect the new configuration when restarted. | + | This ensures that the WSL engine fully stops and will respect the new configuration when restarted.<br> |
| − | + | ||
| − | + | '''Restarting WSL:'''<br> | |
| − | |||
| − | + | Restart WSL and check if the issue is resolved.<br> | |
| − | + | To verify that the setting has taken effect, rrun the following command '''inside WSL'''<br> | |
| − | |||
| − | |||
| − | wslinfo --networking-mode | + | wsl wslinfo --networking-mode |
| + | If the configuration was applied successfully, you should see virtioproxy as the result. | ||
גרסה אחרונה מ־11:48, 5 ביוני 2025
לעברית לחצו כאן
To switch from edit view to read view
To search in the Wiki
When connected to the filter using the WiFree3 software, typically (with default WSL settings), internet access is unavailable in WSL.
To try and resolve this issue, you can configure the network mode in WSL to virtioproxy.
See here how to do it using the WSL Settings tool.
If you don’t have the WSL Settings software, here’s a manual guide (credit: grock) to configure it manually:
Prerequisites
Ensure you are using WSL 2, as virtioProxy is specific to WSL 2.
You need administrative privileges to modify WSL configuration files.
Verify your WSL version by running wsl --version in a Windows Command Prompt or PowerShell. Ensure you have a recent version (e.g., WSL 2.0.14 or higher).
Back up any important data or configurations before making changes.
Steps to Change Network Mode to virtioProxy
- Open or Create the .wslconfig File:
The .wslconfig file is used to configure global WSL 2 settings and is located in your Windows user profile directory (%UserProfile%.wslconfig).
- Open a text editor (e.g., Notepad, VS Code) and navigate to C:\Users<YourUsername>.wslconfig.
If the file does not exist, create a new file named .wslconfig.
- Edit the .wslconfig File:
Add or modify the following section in the .wslconfig file to set the networking mode to virtioProxy:
[wsl2] networkingMode=virtioProxy
Save the file and close the text editor.
Shut Down WSL:
To apply the changes, you need to stop all running WSL instances.
Open a Command Prompt or PowerShell and run:
wsl --shutdown
This ensures that the WSL engine fully stops and will respect the new configuration when restarted.
Restarting WSL:
Restart WSL and check if the issue is resolved.
To verify that the setting has taken effect, rrun the following command inside WSL
wsl wslinfo --networking-mode
If the configuration was applied successfully, you should see virtioproxy as the result.