From: Ari Entlich <lmage11@twcny.rr.com>
To: Hin-Tak Leung <hintak.leung@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Help debugging unexpected disassociations?
Date: Sat, 10 Jan 2009 23:58:46 -0500 [thread overview]
Message-ID: <1231649926.21931.5.camel@g4mdd.entnet> (raw)
In-Reply-To: <3ace41890901100516mc2e1ee1h42c4f67b552f7d73@mail.gmail.com>
On Sat, 2009-01-10 at 13:16 +0000, Hin-Tak Leung wrote:
> On Sat, Jan 10, 2009 at 2:13 AM, <lmage11@twcny.rr.com> wrote:
> <snipped>
> >> 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.
> >
> > You need only ask. :)
>
> That info should have been in your first post, or the 2nd...
The first post contained all the information that I felt at the time was
relevant. The second post existed solely to get people to notice me (by
the way, how was it "no use"? I seem to have gotten someone to listen to
me...). If I was wrong in my initial assumption, it is completely within
your capability to correct me without sounding as if I've put some sort
of terrible burden on your head for no reason.
> And you still have not answered one: what distro - that alone would
> have answered or at least hinted at most of the software versions,
> etc.
I'm sorry for not answering this question, somehow I overlooked it. I'm
using Gentoo, which is why my wpa_supplicant is so old - 0.5.7 is the
newest stable version in Gentoo (no idea why).
> 'read my mind'... you are the person asking for help, why do you
> expect others to *chase after you* for info?
Please quit with this "read my mind" crap. If I were asking you to read
my mind, I would not be telling you the information you ask me for or
demanding results before I tell you the required information. I am doing
neither of these things. And also, the fact that you've had to ask me
some questions hardly means you're having to "chase after" anything.
> Most people won't bother.
Most people want to improve the software they write. If they didn't,
posting to this mailing list would be pointless.
> > I am using wpa_supplicant 0.5.7. I am aware that this is a really old version,
> > and I can try updating it if you think that would make a difference. I am running
> > on a Thinkpad T61, which is 64-bit. I think I already said which chip I'm using,
> > but I'll say it again. It's an IWL4965.
>
> Now we are getting somewhere - and my first reply did ask you to run
> wpa_supplicant in the foreground.
> Even for the 0.5.x series, 0.5.10 is current... and most people are
> using 0.6.x . wpa_supplicant (not the driver) is responsible for
> encryption and authentication, and you had a deauthentication problem.
> Hello, anybody home??!!
Given that the version I'm using *CAN* authenticate, it doesn't
immediately make sense to me why wpa_supplicant would be causing this
problem, unless wpa_supplicant is intentionally trying to screw me up by
deauthenticating me. I will try updating, but would you please try a
little harder to hide the fact that you consider me a retard for no
reason next time? Thanks.
> So, as you yourself suggested, you should update. And while you are at
> it, read wpa_supplicant's doc, and work out the debug options and what
> I meant by 'run it in the foreground'.
I know what foreground means. If you look at my response, I guessed that
you meant in order to get debugging messages, which clearly shows that I
knew what you were talking about. And I have in fact tried this (even
before you suggested it), but have run into other problems. I'll try
again.
Ari
next prev parent reply other threads:[~2009-01-11 4:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-10 2:13 Help debugging unexpected disassociations? lmage11
2009-01-10 13:16 ` Hin-Tak Leung
2009-01-11 4:58 ` Ari Entlich [this message]
2009-01-11 14:58 ` Hin-Tak Leung
2009-01-11 15:48 ` Hin-Tak Leung
-- strict thread matches above, loose matches on Subject: below --
2008-12-30 1:38 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
2009-01-08 23:12 ` reinette chatre
2009-01-08 23:22 ` lmage11
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=1231649926.21931.5.camel@g4mdd.entnet \
--to=lmage11@twcny.rr.com \
--cc=hintak.leung@gmail.com \
--cc=linux-wireless@vger.kernel.org \
/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