Linux - Wireless NetworkingThis forum is for the discussion of wireless networking in 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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I'm trying to go fully wireless in my house and get my PC up and running with a USB wireless adaptor (it's a D-Link DWL-G122). I got the driver installed using ndiswrapper, and "ndiswrapper -l" does show me the driver loaded into memory. Next I did:
# modprobe ndiswrapper
# ifconfig eth0 down
# ifconfig eth1 down #I have 2 wired network cards in my comp.
# iwconfig wlan0 essid cupotea
# iwconfig wlan0 mode managed
# ifconfig wlan0 192.168.2.1 netmask 255.255.255.0
# route add default gw 192.168.2.1 netmask 255.255.255.0
# ifconfig wlan0 up
I don't get any errors along the way.
The problem I have is I can only see my PC's and the router on my internal network. I can ping these PC's and the router and I can visit my router homepage at 192.168.2.1 in a browser and it works OK. If I try to visit any external sites it says "[sitename] could not be found. Please check the name and try again." If I try and ping the external IP address of my router it says "connect: Network is unreachable" .... it's like it doesn't know the route and it's not using 192.168.2.1 as the gateway?
One more thing, I can't shut down my computer either. When I do "shutdown -h now" the screen fills up with this:
and then try pinging external sites. Of course, ensuring /etc/resolv.conf is correct first. Don't know why it didn't like the netmask, but both at home + work it won't take it, yet my desktop machines (different card) need it set.
Since you're using a static IP, you do need to set up your /etc/resolv.conf file to include your ISP's nameservers. My guess is that you could surf by IP address (for example, if you try to go to 184.108.40.206 you would end up here at LQ). So for each nameserver your ISP has, you need to add a line like this:
The problem sounds like the domain name server or gateway. For the gateway, fouldsy's suggestion should work (if you follow that by restarting the network /etc/rc.d/network restart). What does your file /etc/resolv.conf have? You don't want the first entry to be the router address (192.168.2.1)
Originally posted by Hangdog42 Since you're using a static IP, you do need to set up your /etc/resolv.conf file to include your ISP's nameservers. My guess is that you could surf by IP address (for example, if you try to go to 220.127.116.11 you would end up here at LQ). So for each nameserver your ISP has, you need to add a line like this:
Ok, I too am having this problem, but my resolv.conf file appears to be correct, according to what was mentioned above. Here are it's contents,
; generated by /sbin/dhclient-script
My wireless connection works fine, but when I shutdown or reboot, that "wrap_reset_port:1040 reset failed -22" error repeats infinitely. I'm using Fedora Core 4, and this is a belkin usb adapter, model F5d7050 with ndiswrapper.
I'm new to Linux, but not computing, and I can usually figure these things out. This one, I'm stumped.
I'm afraid that error message (wrap_reset_port:1040 reset failed -22) has me stumped as well. Googling on it only brings up this thread. If this shutdown error is the only problem, I would post it at the ndiswrapper forum and see if one of the developers can help. They are probably going to suggest you use the latest version of ndiswrapper, so make sure you are.
If your problem is that you can't surf by name, it could be a couple of things. First off, can you surf by IP address? Also, from your resolv.conf file, it looks as if you are using DHCP to get an IP address for your wireless card. Are you sure that is happening? Check the output of ifconfig to make sure. Finally, while your resolv.conf entry should work, it couldn't hurt to add your ISP DNS servers and see if that makes a difference.
DoctorWynn: Are you still having this problem? I noticed a difference between your resolv.conf and mine. In mine my nameservers are listed at the top, and "search domain" is listed on the last line at the end. It could be worth trying - little things like this normally make a difference in Linux.
Hangdog42: to get around the "wrap_reset_port:1040 reset failed -22" problem I just kill the ndiswrapper process as part of the system shutdown ... perhaps not the most graceful approach but it does get around the problem.
Originally posted by stokes DoctorWynn: Are you still having this problem? I noticed a difference between your resolv.conf and mine. In mine my nameservers are listed at the top, and "search domain" is listed on the last line at the end. It could be worth trying - little things like this normally make a difference in Linux.
Yes I am. And can't find any info on it anywhere but here. I will take a look at your suggestion today, and let you know how it goes. It's weird cuz everything works fine. The wireless connection is strong, but this error at shutdown causes me to have to turn off the box manually which I don't like doing for fear of screwing something up. But then again, this isn't windoze!