Skip to content
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

[2.4.4] Two WSL distros getting the exact same network config #12334

Closed
1 of 2 tasks
chemwolf6922 opened this issue Dec 3, 2024 · 2 comments
Closed
1 of 2 tasks

[2.4.4] Two WSL distros getting the exact same network config #12334

chemwolf6922 opened this issue Dec 3, 2024 · 2 comments

Comments

@chemwolf6922
Copy link

chemwolf6922 commented Dec 3, 2024

Windows Version

Microsoft Windows [Version 10.0.26100.2314]

WSL Version

2.4.4.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.15.167.4-microsoft-standard-WSL2

Distro Version

Ubuntu 24.04

Other Software

No response

Repro Steps

The Ubuntu 24.04 distro and a distro I build are getting the exact same network configurations. They have the same MAC address. And a "docker0" network which should not appear on the ubuntu distro since I never installed docker on that distro appeared.
Ubuntu:

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 noprefixroute
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1280 qdisc mq state UP group default qlen 1000
    link/ether 00:15:5d:a7:47:e7 brd ff:ff:ff:ff:ff:ff
    inet 172.27.141.183/20 brd 172.27.143.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::215:5dff:fea7:47e7/64 scope link
       valid_lft forever preferred_lft forever
3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:03:3b:17:e8 brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever

My distro:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue 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 noprefixroute
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1280 qdisc mq qlen 1000
    link/ether 00:15:5d:a7:47:e7 brd ff:ff:ff:ff:ff:ff
    inet 172.27.141.183/20 brd 172.27.143.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::215:5dff:fea7:47e7/64 scope link
       valid_lft forever preferred_lft forever
3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
    link/ether 02:42:03:3b:17:e8 brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever

Both distros' networking are not working at this moment.

Expected Behavior

The network should be isolated between the two distros and work properly for both. (Or at least the Ubuntu one if there is something wrong with my distro.)

Actual Behavior

The distros' networks are somehow tangled together.

Diagnostic Logs

WslLogs-2024-12-03_15-37-21.zip

Copy link

github-actions bot commented Dec 3, 2024

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Open similar issues:

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

Diagnostic information
Detected appx version: 2.4.4.0

@chemwolf6922
Copy link
Author

I just found out that WSL share a network namespace across all "distros".
Still, no idea why the network do not work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant