Tell wpa_action.sh to reconnect if can't ping GW
shafi.ath9k at gmail.com
Sun Apr 24 09:04:40 EDT 2011
On Sat, Apr 23, 2011 at 11:32 AM, Curtis Larsen <curtlarsen at gmail.com> wrote:
> On Fri, Apr 22, 2011 at 3:32 AM, Mohammed Shafi <shafi.ath9k at gmail.com> wrote:
>> On Fri, Apr 22, 2011 at 3:02 PM, Mohammed Shafi <shafi.ath9k at gmail.com> wrote:
>>> On Fri, Apr 22, 2011 at 11:39 AM, Curtis Larsen <curtlarsen at gmail.com> wrote:
>>>> My Atheros AR9280 somewhat frequently stops sending traffic but the
>>>> wireless controller, and my client both seem to think I am connected.
>>>> This is evident by doing a "iwconfig", or "iw dev wlan2 link" on the
>>>> client. I usually end-up typing "wa_cli re-associate to make things
>>>> resume. Is there an automated way to make wpa_action re-associate
>>>> when my client stops getting ping replies to his default gateway?
>>> may be some problem in the driver?
> Yes, I suppose it could be a problem with the driver or a problem with
> the AP (Cisco 1142). I think I will be more successful at coming up
> with a good work-around than identifying the source of the problem in
> this case since no information seems to be available when it occurs
> from either the client or the AP in debug mode.
I don't know whether you are using the latest driver updates. you can
quickly try with compat-wireless
hoping there is some fix for your problem.
> It seems it would not be to difficult though to add something to
> wpa_action.sh that triggers an automatic re-associate if it can't ping
> the default gateway. Does anyone know how to do add an automatic
> script like this? Or does anyone have another approach to keep the
> connectivity going in this circumstance?
sorry i have not digged into it and i don't know
More information about the HostAP