Welcome to Linux Forums! With a comprehensive Linux Forum, information on various types of Linux software and many Linux Reviews articles, we have all the knowledge you need a click away, or accessible via our knowledgeable members.
ryanrad@(none):~> ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.781 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.781 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.772 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=0.766 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=0.749 ms
I'm emailing from the same computer via cable connect, so I know the router is working. Also, I have another laptop that can connect just fine via wireless running XP.
can you please tell me how you got the card to work???
i'm trying it for three weeks now, with different versions of ndiswrapper and with different versions of linux ( redhat9 and mandrake 10) but both aren't a success, i can't get the wireless to work, although it is the right driver according to ndiswrapper.
could you post a copy of your /etc/sysconfig/network-scripts/ifcfg-wlan0 file? perhaps i'm making a simple mistake that can be solved by looking at your ifcfg-wlan0 file
My fault bquark. When I pinged it the first time, I still had the cable plugged in. When you said to ping the router, I thought we were testing the router, not the wireless card.
This time I tried it wireless only and received this message:
ryanrad@(none):~> ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
My fault bquark. When I pinged it the first time, I still had the cable plugged in. When you said to ping the router, I thought we were testing the router, not the wireless card.
This time I tried it wireless only and received this message:
ryanrad@(none):~> ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
You are not reaching the router, so there is a problem. If it worked you would see the return time like the previous attempt with the cable. Did you end the ping with a ctrl-c? If you do it should tell you how many packets were dropped. Probably a 100% fromthe looks of it.
It has been so long that we have been working on this I have forgotten what I was having you check. I will think about it.
A Newbie's Getting Started Guide to Linux
Learn the basics of the Linux operating systems. Get to know what it is all about, and familiarize yourself with the practical side. Basically, if you're a complete Linux newbie and looking for a quick and easy guide to get you started this is it. subscribe
Open Source Security Myths Dispelled Dispel the five major myths surrounding Open Source Security and gain the tools necessary to make a truly informed decision for your IT organization subscribe
InformationWeek InformationWeek is the only newsweekly you'll need to stay on top of the latest developments in information technology. subscribe