Hi, This is a patch against AA which fixes it for us:
wpa_supplicant: fix beacon_int configuration option
wpa_supplicant expects beacon_int instead of beacon_interval in its
config file.
diff --git a/package/hostapd/files/wpa_supplicant.sh
b/package/hostapd/files/wpa_supplicant.sh
index
I have encountered the following error while trying to patch the file:
patching file attitude_adjustment/package/hostapd/files/wpa_supplicant.sh
Hunk #1 FAILED at 119.
Hunk #2 FAILED at 163.
2 out of 2 hunks FAILED -- saving rejects to file
On 10/10/2013 11:28 AM, cmsv wrote:
I have encountered the following error while trying to patch the file:
patching file attitude_adjustment/package/hostapd/files/wpa_supplicant.sh
Hunk #1 FAILED at 119.
Hunk #2 FAILED at 163.
2 out of 2 hunks FAILED -- saving rejects to file
Hi cmsv,
Bruno's patch seems to have had its tab spacing munged in transit, which is
why the patch failed. I'm attaching a Gzipped version of that same patch,
against AA r38347, which should apply cleanly to your build tree.
As for leaving beacon_int unspecified, that would tell the driver to
I believe this problem appeared on or about r36682, which coincides with a
hostapd update to AA. This suggests a regression in hostapd w/r/t/ to
beacon interval code.
I can confirm the same problem happens when attempting to specify
beacon_int on a single psk2-encrypted adhoc interface, not just
Right now i tested with DISTRIB_REVISION=r38305
Successfully initialized wpa_supplicant
Line 12: unknown network field 'beacon_interval'.
Line 33: failed to parse network block.
Failed to read or parse configuration '/var/run/wpa_supplicant-adhoc0.conf'.
enable_mac80211(radio0): Failed to set up
