(hostapd) Wireless device busy on Proxmox Host

B

belette

New Member
Oct 20, 2014
14
0
1
(PVE from ISO 3.3 / Kernel 3.10.0-4-pve / OVS 2.3.0-1 / Intel Wireless 7260)

Hi,

On my Proxmox server at home I have a Wireless adapter I would like to use with Hostapd.
On a similar hardware without Proxmox I am able to use the wireless adapter as an AP but not with Proxmox.

It is like something in Proxmox kernel is locking my resource.
I tried to install the firmware-iwlwifi but it is in conflit with pve-firwmare

When I launch hostapd or even if I tried to change the channel with iwconfig I get

Code: 
nl80211: Failed to set channel (freq=2437): -16 (Device or resource busy)
Could not set channel for kernel driver

I would love to get some ideas from you guys!

belette
 
Hello belette

belette said:
(PVE from ISO 3.3 / Kernel 3.10.0-4-pve / OVS 2.3.0-1 / Intel Wireless 7260)

When I launch hostapd or even if I tried to change the channel with iwconfig I get

Code: 
nl80211: Failed to set channel (freq=2437): -16 (Device or resource busy)
Could not set channel for kernel driver
Click to expand...

The device itself works? I.e. brings

Code: 
iwlist scan

the proper result?

Which kernel module does it use? You can figure it out by

Code: 
modprobe -c | grep <device-id>


Btw.: It is of course up to you how to use the wireless adapter in Proxmox, but note that bridging it is not possible.

Kind regards

Mr.Holmes
 
Mr.Holmes said:
Hello belette
Click to expand...

Hi Mr. Holmes!
Thanks for your reply.

The device itself works? I.e. brings

iwlist scan

the proper result?
Click to expand...

Yes it is! This is the reason why I keep not understanding why it only doesn't work when it tries to change the channel...
iwlist scan is working well and give me all the wireless network around me.

Which kernel module does it use? You can figure it out by

modprobe -c | grep <device-id>
Click to expand...


I have a doubt on this one..
Code: 
lspci -nn
03:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev 73)

but
Code: 
modprobe -c | grep 8086:08b1
is not giving me anything!


Btw.: It is of course up to you how to use the wireless adapter in Proxmox, but note that bridging it is not possible.

Kind regards

Mr.Holmes
Click to expand...
Do you know if it is the same thing when using OVS?
I think it was possible to use a wireless interface inside OVS as an interface. (it is my goal)
 
Hello belette

belette said:
Yes it is! This is the reason why I keep not understanding why it only doesn't work when it tries to change the channel...
iwlist scan is working well and give me all the wireless network around me.
Click to expand...

So you can use wireless but not hostapd. If fact there is a contradiction with PVE kernel. Seems to be simply not supported.

belette said:
I have a doubt on this one..
Code: 
lspci -nn
03:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev 73)

but
Code: 
modprobe -c | grep 8086:08b1
is not giving me anything!
Click to expand...

Both parts of ID are not agglutinated, you should write
Code: 
modprobe -c | grep 8086 | grep 08b1



belette said:
Do you know if it is the same thing when using OVS?
I think it was possible to use a wireless interface inside OVS as an interface. (it is my goal)
Click to expand...

It is not refused by OVS and at the first moment seemingly working - but I had always bad experiences with bridged wireless (doubling messages, mixing up MAC addresses etc.). I don´t have the same adapter, I cannot say if is working in your case. But I never use wireless again for any kind of bridges and would not recommend it, it may consume a lot of time to figure out what happens in case of problems.

Kind regards

Mr.Holmes
 
So you can use wireless but not hostapd. If fact there is a contradiction with PVE kernel. Seems to be simply not supported.
Click to expand...

Thanks for your inputs!
But just to understand better, you think that PVE Kernel is not allowing Hostapd to change the channel?
I still don't understand why PVE Kernel is dealing with the wireless card - driver?
I only realize that when I want to update iwlwifi it needs to remove the PVE Firmware...

Both parts of ID are not agglutinated, you should write
Code: 
modprobe -c | grep 8086 | grep 08b1
Click to expand...

It doesn't give me anything either.
If I remove the last pipe then I got some info on my device.

Code: 
modprobe -c | grep 8086

alias pci:v00008086d00004222sv*sd00001005bc*sc*i* iwl3945
alias pci:v00008086d00004222sv*sd00001034bc*sc*i* iwl3945
alias pci:v00008086d00004222sv*sd00001044bc*sc*i* iwl3945
alias pci:v00008086d00004227sv*sd*bc*sc*i* iwl3945
alias pci:v00008086d00004227sv*sd00001014bc*sc*i* iwl3945
alias pci:v00008086d00004229sv*sd*bc*sc*i* iwl4965
alias pci:v00008086d0000422Bsv*sd00001101bc*sc*i* iwlwifi
alias pci:v00008086d0000422Bsv*sd00001108bc*sc*i* iwlwifi
alias pci:v00008086d0000422Bsv*sd00001121bc*sc*i* iwlwifi
alias pci:v00008086d0000422Bsv*sd00001128bc*sc*i* iwlwifi
alias pci:v00008086d0000422Csv*sd00001301bc*sc*i* iwlwifi
alias pci:v00008086d0000422Csv*sd00001306bc*sc*i* iwlwifi
alias pci:v00008086d0000422Csv*sd00001307bc*sc*i* iwlwifi
alias pci:v00008086d0000422Csv*sd00001321bc*sc*i* iwlwifi
alias pci:v00008086d0000422Csv*sd00001326bc*sc*i* iwlwifi
alias pci:v00008086d00004230sv*sd*bc*sc*i* iwl4965
alias pci:v00008086d00004232sv*sd00001201bc*sc*i* iwlwifi
alias pci:v00008086d00004232sv*sd00001204bc*sc*i* iwlwifi
alias pci:v00008086d00004232sv*sd00001205bc*sc*i* iwlwifi
alias pci:v00008086d00004232sv*sd00001206bc*sc*i* iwlwifi
alias pci:v00008086d00004232sv*sd00001221bc*sc*i* iwlwifi
alias pci:v00008086d00004232sv*sd00001224bc*sc*i* iwlwifi
alias pci:v00008086d00004232sv*sd00001225bc*sc*i* iwlwifi
alias pci:v00008086d00004232sv*sd00001226bc*sc*i* iwlwifi
alias pci:v00008086d00004232sv*sd00001301bc*sc*i* iwlwifi
alias pci:v00008086d00004232sv*sd00001304bc*sc*i* iwlwifi
alias pci:v00008086d00004232sv*sd00001305bc*sc*i* iwlwifi
alias pci:v00008086d00004232sv*sd00001306bc*sc*i* iwlwifi
alias pci:v00008086d00004232sv*sd00001321bc*sc*i* iwlwifi
alias pci:v00008086d00004232sv*sd00001324bc*sc*i* iwlwifi
alias pci:v00008086d00004232sv*sd00001325bc*sc*i* iwlwifi
alias pci:v00008086d00004232sv*sd00001326bc*sc*i* iwlwifi
alias pci:v00008086d00004235sv*sd00001001bc*sc*i* iwlwifi
alias pci:v00008086d00004235sv*sd00001004bc*sc*i* iwlwifi
alias pci:v00008086d00004235sv*sd00001021bc*sc*i* iwlwifi
alias pci:v00008086d00004235sv*sd00001024bc*sc*i* iwlwifi
alias pci:v00008086d00004235sv*sd00001101bc*sc*i* iwlwifi
alias pci:v00008086d00004235sv*sd00001104bc*sc*i* iwlwifi
alias pci:v00008086d00004235sv*sd00001121bc*sc*i* iwlwifi
alias pci:v00008086d00004235sv*sd00001124bc*sc*i* iwlwifi
alias pci:v00008086d00004236sv*sd00001011bc*sc*i* iwlwifi
alias pci:v00008086d00004236sv*sd00001014bc*sc*i* iwlwifi
alias pci:v00008086d00004236sv*sd00001111bc*sc*i* iwlwifi
alias pci:v00008086d00004236sv*sd00001114bc*sc*i* iwlwifi
alias pci:v00008086d00004237sv*sd00001211bc*sc*i* iwlwifi
alias pci:v00008086d00004237sv*sd00001214bc*sc*i* iwlwifi
alias pci:v00008086d00004237sv*sd00001215bc*sc*i* iwlwifi
alias pci:v00008086d00004237sv*sd00001216bc*sc*i* iwlwifi
alias pci:v00008086d00004237sv*sd00001311bc*sc*i* iwlwifi
alias pci:v00008086d00004237sv*sd00001314bc*sc*i* iwlwifi
alias pci:v00008086d00004237sv*sd00001315bc*sc*i* iwlwifi
alias pci:v00008086d00004237sv*sd00001316bc*sc*i* iwlwifi
alias pci:v00008086d00004238sv*sd00001111bc*sc*i* iwlwifi
alias pci:v00008086d00004238sv*sd00001118bc*sc*i* iwlwifi
alias pci:v00008086d00004239sv*sd00001311bc*sc*i* iwlwifi
alias pci:v00008086d00004239sv*sd00001316bc*sc*i* iwlwifi
alias pci:v00008086d0000423Asv*sd00001001bc*sc*i* iwlwifi
alias pci:v00008086d0000423Asv*sd00001021bc*sc*i* iwlwifi
alias pci:v00008086d0000423Bsv*sd00001011bc*sc*i* iwlwifi
alias pci:v00008086d0000423Csv*sd00001201bc*sc*i* iwlwifi
alias pci:v00008086d0000423Csv*sd00001206bc*sc*i* iwlwifi
alias pci:v00008086d0000423Csv*sd00001221bc*sc*i* iwlwifi
alias pci:v00008086d0000423Csv*sd00001301bc*sc*i* iwlwifi
alias pci:v00008086d0000423Csv*sd00001306bc*sc*i* iwlwifi
alias pci:v00008086d0000423Csv*sd00001321bc*sc*i* iwlwifi
alias pci:v00008086d0000423Csv*sd00001326bc*sc*i* iwlwifi
alias pci:v00008086d0000423Dsv*sd00001211bc*sc*i* iwlwifi
alias pci:v00008086d0000423Dsv*sd00001216bc*sc*i* iwlwifi
alias pci:v00008086d0000423Dsv*sd00001311bc*sc*i* iwlwifi
alias pci:v00008086d0000423Dsv*sd00001316bc*sc*i* iwlwifi
 
Hello belette,

belette said:
But just to understand better, you think that PVE Kernel is not allowing Hostapd to change the channel?
Click to expand...

Yes, that´s my impression


belette said:
I still don't understand why PVE Kernel is dealing with the wireless card - driver?
I only realize that when I want to update iwlwifi it needs to remove the PVE Firmware...

[\QUOTE]

What ever the reason is - note the "PVE Kernel" does not mean necessarily a PVE function. The kernel is based on the red hat one for OpenVZ and probably already that kernel causes the mismatch.

I am not a programmer an therefore a cannot treat details why etc. But it´s obvious that it is complex software and interactions sometimes causes problems you never expect. In that particular case probably nobody tested it before because wireless on servers is rather the exception.

But, at least wireless itself works I understood.

Kind regards

Mr.Holmes
Click to expand...
 
Last edited:
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back