linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jon Fairbairn <jon.fairbairn@cl.cam.ac.uk>
To: linux-wireless@vger.kernel.org
Subject: Re: rt73usb Access point status
Date: Sat, 02 May 2009 11:18:29 +0100	[thread overview]
Message-ID: <wfk54zu7t6.fsf@calligramme.charmers> (raw)
In-Reply-To: efe7343f0904300656g127e83e1ge0b21060d6a69955@mail.gmail.com


Luis Correia
<luis.f.correia@gmail.com>
writes:

Hi Luis; thanks for your replies... more below:

> On Thu, Apr 30, 2009 at 14:41, Joerg Pommnitz <pommnitz@yahoo.com> wr=
ote:
>> Reading the mail from Ivo
>> (http://sourceforge.net/mailarchive/message.php?msg_id=3D20080808205=
9.11968.IvDoorn%40gmail.com)

I found that before I posted and found it discouraging,
hence the question.

>> I gather that the ACK in question is not from the peer but from the =
local
>> hardware indicating that the frame was actually sent and not lost du=
e to
>> some local error.
>
> According to Ivo, we cannot be totally sure that the device has sent
> the frame into the air, so no actual ACK is reported back to mac80211=
=2E
>
> The hostapd hack works, as long as the stations are not very far from
> the AP, and thus not 'too many retries' need to be sent.

So is the bug really in hostapd?

> AFAIK, this is not optimal at all, so I don't go around and say 'it
> works'. It may or may not work in your case.

Since I would want to make an AP that generally worked, I
don't think it would be enough.

> If possible, test and report back your findings.

I don't currently have a dongle. I'd be happy to buy one and
test it (I really don't mind going through a fair number of
patch/test/report back cycles, it's just writing code that's
not currently something I can do), but not if there's a
demarcation dispute as to who owns the bug!

--=20
J=C3=B3n Fairbairn                                 Jon.Fairbairn@cl.cam=
=2Eac.uk


--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-05-02 10:18 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-30 13:41 rt73usb Access point status Joerg Pommnitz
2009-04-30 13:55 ` Johannes Berg
2009-04-30 13:56 ` Luis Correia
2009-05-02 10:18   ` Jon Fairbairn [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
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

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=wfk54zu7t6.fsf@calligramme.charmers \
    --to=jon.fairbairn@cl.cam.ac.uk \
    --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;
as well as URLs for NNTP newsgroup(s).