linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Juan Carlos Garza <juancarlosgarza@gmail.com>
To: Luis Correia <luis.f.correia@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: rt2800usb (rt2x00) in ad-hoc mode stalls when transferring large amount of data
Date: Fri, 11 Mar 2011 21:19:29 +0100	[thread overview]
Message-ID: <AANLkTimES4LLH9MT459RGc+2XUZ2csOLRnxWd4dws5mQ@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimfy87qCY7m-5YzBpqLTQKakf1zLMxCGNvotjO3@mail.gmail.com>

On Fri, Mar 11, 2011 at 9:08 PM, Luis Correia <luis.f.correia@gmail.com> wrote:
> Hi
>
> On Fri, Mar 11, 2011 at 20:04, Juan Carlos Garza
> <juancarlosgarza@gmail.com> wrote:
>> Hello
>>
>> I have a Ralink 3071 usb device (Bus 002 Device 003: ID 07b8:3071
>> D-Link Corp. 802.11n/b/g Mini Wireless LAN USB2.0 Adapter).
>> I am using the mac80211 driver by compiling the compat-wireless
>> tarball from yesterday (10 March). I cross compile it with the 2.6.24
>> kernel in a Montavista distribution (and also with 2.6.27 in Fedora)
>>
>> It works pretty good in AP mode using HostAPD and DCHP and I get
>> relative good transfer rates (up to 3.5 MBytes per second).
>>
>> My problems are with Ad-Hoc connections. I can configure the Ad-Hoc
>> connection, for example:
>>
>> iwconfig wlan0 mode ad-hoc
>> iwconfig wlan0 essid my_ad_hoc_nt
>> iwconfig wlan0 key 1122334455
>> ifconfig wlan0 192.168.111.44 up
>>
>> It works and I connect to it on the other end (a windows machine with
>> a compatible static ip address), however, it only works for doing
>> small data transfer rate things like browsing through the directories
>> of a shared folder or retrieving web pages from a web server. When I
>> try to do something like transferring a 500 MByte file, it starts
>> transferring, reaches a peak and then it drops to 0 again. After that,
>> the file is no longer transferred and I cannot do anything else (can't
>> ping).
>>
>> Is this a known issue? Any ideas?
>>
>> Juan Carlos
>> --
>> 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
>>
>
> keep in mind that current (and by design) ad-hoc connections max out at 11Mb.

Thanks for the comment,
Mhh, I've been benchmarking some other chipsets in ad-hoc mode (like
the rtl8188cus) and they do not present these problems (only a slow
transfer rate).

>
> there may be some buffer bottleneck involved.
>

I tried changing the MTU and other parameters, and nothing...

> but I'm not a very good expert on this subject.
>
>
> Luis Correia
>



-- 
________________________________
M.Sc. Juan Carlos Garza Fernández
Chistophstr. 14
70178 Stuttgart, Deutschland
+49 711 4080769
+49 176 21947676
juancarlosgarza@gmail.com
________________________________

      reply	other threads:[~2011-03-11 20:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-11 20:04 rt2800usb (rt2x00) in ad-hoc mode stalls when transferring large amount of data Juan Carlos Garza
2011-03-11 20:08 ` Luis Correia
2011-03-11 20:19   ` Juan Carlos Garza [this message]

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=AANLkTimES4LLH9MT459RGc+2XUZ2csOLRnxWd4dws5mQ@mail.gmail.com \
    --to=juancarlosgarza@gmail.com \
    --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).