SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you using X at all? ie, KDE or XFCE, etc., or are you cli only?
The reason I ask is that it *may* be simpler (as in: more intuitive) vs the cli for a newbie. If you are running X, you may want to consider using either networkmanager or wicd to get your wireless up and running.
Either way, welcome to Slackware in particular, and Linux in general. The folks here are extremely helpful, knowledgeable, and most importantly, very patient. So come on aboard.
true the gui is more intuitive but without knowing which distro version / desktop environment / window manager / network manager utility / ... its hard to give instruction (i am also, assuming they tried the obvious like selecting their wifi router from the dropdown menu but it didnt work).
if you would like to read ahead in the curriculum, you can try these commands to connect via the command line:
sudo iwlist <network-card> scan # this will use the <network-card> interface (that from the iwconfig command above) and scan for wireless routers that are accessible.
sudo iwconfig <network-card> essid <your-router-name> # assuming no security (the access point names will be provided by the previous iwlist command).
sudo dhclient # will attempt to get ip-address, subnet mask, dns server information automatically from your router assuming dhcp is turned on on your router.
However, "sudo" has to be configured in Slackware in order to prevent the careless (as in "freely using what are often root privileges") use of root permissions.
As per your output, wlan0 appears to be up and running, however, issue the ifconfig wlan0 cmd provided by shneidz, then:
iwlist wlan0 scan
the output should show access points within range.
As pointed out earlier, it's at this point that the cli requires specific input in order to connect. Once the output of iwlist is considered, this additional input can be added to ifconfig, iwconfig, etc.
If you follow the link provided by shneizd, you'll find his posts with the proper cli method for connecting (just drop to root unless you've got sudo configured.)
The initial complexity of connecting via cli is why it's been suggested to connect using X, initially, then once it's confirmed to work, the cli can be explored more easily, and further.
In either case, more info is necessary, and the more info, the better. so please continue along either or both paths.
Using wicd/networkmanager, you've indicated that it shows wlan0, but nothing else. Normally the wicd window should show a list of available ap's...is the "scan" button alive? (as in not greyed-out)