You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
wsl network adapter would get new ip on reboot, thus ubuntu would also get a new ip
Actual Behavior
On each reboot, the wsl network adapter retains the same ip address of 172.30.224.1. this causes various connectivity issues within ubuntu. The largest issue is that i can no long connect to the smb on my ubuntu distro. One interesting thing I noticed was when checking the 'neighbors' via ipconfig for the wsl adapter it shows the ubuntu ip (172.30.233.201) as 'stale'
tprinsDW
changed the title
WSL ethernet adapter in (vEtherenet (WSL)) doesn't reset ip on reboot causing connectivity issue within ubuntu
WSL ethernet adapter (vEtherenet (WSL)) doesn't reset ip on reboot causing connectivity issue within ubuntu
Apr 14, 2023
Today I found that the "vEthernet (WSL)" adapter is also missing from the "Network Connections" adapters in the Control Panel. It used to show up there. I'm wondering if some configuration is now missing.
Windows Version
Microsoft Windows [Version 10.0.22621.1413]
WSL Version
1.2.0.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.90.1-microsoft-standard-WSL2
Distro Version
Ubuntu 20.04
Other Software
No response
Repro Steps
behavior is same on each system reboot
Expected Behavior
wsl network adapter would get new ip on reboot, thus ubuntu would also get a new ip
Actual Behavior
On each reboot, the wsl network adapter retains the same ip address of 172.30.224.1. this causes various connectivity issues within ubuntu. The largest issue is that i can no long connect to the smb on my ubuntu distro. One interesting thing I noticed was when checking the 'neighbors' via ipconfig for the wsl adapter it shows the ubuntu ip (172.30.233.201) as 'stale'
Diagnostic Logs
Windows:
PS C:\Users\taylorprins> ipconfig /all
...
Ethernet adapter vEthernet (WSL):
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #2
Physical Address. . . . . . . . . : 00-15-5D-A3-B3-4A
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::6354:e2a1:ed6f:fbf8%58(Preferred)
IPv4 Address. . . . . . . . . . . : 172.30.224.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.240.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 973083997
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-2B-B4-AF-EE-74-78-27-B2-8E-C6
NetBIOS over Tcpip. . . . . . . . : Enabled
PS C:\Users\taylorprins> netsh interface ipv4 show neighbors
...
Interface 58: vEthernet (WSL)
Internet Address Physical Address Type
172.30.224.1 00-00-00-00-00-00 Unreachable
172.30.233.201 00-15-5d-6e-d2-96 Stale
172.30.239.255 ff-ff-ff-ff-ff-ff Permanent
224.0.0.22 01-00-5e-00-00-16 Permanent
224.0.0.251 01-00-5e-00-00-fb Permanent
239.255.255.250 01-00-5e-7f-ff-fa Permanent
ubuntu:
taylorprins@UbuntuWSL:~/wsl_build$ ip a
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 mq state UP group default qlen 1000
link/ether 00:15:5d:6e:d2:96 brd ff:ff:ff:ff:ff:ff
inet 172.30.233.201/20 brd 172.30.239.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::215:5dff:fe6e:d296/64 scope link
valid_lft forever preferred_lft forever
The text was updated successfully, but these errors were encountered: