linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexandre Becholey <alexandre@shockfish.com>
To: linux-wireless@vger.kernel.org
Cc: Ivo van Doorn <ivdoorn@gmail.com>,
	Jon Fairbairn <jon.fairbairn@cl.cam.ac.uk>
Subject: Re: rt73usb Access point status
Date: Mon, 18 May 2009 13:12:37 +0200	[thread overview]
Message-ID: <4A1142A5.2090800@shockfish.com> (raw)
In-Reply-To: <200905161132.21437.IvDoorn@gmail.com>

Ivo van Doorn wrote:
> On Saturday 16 May 2009, Jon Fairbairn wrote:
>   
>> "Christoph .J Thompson" <cjsthompson@gmail.com> writes:
>>
>>     
>>> On Tue, 12 May 2009 09:16:12 +0100
>>> Jon Fairbairn <jon.fairbairn@cl.cam.ac.uk> wrote:
>>>       
>>>> Is there any prospec of persuading Ralink either to release
>>>> a mended version of the firmware or to free the old version?
>>>>         
>>> I think Ivo van Doorn said he didn't want to bother RaLink with that. I was
>>> thinking about writing to them about it but that's difficult because I don't
>>> really understand the technical specifics of the issue.
>>>       
>> Me neither; in particular, does it work as an AP in Windows?
>> If so, how does it get round the bug in the driver?
>>     
>
> Simply by indicating that every single frame passed to the driver has
> been send out succesfully and thus completely ignoring the real status.
>
> I am awaiting a patch from Alexandre which will add that same behavior
> to rt2x00.
>
> Ivo
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>   
Ok, I'll sent it soon.

I was trying to figure out the problem with the ARP packets when the 
wireless interface is bridged with an ethernet. It seems to be a known 
issue:
https://lists.linux-foundation.org/pipermail/bridge/2009-May/006382.html
http://www.linuxfoundation.org/en/Net:Bridge#It_doesn.27t_work_with_my_Wireless_card.21 
(kinda old... last modification from 2007)

Alexandre

  parent reply	other threads:[~2009-05-18 11:12 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
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 [this message]
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=4A1142A5.2090800@shockfish.com \
    --to=alexandre@shockfish.com \
    --cc=ivdoorn@gmail.com \
    --cc=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).