simos
April 10, 2020, 5:46pm
5
That’s a different type of managed . iw is not part of the NetworkManager suite, therefore that managed does not mean managed by NetworkManager .
I see you are using the RTL8812AU . Isn’t that the one that does not work out of the box and you need to install DKMS drivers?
Luckily, I happen to have one of those. I went through the steps and installed a DKMS driver, and managed to replicated the issue that you are facing.
According to the following ,
Does setting parent= and name= to the target of /sys/class/net/wlp1s0/phy80211 somehow work better? In my case here, that’d be phy4 .
If so, that’s because of the split between the hardware wireless card and the logical interface created on top of it. You can’t move just one logical interface but instead need to move the entire card.
You get a better error message when you stop the container, add the nic (it gets added successfully since there is no check), and when you start the container you get:
lxc mykali 20200410173713.876 ERROR network - network.c:lxc_network_move_created_netdev_priv:3126 - Operation not permitted - Failed to move network device "wlx0xxxxxxxxxx" with ifindex 12 to network namespace 104055
There’s a bug report for this, apparently it has been a regression that was supposed to be fixed.
opened 08:40PM - 25 Jul 19 UTC
closed 01:36PM - 26 Jul 19 UTC
# Required information
* Distribution: Ubuntu
* Distribution version: 18.0… 4
* Kernel version: 4.18.0-25-generic
* LXD version: 3.15
* Storage backend in use: btrfs
# Issue description
After lxd snap auto-refresh, the problem occurred.
```
lxc firewall 20190725200021.783 ERROR start - start.c:proc_pidfd_open:1644 - Function not implemented - Failed to send signal through pidfd
lxc firewall 20190725200021.900 ERROR network - network.c:lxc_network_move_created_netdev_priv:3292 - Operation not permitted - Failed to move network device "wlp3s0" with ifindex 3 to network namespace 25846
lxc firewall 20190725200021.900 ERROR start - start.c:lxc_spawn:1846 - Failed to create the network
lxc firewall 20190725200021.900 WARN network - network.c:lxc_delete_network_priv:3374 - Failed to rename interface with index 2 from "enp2s0" to its initial name "enp2s0"
lxc firewall 20190725200021.960 ERROR lxccontainer - lxccontainer.c:wait_on_daemonized_start:873 - Received container state "ABORTING" instead of "RUNNING"
lxc firewall 20190725200021.961 ERROR start - start.c:__lxc_start:2036 - Failed to spawn container "firewall"
lxc 20190725200022.408 WARN commands - commands.c:lxc_cmd_rsp_recv:135 - Connection reset by peer - Failed to receive response for command "get_state"
```
The only solution was to revert.
```
# snap changes
ID Status Spawn Ready Summary
18 Done today at 14:45 -03 today at 14:45 -03 Auto-refresh snap "lxd"
19 Done today at 17:15 -03 today at 17:15 -03 Revert "lxd" snap
#
Here is the fix, support for nl80211 adapters,
lxc:master ← brauner:2019-07-25/bugfixes
opened 07:35AM - 26 Jul 19 UTC
Closes #3105.
Signed-off-by: Christian Brauner <christian.brauner@ubuntu.com>
This post says that they got a workaround to specify the physical interface (in that case, phy2) simply by installing the iw utility. They use Debian, most likely not the snap.
@stgraber , should there be a bug report for this?