Interfaces added with phyadd are name differently than specified name

[wraith-wireless]

See https://wraithwireless.wordpress.com/2016/07/24/linux-kernel-bug/ and in README.md. airmon-ng states something about udev renaming devices so I'm looking further into it.

[mchwalisz]

Wouldn't it be better to handle both ways in PyRIC internally, not that the user needs to know and cope with both ways?

[wraith-wireless]

Yes, phyadd can most likely be removed the only difference betw/ it and devadd is the internal identifier that is being passed to the kernel.

[wraith-wireless]

So it seems that devadd has the same issue. After further fooling around the problem seem related to a very specific use case. If the card is integrated, then everything will work. If the card is usb and you attempt to add a device with the original name in mode managed then you will see the above effect. What is really odd is that netlink will report the new card with the name you gave it.