From: Ben Greear <greearb@candelatech.com>
To: Sven Eckelmann <sven@open-mesh.com>
Cc: Simon Wunderlich <simon@open-mesh.com>,
marek@open-mesh.com, ath10k@lists.infradead.org
Subject: Re: IBSS support in ath10k - our test results and questions
Date: Thu, 09 Apr 2015 19:38:16 -0700 [thread overview]
Message-ID: <55273798.3000004@candelatech.com> (raw)
In-Reply-To: <55257592.1080900@candelatech.com>
I am still getting closer..found place in my 10.1 firmware that was setting
the mcast peer's key-index when it shouldn't, and now I can generate
udp broadcast frames on ath10k and ath9k receives them fine
(and they are encrypted on the air).
But, ARP request and response packets are being transmitted wrong by the ath10k. Looks like
they are truncated and/or scrambled a bit..but they do decrypt on the
ath9k peer (just as mal-formed packet).
I found a bit of stuff that adjusts TID for ARP in the firmware,
but could not find any other special handling.
Anyone know if there is other special handling somewhere that might
account for this?
Thanks,
Ben
On 04/08/2015 11:38 AM, Ben Greear wrote:
> So, I've made some progress.
>
> After fixing PSK (I had it misconfigured all of yesterday!), and with full restart of supplicant,
> I can get the 4-way to complete, and I see PTK and GTK set in driver and firmware.
> I do not know if the keys are set correctly, but the logs seem plausible.
>
> After that, I see plain-text ARPs hit the air (the should be encrypted),
> and the last 21 bytes of the packet appear to be random garbage.
>
> I am guessing driver and/or firmware and/or hardware is not properly
> encrypting the frames.
>
> Off to do some more spelunking in the firmware.
>
> 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
prev parent reply other threads:[~2015-04-10 2:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 17:06 IBSS support in ath10k - our test results and questions Simon Wunderlich
2015-03-19 21:40 ` Ben Greear
2015-03-20 6:44 ` Janusz Dziedzic
2015-03-20 13:56 ` Ben Greear
2015-04-07 21:17 ` Ben Greear
2015-03-20 14:26 ` Simon Wunderlich
2015-03-20 15:32 ` Ben Greear
2015-03-23 11:24 ` Sven Eckelmann
2015-04-06 17:55 ` Ben Greear
2015-04-06 20:04 ` Ben Greear
2015-04-08 18:38 ` Ben Greear
2015-04-10 2:38 ` Ben Greear [this message]
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=55273798.3000004@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=marek@open-mesh.com \
--cc=simon@open-mesh.com \
--cc=sven@open-mesh.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