Thread View: alt.os.linux.suse
10 messages
10 total messages
Started by Gregory Toomey
Mon, 26 Jul 2004 07:02
HOWTO: Adding cheap wifi to your linux box
Author: Gregory Toomey
Date: Mon, 26 Jul 2004 07:02
Date: Mon, 26 Jul 2004 07:02
101 lines
5309 bytes
5309 bytes
Summary: This is a brief howto on adding wifi to a laptop or desktop using a cheap, common 802.11b device.
For SuSE 9.1 its just about all done for you; other distributions may need to do more work.
This Howto
- is for the most common wifi devices, which use the Prism2 chipset
- compatible devices are listed here
http://www.linux-wlan.org/docs/wlan_adapters.html.gz
- is tested with Netgear MA111; this is a usb device with a usb extension cable; can be easily connected to a laptop or dessktop;
I bought one at www.thediscshop.com.au last week for $A77
http://www.netgear.com.au/products/prod_details.asp?prodID=173&view=
- is for connecting from linux TO an access point using a static IP
This howto is NOT
- for 802.11g devices (different driver)
- for peer-peer connections, or using the device AS an access point
- for dhcp (though it should be easy to do)
- for operating in promiscuous mode
GotCha:
- iwconfig can be used to show the device status
- to configure the device you need the wlanctl-ng command
- wlanctl-ng is documented at http://www.linux-wlan.org/
SuSE 9.1
- its trivial; all has been done for you in the default install. wlanctl-ng is available as root. Just connect the device and run script 1 or script 2.
- for other distributions you may need to install a package to get wlanctl-ng; I recommend a 2.6 kernel as it has better wifi support
SCRIPT 1 - simple wifi ( no encryption)
You will need: an access point, ssid for the access point, a linux box, a prism2 wifi device connected to the linux box; root access.
In this script I set up tbe prism2 device connect to an access point. Set up the access point to the same ssid as the script.
#!/bin/bash
linux:~/bin # ifconfig
modprobe prism2_usb prism2_doreset=1
wlanctl-ng wlan0 lnxreq_ifstate ifstate=enable
wlanctl-ng wlan0 lnxreq_autojoin ssid=gmtnet authtype=opensystem
# set up my IP
ifconfig wlan0 192.168.2.6
If all is well ifconfig & iwconfig should show the device:
linux:~/bin # ifconfig
wlan0 Link encap:Ethernet HWaddr 00:09:5B:91:E9:69
inet addr:192.168.2.3 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::209:5bff:fe91:e969/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:24495 errors:0 dropped:0 overruns:0 frame:0
TX packets:26005 errors:0 dropped:4 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:13410263 (12.7 Mb) TX bytes:2572436 (2.4 Mb)
linux:~/bin # iwconfig
wlan0 IEEE 802.11-b ESSID:"gmtnet" Nickname:"gmtnet"
Mode:Managed Frequency:2.412GHz Access Point: 00:50:FC:D6:7B:A8
Bit Rate:11Mb/s Tx-Power:2346 dBm
Retry min limit:8 RTS thr:off Fragment thr:off
Encryption key:off
Link Quality:50/92 Signal level:-60 dBm Noise level:-97 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
(here signal quality=60/92=54%)
PROBLEM:
If you ping the access point from linux and get "network unreachable", or
"Tx attempt prior to association, frame dropped" in the system log, the most likely cause is the ssid in the script does not match the access point.
See ftp://ftp.linux-wlan.org/pub/linux-wlan-ng/FAQ for this and other common problems
SCRIPT 2 - wifi access with encryption
Same as script 1 but with WEP encryption. The ssid and WEP key of the access point must be the same as the script.
Get a random WEP key here:
https://www.wireless.org.au/~jhecker/wepgen/index.php
#!/bin/bash
ssid=gmtnet
wep="E2:74:5D:35:00"
modprobe prism2_usb prism2_doreset=1
wlanctl-ng wlan0 lnxreq_ifstate ifstate=enable
wlanctl-ng wlan0 lnxreq_hostwep decrypt=true encrypt=true
wlanctl-ng wlan0 dot11req_mibset mibattribute=dot11WEPDefaultKeyID=0
wlanctl-ng wlan0 dot11req_mibset mibattribute=dot11ExcludeUnencrypted=true
wlanctl-ng wlan0 dot11req_mibset mibattribute=dot11PrivacyInvoked=true
wlanctl-ng wlan0 dot11req_mibset mibattribute=dot11WEPDefaultKey0=$wep
wlanctl-ng wlan0 lnxreq_autojoin ssid=$ssid authtype="sharedkey"
# set up my IP
ifconfig wlan0 192.168.2.3 netmask 255.255.255.0
route add default gw 192.168.2.20
More Reading:
prism2 driver: http://linux-wlan.org/
http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Linux.Wireless.drivers.802.11b.html
gtoomey
Re: HOWTO: Adding cheap wifi to your linux box
Author: W
Date: Mon, 26 Jul 2004 07:32
Date: Mon, 26 Jul 2004 07:32
2 lines
1094 bytes
1094 bytes
There is an article in the August edition of APC on setting up WiFi under Linux.
Re: HOWTO: Adding cheap wifi to your linux box
Author: James Knott
Date: Mon, 26 Jul 2004 11:53
Date: Mon, 26 Jul 2004 11:53
10 lines
1329 bytes
1329 bytes
W wrote: > There is an article in the August edition of APC on setting up WiFi under > Linux. What's APC? -- (This space intentionally left blank)
Re: HOWTO: Adding cheap wifi to your linux box
Author: Paulo Rocha
Date: Mon, 26 Jul 2004 23:08
Date: Mon, 26 Jul 2004 23:08
11 lines
1233 bytes
1233 bytes
Gregory Toomey wrote: > SuSE 9.1 > - its trivial; all has been done for you in the default install. It's even more trivial no go to YaST2 and configure the wireless network connection there... Why do people tend to teach Linux the hard way? Paulo Rocha
Re: HOWTO: Adding cheap wifi to your linux box
Author: Gregory Toomey
Date: Tue, 27 Jul 2004 00:17
Date: Tue, 27 Jul 2004 00:17
17 lines
1310 bytes
1310 bytes
Paulo Rocha wrote: > Gregory Toomey wrote: > >> SuSE 9.1 >> - its trivial; all has been done for you in the default install. > > It's even more trivial no go to YaST2 and configure the wireless network > connection there... > Why do people tend to teach Linux the hard way? > > > Paulo Rocha With a prism2 driver? They dont use iwconfig for configuration. gtoomey
Re: HOWTO: Adding cheap wifi to your linux box
Author: Paulo Rocha
Date: Tue, 27 Jul 2004 00:19
Date: Tue, 27 Jul 2004 00:19
11 lines
1407 bytes
1407 bytes
Gregory Toomey wrote: > SuSE 9.1 > - its trivial; all has been done for you in the default install. It's even more trivial to go to YaST2 and configure the wireless network connection there... Why do people tend to teach Linux the hard way? Paulo Rocha
Re: HOWTO: Adding cheap wifi to your linux box
Author: James Knott
Date: Tue, 27 Jul 2004 01:57
Date: Tue, 27 Jul 2004 01:57
25 lines
1772 bytes
1772 bytes
Gregory Toomey wrote: > Paulo Rocha wrote: > >> Gregory Toomey wrote: >> >>> SuSE 9.1 >>> - its trivial; all has been done for you in the default install. >> >> It's even more trivial no go to YaST2 and configure the wireless network >> connection there... >> Why do people tend to teach Linux the hard way? >> >> >> Paulo Rocha > > With a prism2 driver? They dont use iwconfig for configuration. > > gtoomey My ThinkPad WiFi uses a Prism 2.5 Wavelan chipset. Yast works fine with it. -- (This space intentionally left blank)
Re: HOWTO: Adding cheap wifi to your linux box
Author: houghi
Date: Tue, 27 Jul 2004 17:28
Date: Tue, 27 Jul 2004 17:28
44 lines
2443 bytes
2443 bytes
["Followup-To:" header set to alt.os.linux.suse.] The Etobian wrote: > On Tue, 27 Jul 2004 01:19:47 +0100, Paulo Rocha ><paulorocha@megamail.pt> wrote: > >>Gregory Toomey wrote: >> >>> SuSE 9.1 >>> - its trivial; all has been done for you in the default install. >> >>It's even more trivial to go to YaST2 and configure the wireless network >>connection there... >>Why do people tend to teach Linux the hard way? > > Because they may have already purchased an incompatible wifi nic, and > either need to do it the hard way to make it work, or use another > card. That would naturlly be stated if that was the case, otherswise it would go like this: >>>>>>>>>> How do you install wifi >>>>>>>>> with Yast >>>>>>>> I tried that >>>>>>> What did happen >>>>>> It did not work >>>>>Dit it gave an error? >>>>Yes >>>>Wich one? >>>It is not supported. >>What card do you have? >A XXYYZZ. OK. Then try this .... Instead of what should then happen: > I tried installing my XXYYZZ card with Yast and it told me it was not > supported. I have no idea how to proceed. Ok. Then try this .... -- http://www.houghi.org | | _) \ \ \ /\ \ \ /\ \ \ / \ _ \ | | _` | \ | _ \ _|_` | \_/\_/ \_/\_/ \_/\_/_)_| _|\___/\_,_|\__, |_| _|_|_)\___/_|\__, | My experience with SUSE. ____/ ____/
Re: HOWTO: Adding cheap wifi to your linux box
Author: Dazz
Date: Wed, 28 Jul 2004 04:34
Date: Wed, 28 Jul 2004 04:34
22 lines
1577 bytes
1577 bytes
On Tue, 27 Jul 2004 02:20:11 GMT, The Etobian <pdcorc@excite.com> wrote: <snipped> >Because they may have already purchased an incompatible wifi nic, and >either need to do it the hard way to make it work, or use another >card. For me, I couldn't get my Linksys 54G card to work in Linux at >all, but with the help of ndiswrapper, the Belkin 802.11b card I got >for 10 bucks after rebate worked. I could have got a card >specifically supported in linux, but 10 bucks was cheap enough to be >worth the risk. As a matter of interest, which Belkin PCI card did you use? I'm using a Belkin USB Wireless setup atm, but want a dedicated PCI card for another of my boxes. Cheers, Dazz <snipped>
Re: HOWTO: Adding cheap wifi to your linux box
Author: Dazz
Date: Thu, 29 Jul 2004 04:55
Date: Thu, 29 Jul 2004 04:55
21 lines
1603 bytes
1603 bytes
On Wed, 28 Jul 2004 23:18:27 GMT, The Etobian <pdcorc@excite.com> wrote: <snipped> >The F5D6001, with the ADMtek chipset. There are three versions of >this card, the first with the PRISM2 chipset,, the second with the >ADMtek chipset, and the third has the RealTek chipset. > >My only complaint is that Belkin didn't revise the model number when >changing chipsets. That's one of my concerns as well. I found a Belkin card for $29.95, however, the packaging doesn't reveal any specs about the chipset. I'm pretty sure the store has a pretty good return policy, so I'll ask a few questions tonight. Thanks for the info. Dazz
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads