Hey Dirk,
> No need for censorship, I did some quick tests and stripped down my
> wpa_supplicant.conf to a single entry. With this configuration I get a
> lot of traces:
>
> ctrl_interface=/var/run/wpa_supplicant
> eapol_version=1
> ap_scan=1
> fast_reauth=1
>
> network={
> frequency=2412
> group=TKIP
> key_mgmt=NONE
> mode=1
> pairwise=NONE
> ssid="Nokia_n9"
> }
>
> I will also attach a dmesg output of my tests.
>
> > * your wpa_supplicant command line parameters when running
>
> It is running with a wpa_cli like this:
>
> /usr/sbin/wpa_supplicant -c /etc/wpa_supplicant/wpa_supplicant.conf \
> -W -B -i wlp4s0 -P /var/run/wpa_supplicant-wlp4s0.pid
> /usr/bin/wpa_cli -a /etc/wpa_supplicant/wpa_cli.sh \
> -p /var/run/wpa_supplicant -i wlp4s0 -P /var/run/wpa_cli-wlp4s0.pid -B
>
Thanks a lot for this, I could reproduce the issue and fix it, will send the
fix
in a minute - please try and report back.
Just two notes on your setup in case you are interested:
* Your wpa-supplicant setup looks a little like an old WPA-NONE setup, but
this is not supported anymore and will not encrypt your messages. Please have
a look at IBSS/RSN if you want encryption.
* Your wpa_supplicant uses the old wext interface to the kernel. This is
deprecated, it would better to use the (not so) new nl80211 interface instead.
You will also get goodies such as 802.11n rates in ad-hoc mode if your
hardware supports it. :)
Thanks again for reporting,
Simon
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
