From: Ben Greear <greearb@candelatech.com>
To: ath10k <ath10k@lists.infradead.org>
Cc: "hostap@lists.shmoo.com" <hostap@lists.shmoo.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: CT ath10k firmware now supports IBSS + RSN
Date: Fri, 10 Apr 2015 16:32:29 -0700 [thread overview]
Message-ID: <55285D8D.6070703@candelatech.com> (raw)
First, thanks to everyone that helped me with questions,
QCA/Tieto's upstream patches, etc.
This needs more testing, but it appears to at least mostly work.
I am using this 4.0 related kernel. I think only the last 3 patches
are IBSS specific, but possibly there are others that matter as well.
http://dmz2.candelatech.com/git/gitweb.cgi?p=linux-4.0.dev.y/.git;a=summary
Firmware binaries and release notes are here:
http://www.candelatech.com/downloads/ath10k-fw-beta/
I'm using a very recent wpa_supplicant..upstream should work I think,
but I am using this one:
https://github.com/greearb/hostap-ct/tree/master/hostapd
supplicant needs to have this enabled, among other things:
CONFIG_IBSS_RSN=y
I suspect there are lingering bugs, perhaps in supplicant, as it seems to take
a few tries for the 4-way to happen properly, and I have to re-start hostapd
on each side each time I associate.
My supplicant config files look like this (you can comment out any options
your supplicant doesn't know about...I have a few extra features not specifically
related to IBSS in my hostapd tree)
ctrl_interface=/var/run/wpa_supplicant
fast_reauth=1
concurrent_assoc_ok=1
scan_cur_freq=1
min_scan_gap=5
freq_list=5180
bss_max_count=2000
network={
ssid="ota-ibss-ssid"
disable_ht=0
disable_vht=0
ieee80211w=0
disable_ht40=1
disable_sgi=0
ht_mcs=""
disable_max_amsdu=-1
ampdu_factor=-1
ampdu_density=-1
freq_list=5180
fixed_freq=1
mode=1
frequency=5180
proto=RSN
key_mgmt=WPA-PSK
#psk="ben-ota-passwd"
psk=fc29b6edf32abd7a9818af3c94b2aa5364c785eee33ed3df11605a3db8f905bc
pairwise=CCMP
group=CCMP
proactive_key_caching=0
}
I'm curious to know if anyone tries it out.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
WARNING: multiple messages have this Message-ID (diff)
From: Ben Greear <greearb@candelatech.com>
To: ath10k <ath10k@lists.infradead.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"hostap@lists.shmoo.com" <hostap@lists.shmoo.com>
Subject: CT ath10k firmware now supports IBSS + RSN
Date: Fri, 10 Apr 2015 16:32:29 -0700 [thread overview]
Message-ID: <55285D8D.6070703@candelatech.com> (raw)
First, thanks to everyone that helped me with questions,
QCA/Tieto's upstream patches, etc.
This needs more testing, but it appears to at least mostly work.
I am using this 4.0 related kernel. I think only the last 3 patches
are IBSS specific, but possibly there are others that matter as well.
http://dmz2.candelatech.com/git/gitweb.cgi?p=linux-4.0.dev.y/.git;a=summary
Firmware binaries and release notes are here:
http://www.candelatech.com/downloads/ath10k-fw-beta/
I'm using a very recent wpa_supplicant..upstream should work I think,
but I am using this one:
https://github.com/greearb/hostap-ct/tree/master/hostapd
supplicant needs to have this enabled, among other things:
CONFIG_IBSS_RSN=y
I suspect there are lingering bugs, perhaps in supplicant, as it seems to take
a few tries for the 4-way to happen properly, and I have to re-start hostapd
on each side each time I associate.
My supplicant config files look like this (you can comment out any options
your supplicant doesn't know about...I have a few extra features not specifically
related to IBSS in my hostapd tree)
ctrl_interface=/var/run/wpa_supplicant
fast_reauth=1
concurrent_assoc_ok=1
scan_cur_freq=1
min_scan_gap=5
freq_list=5180
bss_max_count=2000
network={
ssid="ota-ibss-ssid"
disable_ht=0
disable_vht=0
ieee80211w=0
disable_ht40=1
disable_sgi=0
ht_mcs=""
disable_max_amsdu=-1
ampdu_factor=-1
ampdu_density=-1
freq_list=5180
fixed_freq=1
mode=1
frequency=5180
proto=RSN
key_mgmt=WPA-PSK
#psk="ben-ota-passwd"
psk=fc29b6edf32abd7a9818af3c94b2aa5364c785eee33ed3df11605a3db8f905bc
pairwise=CCMP
group=CCMP
proactive_key_caching=0
}
I'm curious to know if anyone tries it out.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next reply other threads:[~2015-04-10 23:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 23:32 Ben Greear [this message]
2015-04-10 23:32 ` CT ath10k firmware now supports IBSS + RSN Ben Greear
2015-04-13 17:41 ` Ben Greear
2015-04-13 17:41 ` Ben Greear
2015-04-14 0:10 ` Ben Greear
2015-04-14 0:10 ` Ben Greear
2015-04-14 5:34 ` Michal Kazior
2015-04-14 5:34 ` Michal Kazior
2015-04-14 15:01 ` Ben Greear
2015-04-14 15:01 ` Ben Greear
2015-04-15 21:51 ` Ben Greear
2015-04-15 21:51 ` Ben Greear
2015-08-17 13:11 ` Sven Eckelmann
2015-08-17 13:11 ` Sven Eckelmann
2015-08-17 15:33 ` Ben Greear
2015-08-17 15:33 ` Ben Greear
2015-08-18 9:38 ` Sven Eckelmann
2015-08-18 9:38 ` Sven Eckelmann
2015-08-18 16:11 ` Ben Greear
2015-08-18 16:11 ` Ben Greear
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55285D8D.6070703@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=hostap@lists.shmoo.com \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.