Quote:
or at least can you tell me step by step how to configure it,
|
This is really no biggie. The first thing you have to do is configure your card. You use the
iwconfig command to do this. You set the SSID of your access point and the WEP key if you use one:
iwconfig wlan0 mode Managed (you may also want to try Auto)
iwconfig wlan0 key HEX_WEP_KEY_HERE (or see the iwconfig man page for how to enter an ascii key)
iwconfig wlan0 essid Your_AP_SSID
If that has worked, when you run iwconfig alone you should see that wlan0 has recongnized your access point.
The next step is to get an IP address. The easy way is using DHCP if your router is set up to be a DHCP server:
dhclient wlan0
The harder way, if DHCP is causing trouble, is to do it by hand:
ifconfig wlan0 1.2.3.4 (only replace that with the IP address you want the card to use)
route add default gw 5.6.7.8 (replace 5.6.7.8 with the IP address of your router)
Then edit your /etc/resolv.conf and for each nameserver your ISP has (you can usually get this info from your router) you add a line like this:
nameserver 1.2.3.4 (only use the proper IP address for the DNS)
Quote:
linksys ACX 111 this is strange because that is not the card that I have installed,
|
Believe it or not, this might be a good thing. One of the more evil things Linksys does is to change the chipsets inside its cards, but not the model number. So the WPC54G you have may not have the same chipset as another WPC54G. I think what this is telling you is that your card uses the Texas Instruments ACX111 chipset. The reason that this is a good thing is that TI is one of the good guys and they release info about their chipsets, so there is a
native linux driver for this card. My guess is that Suse has this driver available and Yast is trying to use it. If I were in your shoes, I would stop mucking around with ndiswrapper and give this a go.