-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
nspawn: support passing wireless interface to container #30956
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
Conversation
|
looks superficially good to me. |
1da5f8a to
2fc6667
Compare
|
This becomes much bigger than I initially expected. But, now renaming is also supported, and test cases are added. PTAL. |
2fc6667 to
373018b
Compare
|
@Edu4rdSHL Please test again. |
|
(BTW, this is nice article: https://www.suse.com/c/creating-virtual-wlan-interfaces/) |
|
I have tested it and everything works as expected. I did a few tests:
|
373018b to
aaf4211
Compare
c50a459 to
d7bb49b
Compare
Also reorder opening namespace fd to make it match with the order of the arguments.
Also use -EBADF when unspecified.
On failure, the caller logs the error in LOG_ERR.
Similar to FORK_NEW_MOUNTNS or FORK_NEW_USERNS.
Similar to userns_acquire(), but for network namespace.
|
lgtm, just some superficial comments about function names. |
No functional change, just refactoring and preparation for later commits.
This also changes to use sd_device to get some attributes. So, on moving interfaces back to the parent, we need to populate sysfs associated to the client netns. That may look redundant and complicated, but it makes later change easier, and hopefully faster.
If the requested new name for a network interface is already assigned as a alternative name, then it is not necessary to and cannot rename the interface.
- test interface renaming that conflicts with the current alternative network interface name, - test passing wlan interfaces.
d7bb49b to
e8736fb
Compare
|
@poettering Thank you for the review. The functions are renamed. Upgrading the green label. |
Mention systemd/systemd#30956 which will fix this problem and we will not need workarounds.
Closes #7873.