From: Larry Finger <Larry.Finger@lwfinger.net>
To: David Ellingsworth <david@identd.dyndns.org>
Cc: bcm43xx-dev@lists.berlios.de, linux-wireless@vger.kernel.org
Subject: Re: b43legacy: local packet loss
Date: Sun, 06 Jul 2008 13:37:02 -0500 [thread overview]
Message-ID: <487110CE.3050304@lwfinger.net> (raw)
In-Reply-To: <30353c3d0807061106x78e796f4r95f2ce7e56a4bb5c@mail.gmail.com>
David Ellingsworth wrote:
> While using the latest b43legacy driver, I have severe packet loss
> originating from the machine using the b43legacy driver. However, when
> packets are routed through the machine using NAT, no packet loss
> occurs. Ping results are as follows:
>
> using 'ping -c 100 192.168.1.1'
>
>>From local machine (192.168.1.100) to wireless router (192.168.1.1)
> 43% packet loss, average rtt 13.987ms
>
>>From nat machine(192.168.2.100) to wireless router (192.168.1.1) via
> b43legacy router(eth0:192.168.2.1, wlan0:192.168.1.100)
> 0% packet loss, average rtt 3.621ms
>
> The only logical conclusion I can draw from the above information is
> that there is something wrong with how packets are created locally and
> delivered to the device. I'm willing to provide any help necessary
> needed to correct the issue.
More information please.
1. Is your "latest b43legacy" from wireless-testing, 2.6.26-rc9, or what?
2. What BCM43xx card are you using?
3. What wireless router are you using?
Using the wireless-testing git tree with a BCM4306/2 and working with a Linksys
WRT54GL router with standard firmware, my statistics for the ping -c 100
192.168.1.1 command are 0% packet loss with average rtt of 2.919 ms.
Larry
next prev parent reply other threads:[~2008-07-06 18:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-06 18:06 b43legacy: local packet loss David Ellingsworth
2008-07-06 18:37 ` Larry Finger [this message]
2008-07-06 19:42 ` David Ellingsworth
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=487110CE.3050304@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=david@identd.dyndns.org \
--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