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.

Sign up for GitHub

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

Jump to bottom

feature request: supporting ip namespace #518

Closed
webarchymeta opened this issue Dec 15, 2019 · 1 comment · Fixed by #642
Closed

feature request: supporting ip namespace #518

webarchymeta opened this issue Dec 15, 2019 · 1 comment · Fixed by #642

Comments

@webarchymeta
Copy link

The current driver does not support ip namespace. It can be found following the steps, assuming that the wireless device is phy0:

sudo ip netns add test
sudo iw phy phy0 set netns name test

then one gets

command failed: Operation not supported (-95)

Some of other kind of wifi devices allow themselves to be moved into separated ip namespaces, however. I am not sure if this is a inherent problem of the hardware or that of the driver ...

This feature can be useful in virtualized environments of nowadays application
@kimocoder
Copy link
Collaborator

I'll take a look at this issue tomorrow

TheDJVG added a commit to TheDJVG/rtl8812au that referenced this issue May 9, 2020
@TheDJVG
Bugfix: Phy cannot be moved into another namespace
f70cb8c 
When CONFIG_NET_NS is enabled one would assume the device can be
moved into another namespace. Currently it will fail with:

command failed: Operation not supported (-95)

There's a check if the kernel is between 2.6.38 and 3.0.0
before it adds the netns flag to wiphy->flags.

With this commit it will always add the netns flag when
CONFIG_NET_NS is enabled.

Signed-off-by: Daan van Gorkum <daan@vusam.com>
Fixes: aircrack-ng#518
TheDJVG added a commit to TheDJVG/rtl8812au that referenced this issue May 9, 2020
@TheDJVG
Bugfix: Phy cannot be moved into another namespace
761f1d9 
When CONFIG_NET_NS is enabled one would assume the device can be
moved into another namespace. Currently it will fail with:

command failed: Operation not supported (-95)

There's a check if the kernel is between 2.6.38 and 3.0.0
before it adds the netns flag to wiphy->flags.

With this commit it will always add the netns flag when
CONFIG_NET_NS is enabled.

Signed-off-by: Daan van Gorkum <djvg@djvg.net>
Fixes: aircrack-ng#518
@TheDJVG TheDJVG mentioned this issue May 9, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Bugfix: Phy cannot be moved into another namespace TheDJVG/rtl8812au
2 participants
@webarchymeta @kimocoder