Slax Ndiswrapper on a Ad-Hoc Network



This is just a basic set of instructions on how to use the ndiswrapper under Slax.
I'll show what I have to do, and I will explain each step after so you'll know why I did it and its function.
BOLD text is what I typed.
Italics is the bash's response.

ndiswrapper -i lsbcmnds.inf
Installing lsbcmnds *its likely you will also get alot of text from pearl b*tching about this and that, but don't worry.

Ok here I am loading my windows diver into the ndiswrapper. In this case its a linksys driver called lsbcmnds.
Your driver name will likely vary but you get the picture. Please note what you want to load is NOT the DLL but the .inf files.
modprobe ndiswrapper

The only time you should see extra text here is if there is an error. Here I'm loading the ndiswrapper itself, it will act as the windows
driver so you can use your card.

*Please note on some cards you have to type "ifconfig wlan0 up" here.(My linksys card didn't, but a Dlink I tested did)

iwconfig
lo........no wireless extensions.
.
wlan0.....IEEE 802.11G ESSID:off/any
..........Mode: Frequency:2.437Ghz Access Point:00:00:00:00:00:00
..........Bit Rate:54Mb/s Tx-Power:14 dBm
..........Rts thr:2347 B Fragment thr:2346 B
..........Encryption key:off
..........Link Quality:100/100 Signal level:-30 dBm Noise level:-256 dBm
..........Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
..........Tx excessive retries:0 Invalid misc:0 Missed beacon:0


First off if you only see the lo part then it failed, and you should go back and try again with a different driver. If wlan0 has a different number at the
end or is eth0 etc... don't worry its not a problem. As you can see the ESSID is set to "any/off" and the Mode option is empty. When it comes to Ad-hoc networks
these are really some of the key values. That is with the addition of one value that you normaly don't play with when you're in managed mode that is the channel value
When it comes down to it Ad-Hoc is actully pretty simple to setup, even compared to managed mode. Mostly because Ad-Hoc is not normaly used for internet access but
just for a quick moving network. Don't mistake this for saying you can't use it for the internet, because you can.

iwconfig wlan0 mode ad-hoc
This sets you into the ad-hoc(Peer to peer) network mode.

iwconfig wlan0 channel 6
Here I'm setting the channel. I just picked six out of thin air, but this is the channel managed mode normaly operates on as well. The channel range varies from 1-11
in the United States, and 1-13 in much of the rest of the world.

iwconfig wlan0 essid SlaxNET
Here I'm setting the ESSID to "SlaxNET", this is the name of the network itself. In other words its what people will see if they scan for networks. You can set the ESSID
to anything that pleases you. That is unless you are trying to join an already existing network then you should set it to thier name.

ifconfig wlan0 192.168.1.5 netmask 255.255.255.0
I'm setting my local network IP and netmask here. As far as picking an Ip and netmask goes you can do just about anything you want. I would stick to the 255.255.255.* on the
netmask just to play safe. For the IP I like the 192.168.*.* set myself, its normaly also fairly safe. Just be sure your IP is different from anyone elses on your network
and yout netmask is the SAME as everyone else on your network. At this point your Ad-hoc settup should be complete. If you're looking to connect to the internet with an Ad-Hoc
network just take a peak at one of my other guides and just follow the parts on setting up the internet connections.

ifconfig wlan0 up
Just do this to be sure everything takes effect.

Other Guides



Dhcp in Slax
Static IP in Slax