ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@open-mesh.com>
To: ath10k@lists.infradead.org
Cc: Ben Greear <greearb@candelatech.com>,
	Yeoh Chun-Yeow <yeohchunyeow@gmail.com>,
	Pushpal Sidhu <psidhu@gateworks.com>
Subject: Re: IBSS mode is now supported by CT firmware.
Date: Thu, 4 Dec 2014 16:28:55 +0100	[thread overview]
Message-ID: <78773989.kHFoMHjKGm@bentobox> (raw)
In-Reply-To: <547CAC1E.2000709@candelatech.com>

On Monday 01 December 2014 09:57:50 Ben Greear wrote:
> If you have time, can you see if you can get encryption working with
> ath9k to ath9k?  I could not get that working, and I am not sure if
> it is my supplicant setup or if I have some other bugs somewhere...
> 
> Please post config files if you do get it working.

My wpa_supplicant config:

ap_scan=2
network={
	mode=1
	scan_ssid=0
	ssid="mesh"
	bssid=02:BA:DE:AF:FE:01
	key_mgmt=WPA-PSK
	proto=RSN
	frequency=2462
	fixed_freq=1
	beacon_int=100
	mcast_rate=18
	ibss_ht_mode=HT20
	psk="89b8e7e66900dd31b4d1fefa60ed3efb"
}

You need at least the wpa_supplicant version from 
http://w1.fi/cgit/hostap/commit/?id=13adc57b39091dc59372efbeb614b74310dd2e02


> And, what is ath9k to ath9k transfer rates?

I don't have numbers here which I am allowed to post but it is only slightly 
(really tiny difference when measurable at all) slower than the AP<->Sta 
setup.

But you also need an wpa_supplicant patch to enable HT-rates (together with 
wpa_supplicant).

http://lists.shmoo.com/pipermail/hostap/2012-November/026934.html

Btw. I haven't tested your fw and thus cannot say if anything written above 
would also work with ath10k.

Kind regards,
	Sven

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  reply	other threads:[~2014-12-04 15:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-26  0:59 IBSS mode is now supported by CT firmware Ben Greear
2014-11-26  1:21 ` Yeoh Chun-Yeow
2014-11-26  1:39   ` Ben Greear
2014-11-26  1:48     ` Yeoh Chun-Yeow
2014-11-26  1:50       ` Ben Greear
2014-11-26  2:14         ` Yeoh Chun-Yeow
2014-11-26  1:57 ` Dave Taht
2014-11-26 22:36 ` Pushpal Sidhu
2014-11-27  1:04   ` Yeoh Chun-Yeow
2014-11-28 11:42     ` Yeoh Chun-Yeow
2014-11-28 16:28       ` Ben Greear
2014-11-29  0:25         ` Yeoh Chun-Yeow
2014-12-01 17:38         ` Pushpal Sidhu
2014-12-01 17:57           ` Ben Greear
2014-12-04 15:28             ` Sven Eckelmann [this message]
2014-12-01 17:13     ` Pushpal Sidhu

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=78773989.kHFoMHjKGm@bentobox \
    --to=sven@open-mesh.com \
    --cc=ath10k@lists.infradead.org \
    --cc=greearb@candelatech.com \
    --cc=psidhu@gateworks.com \
    --cc=yeohchunyeow@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox