scotf
Group: Members
Posts: 7
Joined: Mar. 2005 |
 |
Posted: April 04 2005,02:32 |
 |
Hey Buf,
I think this is where you are, but of course I could be wrong. You run from the shell the command ndiswrapper -l and you get a response like
| Code Sample |
netwg311 hardware present
|
If that is so, run the iwconfig command with no arguments and you should see eth0, loopback and wlan0. If you don't see wlan0. Try the shell command | Code Sample | | modprobe ndiswrapper |
. Then try iwconfig (no args). If still no wlan0, things aren't working correctly and we have to go back and look at ndiswrapper.
Next use iwconfig to set the particulars of your WiFi network
| Code Sample |
iwconfig wlan0 essid BufHouse ( or whatever your SSID is)
iwconfig wlan0 key FFFFFFFFF ( whatever your network key is.
In this example I assume 64bit WEP so you enter a 10 digit hex key). In one instance, I had to set the channel using iwconfig channel x (mine happens to be 6). Simarly, one can specify the mac address of the access point. However, I've never seen the need to do so.
|
At this point, wlan0 may be up running if your network uses DHCP. To find out run ifconfig and see if wlan0 is listed and if so, does it have an address assigned? If it is listed but doesn't have an IP address assigned issue the shell command | Code Sample | | ifconfig wlan0 up |
. This should obtain (or renew) a lease with the DHCP server.
If you are using static IP's, I think the command after configuring with iwconfig is (you'll have to put in your particulars here)
| Code Sample |
ifconfig wlan0 xxx.xxx.xxx.xxx netmask 255.255.255.0 broadcast xxx.xxx.xxx.255
followed by
router add default gw xxx.xxx.xxx.xxx
you may also have to have specify your name servers. However, if you have had the PC connected using an ethernet cable, setting the addresses of one or more domain name servers should'nt be necessary.
|
Ahh, finally a number of the iw ... commands aren't supported when ndiswrapper is used. I have used iwlist succussfully with ndiswrapper. This will report a list of access points (that broadcast SSID) within the receiving radius of the network card.
Even if all goes well, the computer may hang. If so the network card drivers are exceeding the per-thread stack size limit set by DSL. In order to fix that, we need to rebuild the kernel with a larger stack size. I found some instructions on how to do so for Debian. On a fairly a new PC I installed Ubunto (another Debian derivative) this weekend along with some development tools. Hopefully next weekend I'll have time to rebuild a new kernel for DSL and test.
Best of luck and let me know how you make out!
Kind Regards
Scot
|
.
DSL Market ,
Great VPS hosting provided by Tektonic
