From: "Christoph .J Thompson" <cjsthompson@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Luis Correia <luis.f.correia@gmail.com>,
Jon Fairbairn <jon.fairbairn@cl.cam.ac.uk>,
linux-wireless@vger.kernel.org
Subject: Re: rt73usb Access point status
Date: Mon, 11 May 2009 03:40:16 +0200 [thread overview]
Message-ID: <20090511034016.17f0deb0.cjsthompson@gmail.com> (raw)
In-Reply-To: <1241085910.27613.16.camel@johannes.local>
On Thu, 30 Apr 2009 12:05:10 +0200
Johannes Berg <johannes@sipsolutions.net> wrote:
>
> > The solution they have found is not optimal, b ut works in their scenario.
> >
> > You will need to modify hostapd, according to this blog post:
> > http://eznemegy.blog.hu/2008/12/14/using_rt2x00_wireless_driver_with_hostapd
>
> Based on that information, I have removed the "Yes (under development)"
> note from the driver page since it doesn't really support it... In fact,
> I'm surprised it works even with that hack since hostapd usually polls
> the station with nullfunc frames and waits for an ack.
>
> johannes
>
Another success story with this hack:
I've been using the very same USB dongle Jon is speaking about with a patched hostapd on my AP for over 2 months and so far I didn't have any problems whatsoever with it. WPA2 works fine too. I'm using stock Linux 2.6.29.2 and hostapd 0.6.9 patched. The client machine is never far away from the AP (so that limits possible problems) and it's also running stock Linux 2.6.29.2. The client's wireless card is an ath5k.
--
Christoph .J Thompson <cjsthompson@gmail.com>
next prev parent reply other threads:[~2009-05-11 1:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-25 14:44 Edimax EW-7318USG as Access Point? Jon Fairbairn
2009-04-30 9:39 ` rt73usb Access point status Jon Fairbairn
2009-04-30 9:51 ` Luis Correia
2009-04-30 9:58 ` Luis Correia
2009-04-30 10:05 ` Johannes Berg
2009-05-11 1:40 ` Christoph .J Thompson [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-04-30 13:41 Joerg Pommnitz
2009-04-30 13:55 ` Johannes Berg
2009-04-30 13:56 ` Luis Correia
2009-05-02 10:18 ` Jon Fairbairn
2009-05-02 10:34 ` Luis Correia
2009-05-11 1:55 ` Christoph .J Thompson
2009-05-12 8:16 ` Jon Fairbairn
2009-05-12 19:58 ` Christoph .J Thompson
2009-05-16 8:58 ` Jon Fairbairn
2009-05-16 9:32 ` Ivo van Doorn
2009-05-17 8:47 ` Jon Fairbairn
2009-05-17 12:51 ` Christoph .J Thompson
2009-05-17 14:31 ` Jon Fairbairn
2009-05-17 16:33 ` Gábor Stefanik
2009-05-18 11:12 ` Alexandre Becholey
2009-05-30 8:12 ` Russell Senior
2009-05-30 15:06 ` Christoph .J Thompson
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=20090511034016.17f0deb0.cjsthompson@gmail.com \
--to=cjsthompson@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=jon.fairbairn@cl.cam.ac.uk \
--cc=linux-wireless@vger.kernel.org \
--cc=luis.f.correia@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).