I have found a process by which it is possible to create/join a three-node IBSS using RSN - however, I'm not sure if it is the result of a bug within wpa_supplicant. Is there a simpler way of accomplishing this?<div><br>
</div><div>My wpa_supplicant.conf (initially), using wpa_supplicant 0.7.2 is:</div><div>ctrl_interface=DIR-/var/run/wpa_supplicant GROUP=wheel</div><div>ap_scan=2</div><div>network={</div><div> ssid="swat"</div>
<div> mode=1</div><div> frequency=2412</div><div> proto=RSN</div><div> key_mgmt=WPA-PSK</div><div> pairwise=NONE</div><div> group=CCMP</div><div> psk=1234567890</div><div>}</div><div><br></div><div>Setup:</div>
<div>1. sudo service NetworkManager stop</div><div>2. sudo ifconfig eth1 up 192.168.1.12x/24</div><div>3. sudo pkill wpa</div><div><br></div><div>Process:</div><div>1. Run wpa_supplicant -dd -K -i eth1 -c /etc/wpa_supplicant/wpa_supplicant.conf -D wext</div>
<div>2. Run wpa_cli</div><div> At this point, wpa_supplicant should be associating with a BSSID and then disassociating roughly ten seconds later due to an association timeout.</div><div>3. With both wpa_supplicant and wpa_cli still running, modify wpa_supplicant.conf so that key_mgmt=WPA-PSK is replaced by key_mgmt=WPA-NONE, and save the file.</div>
<div>4. Within wpa_cli, run "reconfigure"</div><div> After a scan, wpa_supplicant should associate with a BSSID and not time out. This connection will remain stable until wpa_supplicant is killed.</div><div>
<br></div><div>In order for a node B to join the IBSS that was previously created by node A, the above process must be completed, with the additional requirement that the modification of wpa_supplicant.conf and "reconfigure" of wpa_supplicant must occur while B's wpa_supplicant is associated with the same BSSID with which A is associated, but before B's association times out. If B's association does time out, wpa_supplicant and wpa_cli must both be killed on node B, wpa_supplicant.conf must return to its initial state as key_mgmt=WPA-PSK, and the entire process must begin again.</div>
<div><br></div><div>It is important to note that wpa_supplicant can not be started with key_mgmt=WPA-NONE - this results in a persistent loop of scans and no attempted associations. The above-detailed process does work for three nodes, but is very cumbersome to apply. Even if I write a bash script that parses the output of wpa_supplicant and wpa_cli, edits wpa_supplicant.conf at the right time, and issues 'wpa_cli reconfigure,' there seems to be a bit of luck involved with getting three nodes on the same IBSS. Is there a bug somewhere within the code for WPA-PSK or WPA-NONE that is preventing me from simply starting wpa_supplicant with key_mgmt=WPA-NONE, or is there an easier way to achieve a three-node IBSS using RSN?</div>
<div><br></div><div>System configuration:</div><div>HP tc4200 with Intel PRO/Wireless 2200 802.11b/g mini-pci adapter</div><div> (ipw2200 driver version 3.1)</div><div>wpa_supplicant v0.7.2 compiled from source with the following options in .config:</div>
<div> CONFIG_DRIVER_RALINK=y</div><div> CONFIG_DRIVER_WEXT=y</div><div> CONFIG_CTRL_IFACE=y</div><div> CONFIG_BACKEND=file</div><div> CONFIG_DEBUG_FILE=y</div><div> CONFIG_WPA_TRACE=y</div><div>Fedora 13 (x86)</div>
<div>Linux kernel 2.6.33.6-147.2.4</div><div><br></div><div>Thank you for your continued support.</div>