Linux: How to disable broadcast of SSID in mesh (mode=5) setup of wpa_suplicant.conf

Hi, 

Can you please try changing the following parameter in hostapd.conf file. 

# Send empty SSID in beacons and ignore probe request frames that do not
# specify full SSID, i.e., require stations to know SSID.
# default: disabled (0)
# 1 = send empty (length=0) SSID in beacon and ignore probe request for
# broadcast SSID
# 2 = clear SSID (ASCII 0), but keep the original length (this may be required
# with some clients that do not support empty SSID) and ignore probe
# requests for broadcast SSID
ignore_broadcast_ssid=0

Regards, 

Sudharshan K N

Hi Sudharshan, thanks for responding.

I tried it already but no effect. That is because, I have setup Mesh (mode=5) in wpa_supplicant.conf file. The SSID is under the Network tag. So the hostapd.conf file is not used or called.

Can you suggest an ability to ignore broadcast or alternate way to hide SSID through the wpa_supplicant.conf file.

Thanks,

Senthil Nathan

Thanks Saurabh for responding.

I was looking for this option because I could not establish secured communication with mesh setup. I raised this question in the other thread (Linux/AM3358: Mesh join.sh connected with psk but not ping) as well.

I am not sure what you meant by "not discoverable by conventional wifi devices" because in our open mesh setup, the SSID of mesh was displayed in the phone and laptop Wifi connections. I know it would not allow to connect but i am looking for option to hide the SSID itself.

Could you please get back soon on versions which will help me to establish secured mesh communication. 

Thanks,

Senthil Nathan

HI Senthil ,
mesh id is different from ssid information element - therefore as far as i know conventional devices should not be able to discover mesh devices unless those devices support mesh themselves. are you able to capture mesh beacon and share with us .

Saurabh

Thanks Saurabh, got it. The beacon were not found for the Mesh ID. It got discovered in our Linux laptop, may be it is scanning for mesh devices as well.

For now, I am going to wait till you get back on missing patches for secured mesh communication.

Thanks,

Senthil Nathan

Senthil , thanks for keeping us posted .

Saurabh

Hi Saurabh,

Can you please let us know what Version of OS, Kernel and Firmware combination to be use to make open Mesh + AP working?

Thanks,
Senthil Nathan

Hi , wl8 supports mesh+AP on the same channel .

Saurabh

Hi Saurabh,

I am using wl8 driver only. My Ubuntu is 18.04.2 LTS and Kernel is Linux arm 4.14.108-ti-r104. In this setup, the Mesh + AP not working. Either mesh works as standalone or AP works as standalone but could not start the other when one is running. Please advice.

Thanks,

Senthil Nathan

Hi , We have not ported or tested our drivers on Ubuntu . I saw similar post on this topic : e2e.ti.com/.../2985728

Saurabh