-
Notifications
You must be signed in to change notification settings - Fork 797
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
"ip link add type bridge" creates interface with no name #2497
Comments
@cascent - Thanks for the post and the repro steps. I have marked it as a bug. To help us prioritize, is this breaking a scenario for you currently? |
@sunilmut should any user just be able to create a bridge? I would have thought that the Windows kernel checks for an administrator token. |
@sunilmut no, I have no current use case - I noticed net.bridge. sysctls and wanted to see if it was possible to create a bridge. @fpqc - you do need sufficient privilege (and can't even enter a new network namespace without being elevated) Not elevated
Elevated
|
@fpqc - Creating a bridge requires admin. |
That's super cool then! But it still leaves us in the weird situation that there is no way right now to elevate to an admin from within a running LX session, and that in such an elevated scenario, since it applies to the entire LX session, you can cause all kinds of mischief without even having LX root by messing around in the mounted drvfs volume. |
Microsoft Windows [Version 10.0.16288.1]
If you create a bridge device in WSL without specifying a name, the kernel creates a bridge device without giving it any name. This is confusing and may break some tools.
Linux assigns bridges devices a default name of bridgeX, where X is the lowest unused number.
Example
WSL output
Linux output
The text was updated successfully, but these errors were encountered: