From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Ben Greear <greearb@candelatech.com>
Cc: ath10k <ath10k@lists.infradead.org>
Subject: Re: Trouble connecting to broadcom AC APs?
Date: Thu, 20 Mar 2014 08:36:58 +0200 [thread overview]
Message-ID: <87txatfkad.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <5329CD60.6080609@candelatech.com> (Ben Greear's message of "Wed, 19 Mar 2014 10:01:20 -0700")
Ben Greear <greearb@candelatech.com> writes:
> We are seeing various funny things when trying to connect
> ath10k stations to commercial APs with broadcom AC NICs.
>
> It sort of works sometimes, but we often see failure to
> acquire DHCP lease in a timely manner, etc.
So it's a problem with broadcast frames? With or without encryption? Did
you try disabling power save?
> Similar testing on APs using QCA AC NICs appears to work
> much better.
>
> Our problems could be most anything, including the fact that this
> testing is done on our modified firmware, but I am curious if anyone
> else seems any similar issues?
Occasionally I test connecting to D-Link DIR-865L in STA mode. But I
just do just simple ping tests and with manual IPs.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2014-03-20 6:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 17:01 Trouble connecting to broadcom AC APs? Ben Greear
2014-03-20 6:36 ` Kalle Valo [this message]
2014-03-20 15:59 ` Ben Greear
2014-03-20 19:17 ` Adrian Chadd
2014-03-20 19:23 ` Ben Greear
2014-03-20 19:26 ` Adrian Chadd
2014-03-20 23:27 ` Ben Greear
2014-03-20 23:34 ` Adrian Chadd
2014-03-21 6:01 ` Janusz Dziedzic
2014-03-21 7:07 ` Janusz Dziedzic
2014-03-21 17:41 ` Ben Greear
2014-03-24 19:45 ` Janusz Dziedzic
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=87txatfkad.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=greearb@candelatech.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 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.