From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Jonathan Bagg <jbagg@lenbrook.com>
Cc: Anthony Ginger <mapfly@gmail.com>,
<linux-wireless@vger.kernel.org>, <ath6kl-devel@qualcomm.com>
Subject: Re: ath6kl hostapd
Date: Fri, 11 May 2012 09:27:25 +0300 [thread overview]
Message-ID: <4FACB14D.4080507@qca.qualcomm.com> (raw)
In-Reply-To: <4FAC0992.6010603@lenbrook.com>
On 05/10/2012 09:31 PM, Jonathan Bagg wrote:
> On 12-05-10 04:33 AM, Kalle Valo wrote:
>> On 05/04/2012 11:30 PM, Jonathan Bagg wrote:
>>> On 12-05-03 01:15 AM, Kalle Valo wrote:
>>>> That might be challenging. I think it's easier if you add debug messages
>>>> and try to pinpoint where it is failing. For example
>>>> ath6kl_cfg80211_change_iface() is a good place to start debugging.
>>> I tried again and it appears that sometimes (< 10 %) I can make
>>> connections to the ath6kl in AP mode.
>> What exactly happens when a connection fails? What client device are you
>> using?
>
> client = ipad and mac book
>
> Udhcpd keeps sending offers and acks forever.
> Sending OFFER of 192.168.5.80
> Sending OFFER of 192.168.5.80
> Sending ACK to 192.168.5.80
> Sending ACK to 192.168.5.80
> Sending ACK to 192.168.5.80
Maybe it's a broadcast problem or something? Try with manual IPs and
then first run unicast ping separetely both from the client and the AP,
for example:
ping 192.168.5.1
If that works run broadcast ping separetely both from the client and the AP:
ping -b 192.168.1.255
Most likely you need to enable broadcast ping replies to get any answers:
echo 0 > /proc/sys/net/ipv4/icmp_echo_ignore_broadcasts
And if MacOS doesn't support broadcast pings install a real operating
system ;)
Kalle
prev parent reply other threads:[~2012-05-11 6:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-16 11:30 ath6kl hostapd Anthony Ginger
2012-02-27 6:43 ` Kalle Valo
2012-02-27 14:45 ` Anthony Ginger
2012-04-11 8:54 ` Kalle Valo
2012-05-01 19:17 ` Jonathan Bagg
2012-05-01 19:27 ` Kalle Valo
[not found] ` <4FA0535D.2060907@lenbrook.com>
2012-05-03 5:15 ` Kalle Valo
2012-05-04 20:30 ` Jonathan Bagg
2012-05-10 8:33 ` Kalle Valo
2012-05-10 18:31 ` Jonathan Bagg
2012-05-11 6:27 ` Kalle Valo [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=4FACB14D.4080507@qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath6kl-devel@qualcomm.com \
--cc=jbagg@lenbrook.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mapfly@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 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.