Wifi hardware disabled

[JnJ]

Hi,

I just installed Debian 8.6 on a HP Elitebook 8460p.
Everything works fine except I cannot use the wifi : the network menu says it is hardware disabled.
However I'm sure the wireless hardware switch is on.
I'm now working with a wired connection without problem.
Anyone knows how to fix this ?

I can add some other information that may be useful :

During the installation process, the installer detected that a microcode file was missing : iwlwifi-6000-4.ucode.
I could continue the installation anyway, and once installed, I followed these steps https://wiki.debian.org/iwlwifi to get the microcode. It seemed to work.

I tried the command

Code: Select all

sudo rfkill unblock all

without success.

I had the same problem under Ubuntu 16.04.

My wireless card is : Intel Corporation Centrino Ultimate-N 6300

Thank you

[JnJ]

Thank you for your answer

First what do you call a wireless interface ? Is it the physical wireless card, or the microcode ?

Here is my interfaces file :

Code: Select all

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

And :

Code: Select all

simon@sj:~$ sudo ip link show
[sudo] password for simon: 
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
    link/ether e4:11:5b:3d:72:28 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether 00:24:d7:f6:38:c8 brd ff:ff:ff:ff:ff:ff
6: wwan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether e2:ca:f0:dc:f7:d8 brd ff:ff:ff:ff:ff:ff

I hope this will help !

[JnJ]

It seemed too easy ...

Code: Select all

simon@sj:~$ sudo ip link set wlan0 up
[sudo] password for simon: 
RTNETLINK answers: Operation not possible due to RF-kill

[JnJ]

I found this thread : https://bbs.archlinux.org/viewtopic.php?id=173808
The same problem is discussed but with a different wireless card and under archlinux.
However bjornoslav brings an answer that is blacklisting hp_wmi.

Code: Select all

# echo "blacklist hp_wmi" > /etc/modprobe.d/hp.conf

Then

Code: Select all

# rfkill unblock all

Do you think I can try this with my configuration ? I prefer to ask since I don't really understand what this stuff do

[stevepusser]

This page: http://www.linlap.com/hp_elitebook_8460p

mentioned some custom setting for the wifi on/off hotkey:

Wireless button

Wireless button is controled by HW, so no driver is needed. For handling events generated by this button (e.g when press show info on screen), is needed proper maping to KEY_WLAN (238) in kernel (default is for unknow key):

setkeycodes e078 238

However, newer kernels often have fixes for these kind of quirks for laptops, so maybe an updated kernel from backports will help. One clue would be to see if the hotkey works out of the box with the newer Ubuntu kernel.

[JnJ]

wizard10000 : the rfkill command does nothing.

Code: Select all

simon@sj:~$ sudo rfkill list
[sudo] password for simon: 
0: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: yes
1: hp-wifi: Wireless LAN
	Soft blocked: no
	Hard blocked: no
2: hp-wwan: Wireless WAN
	Soft blocked: no
	Hard blocked: no
simon@sj:~$ sudo rfkill unblock all
simon@sj:~$ sudo rfkill list
0: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: yes
1: hp-wifi: Wireless LAN
	Soft blocked: no
	Hard blocked: no
2: hp-wwan: Wireless WAN
	Soft blocked: no
	Hard blocked: no

stevepusser : I booted a live Ubuntu 16.10. It also says that the wifi is hardware disabled, and the wireless switch does not respond.
Should I try something else in this direction ?

[JnJ]

Ok new information now :

I disconnected the wired connection, then I could connect a wifi network !
However from the moment I plug in the wire, the wifi status switches to hardware disabled.
My goal is to use my laptop as wifi hotspot, so that's not the solution yet.

Does this bring other ideas ?

[JnJ]

I still haven't worked this out. Any help would be welcome,
Thank you

[GarryRicketson]

I am not at all a expert on this, in fact I know very little,...but these are some
experiences, might help give you some clues.
Where I used to work, the internet connection was by "landline" and a modem and router, the "router" provided by the ISP provider, any way the cable connection was all ways very good, and easy,..the "wifi" was good and strong signal, but there were some "hoops" to jump through.
The office, had all MS Windows machines,...I was the only person using Linux, on my laptop.
If I used a cable I had no problem, using the modem and router.
How ever nobody could get the wifi "hotspot",..it did not matter if it was me with my linux laptop, or a Windows powered laptop, mobile phone, what ever.
After accessing the modem, or router, (on this I get confused about the correct term), but any way I got looking at configuration settings, and found a option,
"wifi hot spot = off",...changing it to "wifi hot spot = on" , and then we had
a "wifi hot spot", every body could use, if they had the password.
Including me, on my Linux laptop.
Ok, now here at home, my only internet access is via a "broad band" device of
some sort,... I have a USB broad band device I used to use, but no longer use it.
It never did have any option for a "wifi hot spot", ...... nor the laptop.
I started using my "cell phone" it is a "Blu-dash", but I don't think that matters
much, the point is:
I still use the same "chip" I had in the USB device, it is actually the same as what the mobile cell phone uses any way,....
Any way, on the Blu-dash phone, it has options, USB tethering, is what I need to have internet access.
Additionally, if I want to use "wifi", there is a option to use it, but there is no Wifi here,..
The other option available is "enable Wifi hot spot", similar to the modem, where I worked,... IF I do not have the "enable wifi hot spot" turned on,
and try getting wifi access with a laptop, it says "hardware disabled",..
Nothing can be done to change that, within the laptop, nor the OS, (Debian),but it would not matter,..the thing of it is , the phone must have the "wifi hot spot" turned on, then other laptops or even mobile devices, like my granddaughters
tablet, all can use the wifi,...

However from the moment I plug in the wire, the wifi status switches to hardware disabled.

This is confusing to me, What "wire" ? and how is it plugged in USB, phone jack ,
etc ?,....

Any way, it is hard to explain, hence a overly long post,...in a nut shell , it sounds
to me like you are looking in the wrong places to turn on the wifi hot spot,....

However I'm sure the wireless hardware switch is on.

For me, the Bludash, phone is my "wireless hardware", if Wifi is on, I have
wifi,but only for the phone, and the laptop it is connected to, if there is a signal, but unless I also have the "enable wifi hot spot" on,
there is no Wifi hot spot, again, this can not be changed form the computer,
it must be changed in the "hardware'' in this case, (the Bludash phone).
Any way, sorry if this does not help or confuses the issue,. guess that is about all

[JnJ]

Thanks for your answer. I am not exactly in your case but maybe you can help me.
First let me clarify my situation.
At home, I have an internet connection via an ethernet wire, directly plugged into a socket in the wall. I don't have any clue about how it works behind the wall (I live in a student housing).
What I want to do is to share this connection via wifi to connect my smartphone to the internet. The idea is to setup a wifi hostspot on the laptop.
When the ethernet wire is not plugged into my laptop, the wifi seems to work normally (I can connect to wifi networks).
But if the ethernet wire is plugged in, I cannot do anything with the wifi, every button is gray or unclickable. And instead of the "turn on" button I have the message "hardware disabled". No way to setup a wifi hotspot.

it sounds to me like you are looking in the wrong places to turn on the wifi hot spot

probably...
Do you know if there is a configuration file about wifi hotspot where I could find something like "wifi hot spot = on/off", like in your router ?

[GarryRicketson]

Is this laptop, only Debian, or do you also have Windows on it ?

The reason I ask, I found this :
HP Notebook PCs - Hotspot Still Available Despite Being Disabled
It says it includes HP EliteBook 8460p Notebook PC , I think that is the same as yours.
It is sort of the reverse, but it is enough to tell me the laptop should be capable
of broadcasting a wifi signal and being a "hot spot".
The problem is the instructions, are based on if Windows is being used,...
If your "wifi hotspot", or "broad casting" was disabled , via windows at some time,
then it probably still is disabled.
A long time ago there was a thread on this forum, and the solution was to
enable something, but via windows,...it was odd, because no body thought
A windows setting could/or would effect the Linux partition, but it can.
Another thing, a long time ago when I was in the U.S. I needed to buy a USB broad band device, that would work in the U.S., mine from Mexico, would not
work,.. but also I had the same problem with the one in /from Mexico, when I bought it,...the problem, the device included a tiny piece of software, GUI, that
is used to activate the account and device, and this piece of software is only for Windows, it can not and will not run on a linux system.
It is only needed once, to activate the device, after that it is not needed or used.
So I asked the place (Wal Mart) where I bought the device, to activate it, for me on their Windows computer, but they refused to, (pinche walmart),...In Mexico
the store I bought a similar one, activated it for me,...so I knew once it was activated, it would work fine on Linux,...but I had to use windows to "activate", or enable the device.
So any way, sorry for getting "long story", but it goes to show,...my thoughts
are if you do still have windows, as a "dual boot " set up,...then that would be
a place to start, see if you can get the "wifi broadcasting" working from you windows partition first,...
There is some thing that does not make sense to me,..

When the ethernet wire is not plugged into my laptop, the wifi seems to work normally (I can connect to wifi networks).

Let's not worry about the cable part,..but "the wifi seems to work normally (I can connect to wifi networks)"
So you can connect to a wifi network with the laptop ?
With the wifi turned on, I can connect to a wifi network with my phone,... but
it does NOT broad cast, it will not be a "hot spot" unless I turn that on.
And there is no need to turn it on, if there is a Wifi signal being broadcast
from some where,...like in the situation where I used to work,...they had a
wifi "hot spot",...
So your laptop is receiving a wifi signal,..
Then you say :

What I want to do is to share this connection via wifi to connect my smartphone to the internet.

If there is a wifi signal, that your laptop can connect to, the "smart phone" should
be able to connect to it ,.(the same signal) ....if it can not connect to the wifi signal your laptop is
receiving,...it will not be able to connect the the wifi signal produced , if and when you get the laptop "broadcasting", ...or working as a "hot spot",...it sounds
to me like the "smart phone" is not able to connect to a wifi signal, for some reason.

(quote0 Do you know if there is a configuration file about wifi hotspot where I could find something like "wifi hot spot = on/off", like in your router ?(/quote)

Based on the link to the HP site above,

DESCRIPTION

The Manageability registry key "AllowHotspot" within HP Connection Manager 4.2.x does not disable sharing if the Hotspot was configured prior to setting a value of False in the Windows Registry. As a result, the notebook continues to broadcast its Service Set Identifier (SSID).

It sounds like there is a "internal" switch of some sort,...
As far as the wifi signal you are receiving and using when you are able to
connect to the "wifi network" with your laptop,..that is coming from the
"school", or "home",...Did you need to "register" with them or anythnng
like that, in order to be able to use your laptop on their network, either cable
or wifi ? Then you might have to do the same with the phone,... to use that
network,... of course if you can get your laptop "broadcasting" then their work
be no need to register the phone as well,...

----directly plugged into a socket in the wall. I don't have any clue about how it works behind the wall (I live in a student housing).

Also they would have settings in their router, but you have no control
over that, ....However there is a "wifi signal" being produced, or "broadcasted "
I do not see any reason you should not be able to access it with the smart phone
as well, and use the same password , user name as you use for your laptop.
This is on of those problems that is really hard to say what is going on, with out
actually being there, and able to see exactly what the network situation is.
Another option might be to take the laptop to a "tech" shop, and see if they
know how to access the internal "switch", and check to verify if it is really on
or off,...
Also maybe http://h30434.www3.hp.com/
you could get some more details on how to enable it,..you need to do a little searching there,...

http://forums.debian.net/viewtopic.php? ... 23#p633194
Postby stevepusser » 2017-01-05 13:20
This page: http://www.linlap.com/hp_elitebook_8460p

mentioned some custom setting for the wifi on/off hotkey:

Did you even bother to look at the link Steve posted , carefully,

Wireless button

Wireless button is controled by HW, so no driver is needed. For handling events generated by this button (e.g when press show info on screen), is needed proper maping to KEY_WLAN (238) in kernel (default is for unknown key):

Code: Select all

setkeycodes e078 238

Did you try that, ?
With that and the one I posted:
http://h20564.www2.hp.com/hpsc/doc/publ ... -c03297766
You should be able to resolve this, if not, I think your best bet is to try to
find a tech shop, or repair shop, that has somebody familiar with these
HP laptops, and they can show you exactly which key
or "button". ...I don't know exactly where,...but for example on a older
Acer, I have there is a little "switch", on the front, under the edge,..it has
to be turned on to enable wifi broadcasting,...

[JnJ]

I only have debian installed on this laptop.
At home I have no wifi network to connect to, only this ethernet connection.
As for what stevepusser suggested, I couldn't find how to edit key mapping in the kernel.
I think this link HP Notebook PCs - Hotspot Still Available Despite Being Disabled would be useful if I had windows installed, and I don't know if there is an equivalent of this Manageability registry key "AllowHotspot" in debian.

Well, I actually moved on on this issue. I found an option in the BIOS "LAN/WLAN switch", it was on. Anyway I reseted the default configuration of the BIOS and rebooted.
Surprinsingly this solved the "wifi harware disabled problem". I checked back the "LAN/WLAN switch" state and it was reseted to off.
But now it seems that the issue has turned to a different one.
So now I can use the wifi even if the ethernet wire is plugged in. I can turn on wifi, see the list of wifi networks, and even turn on the wifi hotspot.
Connecting to a wifi network works (conected to a hotspot created with my phone) but the wifi hotspot does not work.
To be more precise : I can turn on the wifi hotspot and network manager tells me that the SSID is the name of my laptop, the encryption used is WEP and gives me a password, with no options to configure. The problem is my phone can't detect this network (but it detects the other networks). Even entering manually SSID, encryption type and password doesn't work.
One more thing : I cannot turn off the wifi hotspot. I can click the turn off button but it won't turn off. Even after switching on and off airplane mode, the hotspot is still on.

From this, I tried

Code: Select all

sudo dpkg-reconfigure network-manager
sudo dpkg-reconfigure network-manager-gnome

This didn't bring any change.
I thought maybe reinstalling network manager would solve this.
I downloaded the network-manager and network-manager-gnome packages and tried to remove the ones installed with

Code: Select all

sudo dpkg -r network-manager
sudo dpkg -r network-manager-gnome

but I couldn't due to dependency issues. GNOME depends on network-manager-gnome which depends on network-manager.

I found no other information about invisible and unturnoffable hotspots. Any ideas ?

Something just came to my mind, I don't know if it is somehow related. Everytime I boot, I get this messages on the screen before the one where I login to my user account.

Code: Select all

[   9.865197] kvm: disabled by bios
[   9.896839] kvm: disabled by bios
[   9.928461] kvm: disabled by bios
[   9.941160] kvm: disabled by bios

With numbers slightly different each time.

[Head_on_a_Stick]

The idea is to setup a wifi hostspot on the laptop.

Are you sure that your card supports an access point mode under GNU/Linux?

Also, those KVM messages relate to virtualisation and are not connected to your current problems.

[GarryRicketson]

It sounds like the OP is closer,

H_O_A_S>
Are you sure that your card supports an access point mode under GNU/Linux?

I have 2 HP s , but differnt models, one I know does not have the capability to broadcast, (produce a hot spot), the other I have never really looked, maybe later
to today I will get it out , and see,...
I think the OP should try to contact HP support, it may take some real digging, and
if nothing is found in their FAQs, etc,..a e-email, to their "tech" support,...it may take
a while to get a response,...
Agreed, on the KVM thing, it has nothing to do with it,...on both my HP's I get
those kind of messages all the time, everything works fine, and I ignore them.

by JnJ » To be more precise : I can turn on the wifi hotspot and network manager tells me that the SSID is the name of my laptop, the encryption used is WEP and gives me a password, with no options to configure. The problem is my phone can't detect this network (but it detects the other networks). Even entering manually SSID, encryption type and password doesn't work.
One more thing : I cannot turn off the wifi hotspot. I can click the turn off button but it won't turn off. Even after switching on and off airplane mode, the hotspot is still on.

Essentially it seems like you are in the same situation now, that the link I posted
talks about, but you can not access the registry,

From: http://h20564.www2.hp.com/hpsc/doc/publ ... -c03297766
RESOLUTION
To resolve this issue, disable Internet Connection Sharing as follows:
Click Start, type computer manage in the search field, then select Computer Management from the search results.
Select Services and Applications from the list.
Double-click Services.
Scroll down to Internet Connection Sharing (ICS) and double-click it.
Set Startup type to Disabled.
Click Apply.

I see they also say :

Operating Systems Affected: Not Applicable
Software Affected: Not Applicable

I can not find a direct e-mail, option...but if you register, and login you can submit a question about this,....
http://h30434.www3.hp.com/t5/Notebook-S ... p/Recovery
Some additional "browsing" might help you find a more appropriate area,... I don't know, or just submit a question, and maybe at least some one will direct you to
a more specific area,...

I would not keep changing things, just "guessing", or blindly at this point, you seem
pretty close, and have the wifi working, keep changing things and experimenting might set you back, and cause more problems,...
Maybe give it a few days, it does seem likely that there may be somebody else that
has the same model of HP, and uses Debian, and has all ready solved this, but it may
take some time before they happen to stop by on this forum,and see the thread.
Have you tried looking for some one, or some where in your area, that services HP computers, and also know something about linux,...? I know that can be difficult, and perhpas non existant,...most of these clowns that call their selves technitions, or repair shops, do not have a clue when it comes to a linux system,...but sometimes there are some that do.
I will look at my HP later today, and see if I can find anything,...
------ edit -------
I do not have windows on either of mine, and do not think you should need to have it,
but also, to install the malware, you would need to install it first, and it will remove, or wipe you Debian/ linux partition,...that is the way MS makes their mal-ware, so you do not want to even think about trying that, at this point,...at least I don't think it would be worth it, to install that MS malware, just to have a wifi hot spot, and I am sure this can be solved , with out using their mal ware.

[Thorny]

JnJ, you should be able to get the capabilities of the card with

Code: Select all

 #iw list

(note that the command, iw list, is run as root) and see if AP mode is supported.

[JnJ]

Head_on_a_Stick and Thorny : I think the card supports wifi broadcasting.
Here is the output of #iw list

Code: Select all

simon@sj:~$ sudo iw list
[sudo] password for simon: 
Wiphy phy0
	max # scan SSIDs: 20
	max scan IEs length: 95 bytes
	Retry short limit: 7
	Retry long limit: 4
	Coverage class: 0 (up to 0m)
	Device supports RSN-IBSS.
	Supported Ciphers:
		* WEP40 (00-0f-ac:1)
		* WEP104 (00-0f-ac:5)
		* TKIP (00-0f-ac:2)
		* CCMP (00-0f-ac:4)
	Available Antennas: TX 0 RX 0
	Supported interface modes:
		 * IBSS
		 * managed
		 * monitor
	Band 1:
		Capabilities: 0x1072
			HT20/HT40
			Static SM Power Save
			RX Greenfield
			RX HT20 SGI
			RX HT40 SGI
			No RX STBC
			Max AMSDU length: 3839 bytes
			DSSS/CCK HT40
		Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
		Minimum RX AMPDU time spacing: 4 usec (0x05)
		HT TX/RX MCS rate indexes supported: 0-23, 32
		Bitrates (non-HT):
			* 1.0 Mbps
			* 2.0 Mbps (short preamble supported)
			* 5.5 Mbps (short preamble supported)
			* 11.0 Mbps (short preamble supported)
			* 6.0 Mbps
			* 9.0 Mbps
			* 12.0 Mbps
			* 18.0 Mbps
			* 24.0 Mbps
			* 36.0 Mbps
			* 48.0 Mbps
			* 54.0 Mbps
		Frequencies:
			* 2412 MHz [1] (15.0 dBm)
			* 2417 MHz [2] (15.0 dBm)
			* 2422 MHz [3] (15.0 dBm)
			* 2427 MHz [4] (15.0 dBm)
			* 2432 MHz [5] (15.0 dBm)
			* 2437 MHz [6] (15.0 dBm)
			* 2442 MHz [7] (15.0 dBm)
			* 2447 MHz [8] (15.0 dBm)
			* 2452 MHz [9] (15.0 dBm)
			* 2457 MHz [10] (15.0 dBm)
			* 2462 MHz [11] (15.0 dBm)
			* 2467 MHz [12] (15.0 dBm) (no IR)
			* 2472 MHz [13] (15.0 dBm) (no IR)
	Band 2:
		Capabilities: 0x1072
			HT20/HT40
			Static SM Power Save
			RX Greenfield
			RX HT20 SGI
			RX HT40 SGI
			No RX STBC
			Max AMSDU length: 3839 bytes
			DSSS/CCK HT40
		Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
		Minimum RX AMPDU time spacing: 4 usec (0x05)
		HT TX/RX MCS rate indexes supported: 0-23, 32
		Bitrates (non-HT):
			* 6.0 Mbps
			* 9.0 Mbps
			* 12.0 Mbps
			* 18.0 Mbps
			* 24.0 Mbps
			* 36.0 Mbps
			* 48.0 Mbps
			* 54.0 Mbps
		Frequencies:
			* 5180 MHz [36] (15.0 dBm) (no IR)
			* 5200 MHz [40] (15.0 dBm) (no IR)
			* 5220 MHz [44] (15.0 dBm) (no IR)
			* 5240 MHz [48] (15.0 dBm) (no IR)
			* 5260 MHz [52] (15.0 dBm) (no IR, radar detection)
			  DFS state: usable (for 222 sec)
			  DFS CAC time: 0 ms
			* 5280 MHz [56] (15.0 dBm) (no IR, radar detection)
			  DFS state: usable (for 222 sec)
			  DFS CAC time: 0 ms
			* 5300 MHz [60] (15.0 dBm) (no IR, radar detection)
			  DFS state: usable (for 222 sec)
			  DFS CAC time: 0 ms
			* 5320 MHz [64] (15.0 dBm) (no IR, radar detection)
			  DFS state: usable (for 222 sec)
			  DFS CAC time: 0 ms
			* 5500 MHz [100] (15.0 dBm) (no IR, radar detection)
			  DFS state: usable (for 222 sec)
			  DFS CAC time: 0 ms
			* 5520 MHz [104] (15.0 dBm) (no IR, radar detection)
			  DFS state: usable (for 222 sec)
			  DFS CAC time: 0 ms
			* 5540 MHz [108] (15.0 dBm) (no IR, radar detection)
			  DFS state: usable (for 222 sec)
			  DFS CAC time: 0 ms
			* 5560 MHz [112] (15.0 dBm) (no IR, radar detection)
			  DFS state: usable (for 222 sec)
			  DFS CAC time: 0 ms
			* 5580 MHz [116] (15.0 dBm) (no IR, radar detection)
			  DFS state: usable (for 222 sec)
			  DFS CAC time: 0 ms
			* 5600 MHz [120] (15.0 dBm) (no IR, radar detection)
			  DFS state: usable (for 222 sec)
			  DFS CAC time: 0 ms
			* 5620 MHz [124] (15.0 dBm) (no IR, radar detection)
			  DFS state: usable (for 222 sec)
			  DFS CAC time: 0 ms
			* 5640 MHz [128] (15.0 dBm) (no IR, radar detection)
			  DFS state: usable (for 222 sec)
			  DFS CAC time: 0 ms
			* 5660 MHz [132] (15.0 dBm) (no IR, radar detection)
			  DFS state: usable (for 222 sec)
			  DFS CAC time: 0 ms
			* 5680 MHz [136] (15.0 dBm) (no IR, radar detection)
			  DFS state: usable (for 222 sec)
			  DFS CAC time: 0 ms
			* 5700 MHz [140] (15.0 dBm) (no IR, radar detection)
			  DFS state: usable (for 222 sec)
			  DFS CAC time: 0 ms
			* 5745 MHz [149] (15.0 dBm) (no IR)
			* 5765 MHz [153] (15.0 dBm) (no IR)
			* 5785 MHz [157] (15.0 dBm) (no IR)
			* 5805 MHz [161] (15.0 dBm) (no IR)
			* 5825 MHz [165] (15.0 dBm) (no IR)
	Supported commands:
		 * new_interface
		 * set_interface
		 * new_key
		 * start_ap
		 * new_station
		 * new_mpath
		 * set_mesh_config
		 * set_bss
		 * authenticate
		 * associate
		 * deauthenticate
		 * disassociate
		 * join_ibss
		 * join_mesh
		 * set_tx_bitrate_mask
		 * frame
		 * frame_wait_cancel
		 * set_wiphy_netns
		 * set_channel
		 * set_wds_peer
		 * probe_client
		 * set_noack_map
		 * register_beacons
		 * start_p2p_device
		 * set_mcast_rate
		 * Unknown command (104)
		 * connect
		 * disconnect
	Supported TX frame types:
		 * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
	Supported RX frame types:
		 * IBSS: 0x40 0xb0 0xc0 0xd0
		 * managed: 0x40 0xd0
		 * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
		 * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
		 * mesh point: 0xb0 0xc0 0xd0
		 * P2P-client: 0x40 0xd0
		 * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
		 * P2P-device: 0x40 0xd0
	software interface modes (can always be added):
		 * monitor
	interface combinations are not supported
	HT Capability overrides:
		 * MCS: ff ff ff ff ff ff ff ff ff ff
		 * maximum A-MSDU length
		 * supported channel width
		 * short GI for 40 MHz
		 * max A-MPDU length exponent
		 * min MPDU start spacing
	Device supports TX status socket option.
	Device supports HT-IBSS.
	Device supports SAE with AUTHENTICATE command
	Device supports scan flush.
	Device supports per-vif TX power setting
	Driver supports a userspace MPM

My novice eye understands it is supported because AP appears in both "supported TX and RX frame types".

I also found this document about my wireless card : Intel Centrino Ultimate-N 6300 which says under Technical specifications - General - Roaming : "Supports seamless roaming between respective access points (802.11b, 802.11g, 802.11a/b/g, and 802.11a/b/g/n)"

GarryRicketson, you're right I don't want to install Windows over Debian. As for asking a tech shop I would prefer to avoid it, or maybe consider it as a last resort.

I think I have found something more. I tried to use NM in command line mode to setup the wifi hotspot but didn't succeed, I don't understand everything in the man page.
After, I tried different things and this is what I found :
I first turned on the wifi hotspot via the wifi settings window. Then :

Code: Select all

simon@sj:~$ nmcli connection
NAME                UUID                                  TYPE             DEVICE 
Hotspot             cd1004ec-d1a3-4403-b4a1-e5ee2bccb256  802-11-wireless  --     
Hotspot             feb2a4b2-5e8c-42ed-9079-44a39a3306f3  802-11-wireless  --     
Lindihopp           99831902-7da9-46ab-bd28-26bbdc8f39ee  802-11-wireless  --     
eduroam             b47c548a-721f-45e9-928c-6cdfbf92d54d  802-11-wireless  --     
WAX                 c1b00afc-e650-45fd-9358-ced6a6597015  802-11-wireless  --     
Wired connection 1  76766154-0f7d-4e01-821e-b82847344f99  802-3-ethernet   eth0 

Wired connection 1 is my current ethernet connection.
WAX, eduroam and Lindihopp are wifi networks I have connected to recently.
And this Hotspot appears twice I don't know why.
Then I looked at :

Code: Select all

simon@sj:~$ nmcli connection show Hotspot
connection.id:                          Hotspot
connection.uuid:                        cd1004ec-d1a3-4403-b4a1-e5ee2bccb256
connection.interface-name:              --
connection.type:                        802-11-wireless
connection.autoconnect:                 no
connection.timestamp:                   0
connection.read-only:                   no
connection.permissions:                 
connection.zone:                        --
connection.master:                      --
connection.slave-type:                  --
connection.secondaries:                 
connection.gateway-ping-timeout:        0
802-11-wireless.ssid:                   sj
802-11-wireless.mode:                   adhoc
802-11-wireless.band:                   --
802-11-wireless.channel:                0
802-11-wireless.bssid:                  --
802-11-wireless.rate:                   0
802-11-wireless.tx-power:               0
802-11-wireless.mac-address:            00:24:D7:F6:38:C8
802-11-wireless.cloned-mac-address:     --
802-11-wireless.mac-address-blacklist:  
802-11-wireless.mtu:                    auto
802-11-wireless.seen-bssids:            
802-11-wireless.hidden:                 yes
802-11-wireless-security.key-mgmt:      none
802-11-wireless-security.wep-tx-keyidx: 0
802-11-wireless-security.auth-alg:      --
802-11-wireless-security.proto:         
802-11-wireless-security.pairwise:      
802-11-wireless-security.group:         
802-11-wireless-security.leap-username: --
802-11-wireless-security.wep-key0:      --
802-11-wireless-security.wep-key1:      --
802-11-wireless-security.wep-key2:      --
802-11-wireless-security.wep-key3:      --
802-11-wireless-security.wep-key-flags: 0 (none)
802-11-wireless-security.wep-key-type:  1 (key)
802-11-wireless-security.psk:           --
802-11-wireless-security.psk-flags:     0 (none)
802-11-wireless-security.leap-password: --
802-11-wireless-security.leap-password-flags:0 (none)
ipv4.method:                            shared
ipv4.dns:                               
ipv4.dns-search:                        
ipv4.addresses:                         
ipv4.routes:                            
ipv4.ignore-auto-routes:                no
ipv4.ignore-auto-dns:                   no
ipv4.dhcp-client-id:                    --
ipv4.dhcp-send-hostname:                yes
ipv4.dhcp-hostname:                     --
ipv4.never-default:                     no
ipv4.may-fail:                          yes
ipv6.method:                            auto
ipv6.dns:                               
ipv6.dns-search:                        
ipv6.addresses:                         
ipv6.routes:                            
ipv6.ignore-auto-routes:                no
ipv6.ignore-auto-dns:                   no
ipv6.never-default:                     no
ipv6.may-fail:                          yes
ipv6.ip6-privacy:                       -1 (unknown)
ipv6.dhcp-hostname:                     --

connection.id:                          Hotspot
connection.uuid:                        feb2a4b2-5e8c-42ed-9079-44a39a3306f3
connection.interface-name:              --
connection.type:                        802-11-wireless
connection.autoconnect:                 no
connection.timestamp:                   0
connection.read-only:                   no
connection.permissions:                 
connection.zone:                        --
connection.master:                      --
connection.slave-type:                  --
connection.secondaries:                 
connection.gateway-ping-timeout:        0
802-11-wireless.ssid:                   sj
802-11-wireless.mode:                   adhoc
802-11-wireless.band:                   --
802-11-wireless.channel:                0
802-11-wireless.bssid:                  --
802-11-wireless.rate:                   0
802-11-wireless.tx-power:               0
802-11-wireless.mac-address:            00:24:D7:F6:38:C8
802-11-wireless.cloned-mac-address:     --
802-11-wireless.mac-address-blacklist:  
802-11-wireless.mtu:                    auto
802-11-wireless.seen-bssids:            
802-11-wireless.hidden:                 yes
802-11-wireless-security.key-mgmt:      none
802-11-wireless-security.wep-tx-keyidx: 0
802-11-wireless-security.auth-alg:      --
802-11-wireless-security.proto:         
802-11-wireless-security.pairwise:      
802-11-wireless-security.group:         
802-11-wireless-security.leap-username: --
802-11-wireless-security.wep-key0:      --
802-11-wireless-security.wep-key1:      --
802-11-wireless-security.wep-key2:      --
802-11-wireless-security.wep-key3:      --
802-11-wireless-security.wep-key-flags: 0 (none)
802-11-wireless-security.wep-key-type:  1 (key)
802-11-wireless-security.psk:           --
802-11-wireless-security.psk-flags:     0 (none)
802-11-wireless-security.leap-password: --
802-11-wireless-security.leap-password-flags:0 (none)
ipv4.method:                            shared
ipv4.dns:                               
ipv4.dns-search:                        
ipv4.addresses:                         
ipv4.routes:                            
ipv4.ignore-auto-routes:                no
ipv4.ignore-auto-dns:                   no
ipv4.dhcp-client-id:                    --
ipv4.dhcp-send-hostname:                yes
ipv4.dhcp-hostname:                     --
ipv4.never-default:                     no
ipv4.may-fail:                          yes
ipv6.method:                            auto
ipv6.dns:                               
ipv6.dns-search:                        
ipv6.addresses:                         
ipv6.routes:                            
ipv6.ignore-auto-routes:                no
ipv6.ignore-auto-dns:                   no
ipv6.never-default:                     no
ipv6.may-fail:                          yes
ipv6.ip6-privacy:                       -1 (unknown)
ipv6.dhcp-hostname:                     --

Both Hotspot appears to be the same except for the uuid.
What bothers me is the line :

Code: Select all

802-11-wireless.hidden:                 yes

After some searching I ended up scrolling down the nm-settings man page.
In "Table 29. 802-11-wireless setting", entry "hidden", it is said that the default value should be FALSE, and also "If TRUE, indicates this network is a non-broadcasting network that hides its SSID. In this case various workarounds may take place, such as probe-scanning the SSID for more reliable network discovery. However, these workarounds expose inherent insecurities with hidden SSID networks, and thus hidden SSID networks should be used with caution."

I don't know how to switch the value of the "802-11-wireless.hidden" field. Should I even do it ?

[Thorny]

Head_on_a_Stick and Thorny : I think the card supports wifi broadcasting.

It looks that way to me too.

And this Hotspot appears twice I don't know why.

Presumably because it is two bands ,

802-11-wireless.mode: adhoc

I am not an expert on this topic but I remember from when people in forums started mentioning hotspots that adhoc type connections didn't connect to phones. Adhoc was more for computer to computer, like in a meeting. You certainly don't want WEP security in 2017 it just isn't secure any longer.

I did find this site that was updated in Jan 2016 describing how to accomplish a hotspot on both Debian and Ubuntu that has WPA2 security. Maybe have a look at it and see if it makes sense for your use case.
https://www.cyberciti.biz/faq/debian-ub ... ess-point/