From: Stefan Zwanenburg <stefanhetzwaantje@gmail.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: 'Chaoming_Li' <chaoming_li@realsil.com.cn>,
linux-wireless@vger.kernel.org
Subject: Re: 答复: 答复: 答复: RTL8192SE and 802.11n problem
Date: Wed, 28 Sep 2011 00:25:57 +0200 [thread overview]
Message-ID: <4E824D75.1070509@gmail.com> (raw)
In-Reply-To: <4E823976.2090407@lwfinger.net>
On 09/27/2011 11:00 PM, Larry Finger wrote:
> I have to go now, but if no one describes what we are seeing, I'll
> review the 802.11n specs and get back to you tomorrow.
>
> Larry
I've taken a quick peek at the specs, and I'm afraid I can't be of any
help there (I found out — again — I have great respect for you guys for
reading those documents!). However, something just dawned on me, and I'm
not sure if it is at all relevant here, but somehow, my NIC seems to be
getting all kinds of different MAC addresses assigned (apparently
randomly). I just checked my "persistent net" udev rules file (mind you,
this file is automatically amended whenever a new NIC appears on my
system), and there are 26(!) different rules for just my wireless
interface, all with different MAC addresses.
As you may have noticed from my dump of the association process, the MAC
address in use is one with a vendor ID for some "Azurewave" interface.
There are quite a few in the rules file for Realtek interfaces, but the
one I mostly get is for an Azurewave vendor ID.
I just tried setting a different MAC address (using ifconfig wlan0 hw
ether 00:e0:4c:81:82:58) however it didn't change anything about my no
802.11n link situation (as I expected). So perhaps this little tidbit
should be ignored for now.
I just thought I'd let you know, in case this isn't a known problem.
Regards,
Stefan Zwanenburg
next prev parent reply other threads:[~2011-09-27 22:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4E77AECF.7090001@gmail.com>
[not found] ` <4E820130.7080801@gmail.com>
2011-09-27 21:00 ` 答复: 答复: 答复: RTL8192SE and 802.11n problem Larry Finger
2011-09-27 22:25 ` Stefan Zwanenburg [this message]
2011-09-28 4:56 ` Larry Finger
2011-09-28 23:28 ` Stefan Zwanenburg
2011-09-29 2:32 ` Stefan Zwanenburg
2011-09-29 3:28 ` Larry Finger
[not found] ` <0EF5E594196F41B48B0B4D168B714838@realsil.com.cn>
2011-09-29 23:15 ` 答复: " Stefan Zwanenburg
2011-09-29 23:58 ` Stefan Zwanenburg
[not found] <4E67CE3F.8090405@gmail.com>
[not found] ` <4E67CEA3.7020709@gmail.com>
2011-09-08 2:23 ` Larry Finger
2011-09-08 2:50 ` Larry Finger
2011-09-08 3:23 ` Stefan Zwanenburg
2011-09-08 3:42 ` Larry Finger
[not found] ` <8117B559D4E64A83837479A8C342A5CA@realsil.com.cn>
[not found] ` <4E6E537D.5060404@gmail.com>
[not found] ` <24C6797004D84406B7564679CAE21531@realsil.com.cn>
[not found] ` <4E74946A.3080206@gmail.com>
[not found] ` <1903155944F64F00AC0C401593C20923@realsil.com.cn>
2011-09-19 20:04 ` 答复: 答复: 答复: " Stefan Zwanenburg
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=4E824D75.1070509@gmail.com \
--to=stefanhetzwaantje@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=chaoming_li@realsil.com.cn \
--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).