slackware How to connect wireless network
I'm not able to connect a wireless network
The following codes are what I did Code:
bash-4.2# ifconfig Code:
bash-4.2# iwconfig Code:
ifconfig wlan0 up Code:
ifconfig Code:
iwlist wlan0 scanning |grep ESSID So I tried to connect Code:
iwconfig wlan0 essid MY_HOME There was no inet address Code:
ifconfig Code:
dhclient wlan0 I can't connect the internet using wlan0 Code:
bash-4.2# ifconfig |
Some essential information is needed: What make/model computer and what wireless chipset does it have (running lspci in a terminal should reveal that information, unless it's a USB dongle)?
|
Yeah I'm using USB dongle
Its name is NEXT-201N MINI It looks like this http://ez-net.co.kr/new_2012/upload/...20MINI_800.jpg And it provides drivers but I did't install Because when I typed iwconfig seems that my computer recognized the usb dongle http://www.ez-net.co.kr/ez-net/downl...20DRIVER_A.zip http://www.ez-net.co.kr/ez-net/downl...20DRIVER_A.zip |
The system may be seeing the device but may not have the correct firmware for it.
Unfortunately, I have no personal experience with it and all the relevant links I can turn up seem to be in Korean. This might be a case for ndiswrapper. I haven't had to use it for years. It can be hit-or-miss, but I have used it successfully (back on Slackware 10.x). There is a Slackbuild: http://slackbuilds.org/result/?searc...rapper&sv=14.1 Alien Bob has an article on NDISWrapper at his wiki: http://alien.slackbook.org/dokuwiki/...re:ndiswrapper |
Wasn't there somthing wrong with my commands?
By the way, dhclient looks like resetting wlan0 Code:
bash-4.2# iwconfig wlan0 essid MY_HOME And I installed ndiswrapper and installed driver using it When I type ndiswrapper -l Code:
bash-4.2# ndiswrapper -l Code:
ifconfig wlan0 up |
Hopefully someone will come along and help us out.
I'm out of ideas without one of those devices to test. Do you have a different maybe more mainstream brand of dongle you could try, maybe borrow one from a friend for some testing? This list may help, though it's a bit dated: http://www.cyberciti.biz/tips/linux-...pter-list.html |
Quote:
Code:
USB: 0BDA:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter That device should be supported by the rtl8192cu kernel module. Is this module being loaded when you plug the device? (Check the output of 'lsmod') Also, it may be easier trying to get this device working using the GUI frontend to NetworkManager. http://docs.slackware.com/slackware:...ation_services |
Thanks I feel like getting closer to the solution
kernel modules seem to be loaded properly Code:
Module Size Used by And when I activated it, suddenly my wired connection was disconnected So I had to turn it off and connected wired connection using 'dhclient eth0' And I also tried Wicd,Happily it didn't have the wired connection disconnected But When I tried to connect wifi points It says: Resetting IP address... Putting Interface up... Obtaining IP address... Connection Failed: Unable to Get IP Address At last,I just tried making on a Android access point And connecting to the AndroidAP was successful I can connect the AndroidAP using dhclient command and networkmanger and Wicd But unfortunately I failed to connect other wifi points I guess there's problem in my home network But I can connect other wifi points if I use my phone But my computer can't connect And there's also no problem with my usb dongle. I used to connect wifi when I was using windows |
Shouldn't he be using the command "dhcpcd wlan0" instead of "dhclient wlan0" or do they both work?
|
I'm not sure about how to use dhcpd
And don't know much about the difference between two Anyway it doesn't seem to work Code:
bash-4.2# dhcpd wlan0 |
It should not be `dhcpd` but `dhcpcd`
Note the extra "c" in the correct command. I use `dhcpcd` all the time and it works quite well but for all practical purposes it's the same as dhclient, so I don't think that's the issue. But anyway, it sounds more like an issue with your network; as I understand it, you were able to connect to your android phone as an AP from your Slackware system, yes? If so, maybe try temporarily turning off encryption on your home network and see if you can connect to it from your computer. |
Quote:
but there's already no encryption on the wifi see this http://i58.tinypic.com/10qaobc.png MY_HOME is what I'm trying to connect I really don't know there is a problem in my home network Because when I was using windows there was no problem connecting wireless network |
Notice how all the access points in range are using WPA2. So should you! WEP and WPA are busted for security, so staying on WEP/WPA is just signing yourself up for the internet bills that people leeching on your connection should be paying. http://www.aircrack-ng.org/
First, set your access point to use only WPA2. Yes, it takes some more work handling the PSK key, but it is the only realistic option. Second, I suggest that you try using NetworkManager rather than wicd. Third, if you are using a GUI network manager in Slackware, make sure that the file /etc/rc.d/rc.inet1.conf is the same as originally installed. From the email to root titled ' Welcome to Linux (Slackware 14.1)!' (bold emphasis is mine) Quote:
Fifth, try making initial connection with dhcpcd as it is the default, but it may be that you will have more success if you switch to using dhclient. (I have a device that does not play well with NetworkManager and the version of dhcpcd in Slackware 14.1). The default setting is set in /etc/NetworkManager/NetworkManager.conf Aside - Not recommended until you have a working GUI network manager setup as wpa_supplicant can be picky about options. Note - All of the following requires root privileges. If you want to use a wireless LAN connection with WPA2 encryption from the command line, then you will need to use wpa_supplicant with a string of options after setting up the /etc/wpa_supplicant.conf configuration file. It would pay to check initially that your device is not turned off in software by using rfkill. After establishing the connection to your access point with wpa_supplicant, you will need to run dhcpcd or dhclient to further configure your internet connection via DHCP. |
I've followed what you said
I deleted wicd and set loopback using netconfig I enabled /etc/rc.d/rc.networkmanager I set networkmanager using netconfig And it no longer disturbs the wired connection Still, I'm only able to connect my AndroidAP http://i58.tinypic.com/idxjwz.png |
If you can connect to the AndroidAP, then the NetworkManager setup and the appropriate kernel module loading are OK. There must be some configuration problem with the connection to the MY_HOME access point. Is there anything in the logs (check /var/log/messages and /var/log/syslog) that they may give a clue?
You can also get more detailed logging using the procedure in this post. http://www.linuxquestions.org/questi...9/#post5067787 |
Thanks allend, frankbell, notKlaatu, itsgregman
I really don't know why But today my computer was suddenly connected via the networkmanager May be it was my cheap usb dongle or weak signal Anyway I really feel sorry and thankful for you all |
Thanks allend, frankbell, notKlaatu, itsgregman
I really don't know why But today my computer was suddenly connected via the networkmanager May be it was my cheap usb dongle or weak signal Anyway I really feel sorry and thankful for you all |
All times are GMT -5. The time now is 08:23 PM. |