-
Notifications
You must be signed in to change notification settings - Fork 822
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
networkingMode: mirrored not working but virtioproxy does. #10717
Comments
@ssantosv you need Windows 11 for |
Yeps, I guessed that it was for Windows 11 only (although it is mentioned in logs, as an option in Windows 10). But what is really interesting is "virtioproxy". Seems to remain undocumented yet and working in Windows 10. Any information about it? |
Is there any documentation on VirtuoProxy? I'm getting error message after ugprading to Windows 11 22H2:
|
what is virtioproxy mode? |
Windows Version
10.0.19045.3570
WSL Version
2.0.7.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.133.1-1
Distro Version
Ubuntu 22.04
Other Software
No response
Repro Steps
.wslconfig
networkingMode=virtioproxy
or
networkingMode=mirrored
Expected Behavior
For me, a mirrored network. It des not work.
EventViewer:
"No se admite el modo de red reflejada, revirtiendo a las redes NAT"
Actual Behavior
I think I found a not documented mode that works:
networkingMode=virtioproxy
It shows a new lookback0 interface with a 169 network and eth0 gets the same IP as the host network. Example (redacted)
sergio@desktop:~$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether [redacted] brd ff:ff:ff:ff:ff:ff
altname [redacted]
altname [redacted]
inet 192.168.1.50/24 brd 192.168.1.255 scope global eth0 [THIS IP ADDRES IS THE SAME AS IN WINDOWS]
valid_lft forever preferred_lft forever
inet6 [redacted]/64 scope link
valid_lft forever preferred_lft forever
3: loopback0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether [redacted] brd ff:ff:ff:ff:ff:ff
altname [redacted]
altname [redacted]
inet 169.254.73.153/30 brd 169.254.73.155 scope global loopback0
valid_lft forever preferred_lft forever
inet6 f[redacted]/64 scope link
valid_lft forever preferred_lft forever
In windows:
Adaptador de Ethernet vEthernet (WSL):
Sufijo DNS específico para la conexión. . :
Vínculo: dirección IPv6 local. . . : fe80::2322:8351:528f:1874%35
Dirección IPv4. . . . . . . . . . . . . . : 172.25.160.1
Máscara de subred . . . . . . . . . . . . : 255.255.240.0
Puerta de enlace predeterminada . . . . . :
Adaptador de LAN inalámbrica Wi-Fi:
Sufijo DNS específico para la conexión. . :
Vínculo: dirección IPv6 local. . . : fe80::f610:a801:c872:99c4%23
Dirección IPv4. . . . . . . . . . . . . . : 192.168.1.50
Máscara de subred . . . . . . . . . . . . : 255.255.255.0
Puerta de enlace predeterminada . . . . . : 192.168.1.1
cat /etc/networks
symbolic names for networks, see networks(5) for more information
link-local 169.254.0.0
If no virtioproxy (no networkingMode swith, so NAT by default).
sergio@desktop:~$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1492 qdisc mq state UP group default qlen 1000
link/ether [redacted] brd ff:ff:ff:ff:ff:ff
inet 172.25.173.122/20 brd 172.25.175.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::215:5dff:fe08:66c7/64 scope link
valid_lft forever preferred_lft forever
So:
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: