Linux wireless drivers development
 help / color / mirror / Atom feed
From: "Hin-Tak Leung" <hintak.leung@gmail.com>
To: lmage11@twcny.rr.com
Cc: linux-wireless@vger.kernel.org
Subject: Re: Help debugging unexpected disassociations?
Date: Fri, 9 Jan 2009 21:08:57 +0000	[thread overview]
Message-ID: <3ace41890901091308g7c9f5e2cj5595017131b7afd7@mail.gmail.com> (raw)
In-Reply-To: <20090108231828.QHGIG.228066.root@hrndva-web20-z02>

On Thu, Jan 8, 2009 at 11:18 PM,  <lmage11@twcny.rr.com> wrote:
> ---- Hin-Tak Leung <hintak.leung@gmail.com> wrote:
>> On Thu, Jan 8, 2009 at 10:43 PM,  <lmage11@twcny.rr.com> wrote:
>> > ---- lmage11@twcny.rr.com wrote:
>> >> Hey everyone. I'm using an Intel 4965AGN using the iwlagn
>> >> driver in 2.6.28. When using a specific AP, my connection is
>> >> unexpectedly dropping with nothing more than a
>> >> "wlan0: deauthenticated". Any tips on how I could figure out
>> >> whether this is the driver's fault or the AP's? Another problem I'm
>> >> having is that dhcpcd is timing out a lot, usually after trying to
>> >> reconnect from a connection drop.
>> >>
>> >> The AP is a Linksys WRT54Gv1 with WPA2 and ssid broadcasting enabled.
>> >>
>> >> Thanks!
>> >>
>> >> Ari
>> >
>> > Um... Bump?
>>
>> It is no use and quite annoying to do that - it sounds like "read my
>> mind and spoon-feed me". Your initial post has almost no useful
>> information to speak of (actual log entries, wpa_supplicant config,
>> whether using networkmanager or static config, etc).
>
> Um.
>
> Well considering as I'm not a developer and don't know how to debug
> these things, I think "spoon-feeding" is an appropriate term, no? And
> also, I didn't ask you to read my mind, I didn't even ask you to figure
> out the problem for me, I asked for the information that I would need
> to figure out the problem MYSELF.
>
> As for "useful information", the "wlan0: deauthenticated" is *LITERALLY*
> all I get. I was not lying to you. After stripping out identifying information,
> my wpa_supplicant config would be pretty much completely empty. The config
> for this AP is about as simple as a consumer WPA2 AP config can be. I am not
> using networkmanager.
>
>> You probably should try to run wpa_suplicant in the foreground.
>
> You mean so I can see the debug messages it outputs?

Even if you strip away privacy info (and put in xx.yy.zz) it is still
better than "read my mind and guess my problem".

For example, this is how my deauth looks like, when NetworkManager
cuts the connectiion, in preparation for
suspending to RAM:

wlan2: deauthenticating by local choice (reason=3)

Also, it is always useful to quote versions of relevant software -
what version of wpa_supplicant, and networkmanager you are using; or
even what distribution you are using, and hardware (64-bit, 32-bit).
You have written 3 times and added no new info.

  reply	other threads:[~2009-01-09 21:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-30  1:38 Help debugging unexpected disassociations? lmage11
2009-01-08 22:43 ` lmage11
2009-01-08 23:06   ` Hin-Tak Leung
2009-01-08 23:18     ` lmage11
2009-01-09 21:08       ` Hin-Tak Leung [this message]
2009-01-08 23:12   ` reinette chatre
2009-01-08 23:22     ` lmage11
  -- strict thread matches above, loose matches on Subject: below --
2009-01-10  2:13 lmage11
2009-01-10 13:16 ` Hin-Tak Leung
2009-01-11  4:58   ` Ari Entlich
2009-01-11 14:58     ` Hin-Tak Leung
2009-01-11 15:48     ` Hin-Tak Leung

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=3ace41890901091308g7c9f5e2cj5595017131b7afd7@mail.gmail.com \
    --to=hintak.leung@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lmage11@twcny.rr.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