[BUG]There is UNEXPECTED WiFi option in v2307.40000.5.0_x64_Release-Nightly-MindTheGapps-13.0-RemovedAmazon

[Snowlights2022]

Describe the bug | 描述一下这个错误

I apologise for some screenshots without English. I added detailed descriptions in English to solve the problem.

The screenshot was made when WSA cannot connect to Internet.It shows a option ui different from repo's help.There is no VirtWiFi and Internet. I apologise for I didn't make a screenshot when WSA can connect to Internet. At that time, it shows Fake WiFi or nothing, just like screenshot above.

Steps to reproduce the issue | 重现该问题的步骤

Advanced setting->Manage developer setting->click search->search WIFI->click WIFI->See the screenshot above

Expected behaviour | 预期的行为

Just like screenshot above, and WSA can connect to Internet sucessfully.

Downloaded Build Of WSA | 已下载的WSA版本

VERSION: v2307.40000.5.0_x64_Release-Nightly-MindTheGapps-13.0-RemovedAmazon SOURCE: just from this repo's realease.

Windows build number | Windows构建号

10.0.22631 Build22631.2262 ni_release

PC Specification | 个人电脑规格

Additional context | 额外的背景

• 159

  Differently, I saw FakeWifi sometimes when WSA was connected to the Internet. Once I see this again, I will attach the screenshot to this issue.

• Hyper-V settings The screenshots were made with Hyper-V Manager form Microsoft.

  

  Having tried the fixes listed in repo's guide and using the method form windows settings,find 'apps' from bar, then find WSA, touch'...',Advanced settings, then try to repair or reset , it didn't work. After reset my Windows Internet settings for times, I find that WSA sets virtual network adapter WSLCore for Internet. That is a internal network. But it didn't work, my WSA still has no Internet.

  

At the same time, WSL uses virtual network adapter WSL for Internet. That is also internal, but different form WSA, it works. It seems like a bridged network? Once I confirmed it, I will attach details here. I think there is wrong settings for WSLCore , but I don't know how to find it.

• Present Situation

  Before I totally reset my Internet settings from Windows settings, WSA can get access to Internet sometimes. It shows FakeWifi in Android settings. At that time it even can cowork with Cloudflare WARP. But after reset, WSL reloaded that WSL, and connected to Internet successfully. WSA now has no Internet, NO Internet, NO VPN can work with WSA. I changed advaced settings Local network access many times, no differences yet.

• If more info needed, just @Sonwlights2022 , I am waiting for solutions!

[Snowlights2022]

I want to add that the official WSA 2307.40000.5.0 from ms store works without such problem on my laptop.

[arishwin]

here is the screenshot with FakeWifi:

However, I would like to add, that after I click on that, it does not appear in the WiFi settings:

And saved networks shows that VirtWifi is disconnected:

[Snowlights2022]

There may be bugs from official WSA about this condition. But it seems still unsolved now in v2308. I will stay at v2306 until Microsoft fixed the bug or I get a easier way to alleviate this problem.

[MustardChef]

There may be bugs from official WSA about this condition. But it seems still unsolved now in v2308. I will stay at v2306 until Microsoft fixed the bug or I get a easier way to alleviate this problem.

@Snowlights2022 Does the internet work on the official 2308 builds of WSA?

From what I have found, disabling your Antivirus Firewall and using Windows Firewall may fix internet issues in some cases. Please could you try this if this applies to you.

[d0j1a1701]

It seems that this issue is related to the proxy tool (for me, Clash Meta).

When you use a proxy, the system seems to automatically apply the proxy to WSL, this behavior is called "autoproxy", here is the configuration in my C:/Users/<omit>/.wslconfig:

[experimental]
autoMemoryReclaim=gradual  # gradual | dropcache | disabled
networkingMode=mirrored
dnsTunneling=true
firewall=true
autoProxy=true

In this case, WSL will automatically set up an agent consistent with the host, and the Hyper-V Manager shows the WSL virtual switch in "internal" state. Testing has shown that all traffic from WSL goes through the agent.

However, WSA does not seem to automatically set up a proxy. The Hyper-V Manager shows that the WSA virtual switch is in "internal" state, but the WSA settings indicate that there is no Wi-Fi connection and internet access is not available.

So I tried to manually set up a proxy by running the following command in Powershell to manually set WSA to use a host proxy:

$WinNetIP=$(Get-NetIPAddress -InterfaceAlias 'vEthernet (Default Switch)' -AddressFamily IPV4)
adb connect 127.0.0.1:58526
adb shell settings put global http_proxy "$($WinNetIP.IPAddress):7890"

After the issue was resolved, all traffic from WSA went through the host proxy via the "FakeWifi" network.

[d0j1a1701]

Also, I hope developers can add an option to automatically execute a script to set up a proxy after WSA starts.

[MustardChef]

@d0j1a1701 Thank you, we will consider this for our WSAUtilities project. So just to confirm, you were able to successfully set up a proxy with WSA without any issues to the internet. (Most people attempting to use any kind of proxy lose internet access after/when it is applied).

[d0j1a1701]

@MustardChef Yes. The proxy client Clash Meta I use on Windows exposes a mixed type proxy of http/socks5 on 0.0.0.0:7890, all my configurations above are based on this.

[d0j1a1701]

@MustardChef I don't know if it's possible to make WSA use the same "mirror" network mode as WSL

Or manually specify the virtual switch used by WSA (such as "Default Switch")

[d0j1a1701]

Update: I used the "Auto-run script" feature of KernalSU and placed the executable autoproxy.sh in /data/adb/boot-completed.d.

settings put global http_proxy "http://127.0.0.1:7890"

Solved the problem.

[MustardChef]

@MustardChef Yes. The proxy client Clash Meta I use on Windows exposes a mixed type proxy of http/socks5 on 0.0.0.0:7890, all my configurations above are based on this.

Does the proxy persist after restart?

[d0j1a1701]

@MustardChef Yes. The proxy client Clash Meta I use on Windows exposes a mixed type proxy of http/socks5 on 0.0.0.0:7890, all my configurations above are based on this.

Does the proxy persist after restart?

No, that's why I have to use KernalSU to execute a script everytime startup, in order to automatically set the proxy.

[d0j1a1701]

In addition, you should enable "Local Network Access" in the WSA advanced settings and set/add a switch named "vSwitch (WSL)" in the Hyper-V Manager and set it to the network card you are using, so that you can access the proxy on the host using 127.0.0.1.

[rahaaatul]

In addition, you should enable "Local Network Access" in the WSA advanced settings and set/add a switch named "vSwitch (WSL)" in the Hyper-V Manager and set it to the network card you are using, so that you can access the proxy on the host using 127.0.0.1.

How do I add a switch in Hyper-V Manager?

I don't see FakeWifi or VirtWifi in WSA.