From: Larry Finger <Larry.Finger@lwfinger.net>
To: alupu@verizon.net
Cc: linux-wireless@vger.kernel.org
Subject: Re: r8712u staging in kernel 3.2.9
Date: Tue, 06 Mar 2012 21:22:49 -0600 [thread overview]
Message-ID: <4F56D489.9060207@lwfinger.net> (raw)
In-Reply-To: <31991817.2926129.1331079358141.JavaMail.root@vznit170116>
[-- Attachment #1: Type: text/plain, Size: 564 bytes --]
Here are the details for my system, which is 64-bit. I'm running kernel 3.3-rc5
with wireless-tools version 30. Apparently my kernel has V22 - that seems
surprising.
If I use 'iwconfig wlanX essid blah-blah' followed by 'iwconfig wlanX key
restricted xxxxxxxxxxxxxx', then it does not work, but it does when I combine
the essid and key on a single line.
What would be the ifconfig command to start the interface with DHCP? In my
distro, we have an ifup command that reads a configuration file. That script is
too complicated to see what it does.
Larry
[-- Attachment #2: r8712u_config --]
[-- Type: text/plain, Size: 4073 bytes --]
finger@linux-gskd:~/wireless-testing> ls -ogtr /usr/sbin | grep iw
-rwxr-xr-x 1 98504 Oct 29 12:57 iw
-rwxr-xr-x 1 14712 Oct 29 13:09 iwspy
-rwxr-xr-x 1 14760 Oct 29 13:09 iwpriv
-rwxr-xr-x 1 35504 Oct 29 13:09 iwlist
-rwxr-xr-x 1 14680 Oct 29 13:09 iwgetid
-rwxr-xr-x 1 18960 Oct 29 13:09 iwevent
-rwxr-xr-x 1 27160 Oct 29 13:09 iwconfig
finger@linux-gskd:~/wireless-testing> iwconfig --version
iwconfig Wireless-Tools version 30
Compatible with Wireless Extension v11 to v22.
Kernel Currently compiled with Wireless Extension v22.
wlan4 Recommend Wireless Extension v16 or later,
Currently compiled with Wireless Extension v22.
finger@linux-gskd:~/wireless-testing> uname -r
3.3.0-rc6-wl+
finger@linux-gskd:~/wireless-testing> iwconfig wlan4
wlan4 unassociated Nickname:"rtl_wifi"
Mode:Managed Access Point: Not-Associated Sensitivity:0/0
Retry:off RTS thr:off Fragment thr:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
finger@linux-gskd:~/wireless-testing> ifconfig
eth0 Link encap:Ethernet HWaddr 40:61:86:FC:43:BA
inet addr:192.168.3.101 Bcast:192.168.3.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:101 errors:0 dropped:0 overruns:0 frame:0
TX packets:117 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:60068 (58.6 Kb) TX bytes:14665 (14.3 Kb)
Interrupt:43 Base address:0xa000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:56 errors:0 dropped:0 overruns:0 frame:0
TX packets:56 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2880 (2.8 Kb) TX bytes:2880 (2.8 Kb)
finger@linux-gskd:~/wireless-testing> sudo iwconfig wlan4 essid radius key restricted 1234f0033edaebf3f7dab4ceca
finger@linux-gskd:~/wireless-testing> sudo iwconfig wlan4
wlan4 IEEE 802.11bg ESSID:"radius" Nickname:"rtl_wifi"
Mode:Managed Frequency:2.412 GHz Access Point: 00:14:BF:85:49:FA
Bit Rate:54 Mb/s Sensitivity:0/0
Retry:off RTS thr:off Fragment thr:off
Encryption key:1234-F003-3EDA-EBF3-F7DA-B4CE-CA Security mode:restricted
Power Management:off
Link Quality=100/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
finger@linux-gskd:~/wireless-testing> sudo ifconfig wlan4 up
finger@linux-gskd:~/wireless-testing> ifconfig
eth0 Link encap:Ethernet HWaddr 40:61:86:FC:43:BA
inet addr:192.168.3.101 Bcast:192.168.3.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:102 errors:0 dropped:0 overruns:0 frame:0
TX packets:117 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:60128 (58.7 Kb) TX bytes:14665 (14.3 Kb)
Interrupt:43 Base address:0xa000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:56 errors:0 dropped:0 overruns:0 frame:0
TX packets:56 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2880 (2.8 Kb) TX bytes:2880 (2.8 Kb)
wlan4 Link encap:Ethernet HWaddr 00:26:5A:BF:41:E4
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:37 errors:0 dropped:8 overruns:0 frame:0
TX packets:27 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:12007 (11.7 Kb) TX bytes:6195 (6.0 Kb)
next parent reply other threads:[~2012-03-07 3:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <31991817.2926129.1331079358141.JavaMail.root@vznit170116>
2012-03-07 3:22 ` Larry Finger [this message]
2012-03-13 4:13 r8712u staging in kernel 3.2.9 alupu
-- strict thread matches above, loose matches on Subject: below --
2012-03-12 23:02 alupu
2012-03-13 0:54 ` Larry Finger
2012-03-12 1:46 alupu
2012-03-12 2:54 ` Larry Finger
2012-03-11 22:36 alupu
2012-03-12 0:19 ` Larry Finger
2012-03-11 19:57 alupu
2012-03-11 19:57 alupu
2012-03-10 18:10 alupu
2012-03-11 4:23 ` Larry Finger
2012-03-10 4:53 alupu
2012-03-09 19:06 alupu
2012-03-10 2:17 ` Larry Finger
2012-03-07 5:31 alupu
2012-03-07 16:15 ` Larry Finger
2012-03-07 1:44 alupu
2012-03-06 2:22 alupu
2012-03-06 20:21 ` Larry Finger
2012-03-05 17:07 alupu
2012-03-05 19:10 ` Larry Finger
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=4F56D489.9060207@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=alupu@verizon.net \
--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).