Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Novice
2,157 Views

How to force wpa_supplicant to create Ad-Hoc network with specific BSSID/cell-id?

Currently, wpa_supplicant on Edison ignores the bssid parameter defined within the wpa_supplicant.conf when creating an ad-hoc network. My wpa_supplicant file is as below:

ctrl_interface=/var/run/wpa_supplicant

ctrl_interface_group=0

config_methods=virtual_push_button virtual_display push_button keypad

update_config=1

fast_reauth=1

device_name=Edison

manufacturer=Intel

model_name=Edison

ap_scan=1

network={

ssid="mesh"

mode=1

scan_ssid=1

frequency=2412

key_mgmt=NONE

auth_alg=OPEN

wep_key0="akakakakakaka"

wep_tx_keyidx=0

bssid=DE:AD:BE:EF:00:00

}

On creation of ad-hoc network, a random cell-id is used instead.

wpa_supplicant -v is

wpa_supplicant v2.1-devel

Copyright (c) 2003-2013, Jouni Malinen <</span>mailto:j@w1.fi j@w1.fi> and contributors

Kernel is 3.10.17-yocto-standard

What should I do?

Tags (1)
7 Replies
Highlighted
Employee
53 Views

Hi myopenid,

Are you following the Edison Wi-Fi User Guide to create this Ad-hoc network? Reading some other threads I've been noticing that versions of wpa_supplicant under 2.0 present this issue, however, you're using version 2.1 and you're getting the same issue. Have you tried going back to version 2.0 or maybe updating to a newer version? Just to make sure that this is not the issue.

Regards,

PabloM_Intel

Highlighted
Employee
53 Views

Hi,

Have you been able to work on this?

Have you tried with another version?

Regards,

Charlie

0 Kudos
Highlighted
Novice
53 Views

PabloM_Intel CMata_Intel

Hi, I have tried to compile and successfully ran wpa_cupplicant 2.5 and it's corresponding wpa_cli but BSSID/cell-id problem still persist. I believe this is a driver issue?

Is it possible to hardcode the address within ieee80211_sta_create_ibss() instead of generating a random one?

How do you suggest that I proceed?

0 Kudos
Highlighted
Employee
53 Views

Hi myopenid,

We are still investigating on your case. Thank you for your patience.

Regards,

PabloM_Intel

0 Kudos
Highlighted
Employee
53 Views

Hi myopenid,

Could you please save the following text in a script named wpacli_ibss_open.sh?

# !/bin/sh

wpa_cli -iwlan0 disconnect

wpa_cli -iwlan0 remove_network all

wpa_cli -iwlan0 add_network

wpa_cli -iwlan0 set_network 0 frequency 2412

wpa_cli -iwlan0 set_network 0 mode 1

wpa_cli -iwlan0 set_network 0 ssid \"mesh\"

wpa_cli -iwlan0 set_network 0 auth_alg OPEN

wpa_cli -iwlan0 set_network 0 key_mgmt NONE

wpa_cli -iwlan0 set_network 0 scan_ssid 1

wpa_cli -iwlan0 select_network 0

wpa_cli -iwlan0 enable_network 0

wpa_cli -iwlan0 status

Save the script file and execute the following commands:

chmod +x wpacli_ibss_open.sh

./wpacli_ibss_open.sh

Wpa_cli –iwlan0 status

 

Please share a screenshot of the output to see what you're getting.

Regards,

Pablo

 

0 Kudos
Highlighted
Novice
53 Views

PabloM_Intel here's the output of the script

root@edison:~# ./ibss.sh

OK

OK

0

OK

OK

OK

OK

OK

OK

OK

OK

wpa_state=SCANNING

p2p_device_address=7a:4b:87:a6:a4:06

address=78:4b:87:a6:a4:06

This is on a fresh copy of 3.10.17-yocto-standard

0 Kudos
Highlighted
Employee
53 Views

Hi myopenid,

We apologize for the late reply. We've been investigating the case and found that the BSSID cannot be set manually, this is because part of the generated number taken from the OUI, which is the manufacturer's identity.

Regards,

Pablo

0 Kudos