linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Ben Ruijl <benruyl@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: r8712u: packet loss
Date: Sun, 06 Mar 2011 11:31:24 -0600	[thread overview]
Message-ID: <4D73C4EC.7090702@lwfinger.net> (raw)
In-Reply-To: <AANLkTikmFj5EDaa3sY6d05XRCKwBWywtMaekmK1hCHPX@mail.gmail.com>

On 03/06/2011 03:52 AM, Ben Ruijl wrote:
> Hi Larry,
>
> The iwconfig I sent you is wrong, because I switched routers. The
> router I had was a wireless N router, with which I had 12 percent
> packet loss. The iwconfig you are seeing is with a wireless G
> connection and now I only have 1 percent packet loss: the same as you
> have. It appears that the relative packet loss is greater with an N
> connection.

I have no idea why the loss should be greater with the N router than with the G 
router.

How is the 2.4 GHz part of the N router configured? What make/model is it, and 
what firmware is it running? Do you have the latest version?

My N router is a Netgear WNDR3300 normally running up to 270 Mbps at 5 GHz and 
54 Mbps at 2.4 GHz; however, I changed it to run up to 270 Mbps in the 2.4 GHz 
band. Again, I get 1% ping loss. My iwconfig output is

wlan12    IEEE 802.11bgn  ESSID:"lwfdjf-n"  Nickname:"rtl_wifi"
           Mode:Managed  Frequency:2.422 GHz  Access Point: C0:3F:0E:BE:2B:44
           Bit Rate:270 Mb/s   Sensitivity:0/0
           Retry:off   RTS thr:off   Fragment thr:off
           Power Management:off
           Link Quality=97/100  Signal level=100/100  Noise level=0/100
           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
           Tx excessive retries:0  Invalid misc:0   Missed beacon:0


That link gets an upload speed measured with tcpperf of more than 80 Mbps.

I do not know why your N link is so lossy. The possible reasons are outdated 
firmware in the router that was established in the pre-N days, or you have 
noise/interference that affects the HT setup more than a simple G configuration.

Larry

      reply	other threads:[~2011-03-06 17:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTi=-KJ+OSvDGuxYvDYQZ2ZdS8G8obbvodOXd9zQD@mail.gmail.com>
     [not found] ` <AANLkTimTecR-W7iGzRWB_DxNVJoovK5SCuWfCmt8SUJo@mail.gmail.com>
2011-02-15 12:58   ` r8712u: packet loss Ben Ruijl
2011-02-15 16:40     ` Larry Finger
2011-02-15 17:20       ` Ben Ruijl
2011-02-15 18:04         ` Larry Finger
2011-02-18 15:02           ` Ben Ruijl
2011-03-06  9:52             ` Ben Ruijl
2011-03-06 17:31               ` Larry Finger [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=4D73C4EC.7090702@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=benruyl@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;
as well as URLs for NNTP newsgroup(s).