Slackware 12.2 internet connection via WiFi problems
Hi guys.
Can somebody, please, help me? I'm trying to set up the internet connection from this distro for a week without any results. Network: my host is connected to the router via WiFi, router is connected to a DSL modem from ISP. From Ubuntu 8.10 Live(where connection works and is set up automatically) I get the values of my host IP, gateway IP, DNS IP. They all have the same values 192.168.0.1. I set them in Slackware 12.2 either by using netconfig or manually by editing "rc.inet1.conf" and "resolv.conf". Still I have no connection. Firefox says "unknown host", ping says nothing. I also tried to use DHCP by dhcpcd wlan0, but it just does broadcasting without any results. My WLAN card is Intel WiFi Link 5100. I can see from the lspci in Sackware. I get connected to the wireless network by using kWiFiNetwork. To be sure I use iwconfig in Slackware and see that I'm really connected since it shows me the access point, signal strength, network name etc. Slackware 12.2 uses the same 2.6.27 kernel as Ubuntu 8.10(where I can use internet), so I guess the hardware part and drivers work. Please help. |
Don't you need an encryption key (WEP or WPA) ?
- if that is the case, you should edit your /etc/rc.d/rc.inet1.conf accordingly (and /etc/wpa_supplicant if it's WPA) - otherwise try as root: dhcpcd <your_wireless_interface_name> I make the assumption that you have a dhpc server -- if not the dhcpcd command is not relevant, of course. And please send the outputs of "ifconfig -a", "iwconfig" and "iwlist scan" (in the latter case, only the relevant cell(s) if there are many). [EDIT] If not already done I suggest you read this article from AlienBob: http://alien.slackbook.org/dokuwiki/...ckware:network |
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
|
Thus, as long as you stay at reachable distance from "jonas 101":
- Edit your /etc/rc.d/rc.inet1.conf so it includes: USEDHCP[4]="yes" (just uncomment that line, IFNAME[4] will do) IFNAME[4]="wlan0" (idem) WLAN_WPA[4]="wpa_supplicant" (idem) WLAN_ESSID[4]="jonas 101" (This is your essid, I guess. Uncomment that line too) - As you need WPA, edit your /etc/wpa_supplicant.conf so it includes: ssid="jonas 101" proto=WPA key_mgmt=WPA-PSK pairwise=CCMP TKIP group=CCMP TKIP WEP104 WEP40 psk="Your_WPA_Key_Here" For more info, see the file : /usr/doc/wpa_supplicant-0.5.10/wpa_supplicant.conf.sample Now, make sure following files be both executables (or chmod +x <file_name>) : /etc/rc.d/rc.inet1 /etc/rc.d/rc.wireless Now reboot : you should get the wireless connection at boot time. PS1: Don't use kwifimanager, it is useless with Slackware PS2: Don't bother yourself with /etc/rc.d/rc.wireless.conf : you don't need to edit anything in it. |
Hi,m
You should look at 'Configuring your network in Slackware'. This link and others are available from 'Slackware-Links'. More than just SlackwareŽ links! |
Still doesn't work. I'v done all you've said. While loading OS it writes(that error was before also): error for wireless request "SET Nickname" Set failed on device wlan0. Operation not supported. Then it stops, like doing something(writes nothing). Then suddenly the same scenario: broadcasting DHCP_DISCOVER. Then "timeout while ...". Then proceed loading the OS.
|
Slackware wireless connection problem
Quote:
|
I went through the same thing a couple days ago and finally got it to work. Didn't take many changes to do it, but figuring out the changes was tricky.
In /etc/wpa_supplicant.conf I did this: ssid="YOURACCESSPOINT" psk=5k5k39c9dfk4... (whatever your key is) In /etc/rc.d/rc.inet1.conf I did this to the wlan0 section: IFNAME[4]="wlan0" USE_DHCP[4]="yes" WLAN_ESSID[4]=YOURACCESSPOINT WLAN_WPA[4]="wpa_supplicant" WLAN_WPADRIVER[4]='wext" Then /etc/rc.d/rc.inet1 restart You can get that long hex key and store it in a file named key by doing this: wpa_passphrase YOURACCESSPOINT password > key This is all it took. I left everything else in those two files intact. Good luck. |
I'm having the exact same problem. I set up Slackware 12.2 yesterday, everything looks like it's working fine except the wireless internet. If I plug the ethernet cable in, it works just fine, but as soon as I unplug it, it stops. (that implies that I go into Network settings to enable/disable wireless/wired) I set up my wireless with KwifiManager with the hex password and everything, but still not working. But the thing is, I do connect to the network, since I can go in the router options... I just can't get to the internet... I even get an IP... I tried it with two differents network, mine and my friend's... So I don't know what to do I tried to modify the two files in /etc but nothing else happens... I really don't know what to do. It's my first wireless experience with linux.
|
Hi,
You should look at 'Configuring your network in Slackware'. What files did you modify in '/etc'? You should make your system changes from the 'cli' instead of your desktop. If you make changes system wide as root then you can restart the 'inet' from the 'cli' by; '/etc/rc.d/rc.inet1 restart'. This link and others are available from 'Slackware-Links'. More than just SlackwareŽ links! |
As you are using 12.2, I recommand you try wicd in testing/. It can automatically probe wireless network as well as wired ones. Remember to edit /etc/rc.d/rc.inet1.conf according to http://ftp.linux.cz/pub/linux/slackw...ADME.SLACKWARE . This small tool can help you a lot. ;)
|
Here are the files. With this configuration it does the following. On executing rc.inet1 during boot it gets stuck for a minute then writes "broadcasting DHCP_DISCOVER", then after some time it writes "timeout while waiting for valid DHCP response". Still no connection...
rc.inet1.conf Code:
# /etc/rc.d/rc.inet1.conf wpa_supplicant.conf Code:
# See /usr/doc/wpa_supplicant-0.5.10/wpa_supplicant.conf.sample rc.wireless.conf Code:
# Wireless LAN adapter configuration |
I didn't touch rc.wireless.conf to get mine to work.
Try uncommenting out this in rc.inet1.conf. WLAN_WPADRIVER[4]="wext" I showed exactly what I did to get mine to work and it worked on two different machines, including the one I'm posting from. |
Zero result.
PS. I also didn't touch that file. I posted it to show its contents. |
But first make sure /etc/rc.d/rc.wireless is executable:
Code:
bash-3.1$ ls -l /etc/rc.d/rc.wireless In that case make it executable in typing (as root): chmod +x /etc/rc.d/rc.wireless and then try again: /etc/rc.d/rc.inet1 restart If you don't succeed, try commenting these lines in wpa_supplicant.conf: Code:
network={ |
Aahhhh.... Ich kann das nicht glauben!!!
After a week of suffer I'm in the internet from my Slackware 12.2. I really don't know what was the problem. The file was executable and I've also tried to comment that stuff. It didn't help... But now I've been experimenting with setting the route and the gateway manually after what I've used dhcpcd. It's unbelivable but I got response and now I'm here. So, I guess I'll have to analyse what I've done in the command line. Aha it's this: Code:
root@DarkStar:~# ping 216.239.59.104 |
Greetings,
I find it interesting that Puppy Linux installs on a thumbdrive and the Connection Manager is on the desktop and starts and scans a wifi network is seconds. But a 5gig installation like slackware can't preinstall ndiswrapper or include a decent network setup program. And ps where are all those A to Z programs that were installed with the full install on the start menu? I not knocking Slackware, Ubuntu and Opensuse are just as bad. 20 gig of Linux DVDs and the only one that works right is a 92 meg Puppy installation. At least I have internet so I can search the forums for info on all these other worthless systems. Just my 2 cents worth tlcstat |
ticstat, does what you say helps anybody ? Bad digestion, maybe :scratch:
|
Greetings,
Depends! It should give them a heads up on a very small distro that runs wifi very well. That will at least give them internet so that they can search for the answers to all these big distro problems without going over to their neighbors pc to use internet. It makes sense to me that to be usable the GUI should at least have the installed programs on the start menu and a decent network utility. Especially since the synaptic and apt-get need a network connection. So to answer your question. If the developers are listening then, Yes it should help everybody. Hello! Are you listening! tlcstat |
Quote:
- Some (most ?) slackers don't use GUI very often. - E.g. I use a Fluxbox WM without any icon nor visible start menu (though I can access one with a right click). I prefer to access the apps I often use with keyboards shortcuts, it's *a lot* faster. - Synaptic and apt-get are useless for most slackers, who use Slackware tools for packages management instead. - I won't speak for other people, but slackware network-scripts package is all I need to connect my laptop to the Internet, be it by wire or wireless. Thus: - I believe you've heard about Slackware, but I wouldn't bet you really know it. - I understand that Puppy Linux fits your needs. Very well, but that doesn't mean it fits everybody's needs and it doesn't -- otherwise why wouldn't everybody use it ? - If you don't receive an immediate and enthusiastic response from the developers to your last post, may I suggest you contact them directly. To begin with you could write to Patrick Volkerding, who as you probably know is Slackware's creator and still it's main developer. You'll find his email address on following website: http://slackware.com Take care, |
Greeting,
However, the Slackware 12 does indeed have a GUI and so it should work like one. A GUI isn't something to just to look at until you get to the terminal. I been on computers since MSDOS 1.0 so I know how you feel about the command prompt. I've always liked it myself. Thing is it just isn't very functional for the everyday user. Internet, Checkbook etc are all better in a GUI. Interesting thing, I downloaded the Knoppix Live CD a few minutes ago. It had Ndiswrapper build in with plenty of other nice software. I copied my Widows drivers to a pendrive and had my wifi going in about ten minutes with the wrapper. Seems to me that slackware could do at least that much on a 4gig DVD. Especially since Ndiswrapper is only about 20k. If the Linux community wants to win over Windows users then they are going to have to build in a workable wifi solution. Thats the modern world. And that means a Graphical Wlan Connection manager that works. If I can get that with Puppy Linux and Knoppix then I should be able to get it from a 4Gig Slackware installation. After all whats a extra hundred kilobytes. Anyway, enjoyed your comments. tlcstat |
Quote:
Quote:
Quote:
Quote:
Quote:
Now I don't intend to convince you to use a system you don't like. But you are wasting your time trying to convince me to use another one that Slackware, or that Slackware should be different that what it is. And may be I'm wasting my time in answering you about that. But that's my fault, not yours :( Anyway, it'll be a pleasure to try to help you when you'll decide to install Slackware. :cool: |
legeipsnelU:
Did you try wicd as suggested in an earlier post? I used to use manual config scripts and wpa_supplicant, etc., but ever since wicd I have found wireless access to be very simple. Brian |
Quote:
I installed my slackware full install and did not run netconfig, and then I only modified my /etc/rc.d/rc.inet1.conf. My network used the eth1 interface so I just modified this one to fit my needs, and then I restarted it doing /etc/rc.d/rc.inet1 INTERFACE_RESTART and it worked! I did spend a long time reading different things but now it's working. I can rest in peace. |
Quote:
|
All times are GMT -5. The time now is 01:12 AM. |