From: Alexey Yudichev <ayudichev@gmail.com>
To: John Murdoch <weejoker@yahoo.com>
Cc: linux-wireless@vger.kernel.org, hostap@lists.shmoo.com
Subject: Re: wlan/eth bridge stops working after a while: how to diagnose?
Date: Wed, 27 Jan 2010 20:37:58 +0000 [thread overview]
Message-ID: <4dd58f491001271237o66bc7cd1p968a8894f324533d@mail.gmail.com> (raw)
In-Reply-To: <17290.75428.qm@web24706.mail.ird.yahoo.com>
Yes, I kept my symptoms simpler not to risk confusing more than one
issue but indeed in many cases the client stops seeing the access
point at all. Restarting hostapd fixes the network visibility but most
likely does not fix the actual IP connectivity. Client keeps getting
IP address correctly though so DHCP works.
On Wed, Jan 27, 2010 at 6:39 PM, John Murdoch <weejoker@yahoo.com> wrote:
> --- On Wed, 27/1/10, Alexey Yudichev <ayudichev@gmail.com> wrote:
>
>> I've got ubuntu 9.10 (hostapd 0.6.9)
>> + compat-wireless-2009-12-11 and
>> the box is acting as a basic wireless internet router.
>> Driver is ath9k
>> and server adapter is D-Link DWA-547. All is working fine
>> for 2-3 days
>> until all of a sudden wireless client (MacBook Pro) stops
>> pinging any
>> hosts on a local network. The wireless association remains
>> and hostapd
>> logs are not showing anything unusual. Restarting hostapd
>> or even
>> networking does not help (although I believe restarting
>> networking
>> does not work well on ubuntu anyway). Only rebooting the
>> server helps.
>
> I've been having the same problems for a long time with two different Mini-PCI cards (AR5416 & AR9160) on Debian 5.0 w/ kernel 2.6.32, with various hostapd and compat-wireless releases (latest combination being hostapd 0.7.1 / compat-wireless 2010-01-26).
>
> Both cards have similar issues where hostapd permanently stops transmitting beacons from between 10mins to just over 24hrs. There's absolutely nothing in any logs to suggest issues. I can however restart hostapd and the problem is immediately resolved.
>
>> What would you advise to check/debug or otherwise what
>> would be the
>> best approach to diagnose the problem? I don't see
>> anything
>> interesting in dmesg, messages or daemon.log at this
>> point.
>
> I'm more than willing to collect logs too if pointed in the right direction.
>
> Regards,
>
> John
>
>
>
>
>
>
next prev parent reply other threads:[~2010-01-27 20:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4dd58f491001270211n7ce690bbm9506d97a50bde8b7@mail.gmail.com>
2010-01-27 10:18 ` wlan/eth bridge stops working after a while: how to diagnose? Alexey Yudichev
2010-01-27 18:39 ` John Murdoch
2010-01-27 20:37 ` Alexey Yudichev [this message]
2010-01-31 6:57 ` Jeffrey Baker
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=4dd58f491001271237o66bc7cd1p968a8894f324533d@mail.gmail.com \
--to=ayudichev@gmail.com \
--cc=hostap@lists.shmoo.com \
--cc=linux-wireless@vger.kernel.org \
--cc=weejoker@yahoo.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