K.S. Bhaskar on 3 Aug 2006 22:21:30 -0000 |
Turn the router off and back on. Then try again. [This has worked for me somtimes when I have had this problem...] Then try assigning the card a static IP address within the subnet the router is in, but outside the range it manages, and try pinging the router. For example, if the router is at 192.168.1.1, manages 192.168.1.100 & up, try a static address like 192.168.1.60: sudo ifconfig ath0 192.168.1.60 up ping -c3 192.168.1.1 If that doesn't work, then I am out of my depth. -- Bhaskar On 8/3/06, Mike Leone <turgon@mike-leone.com> wrote: On Thursday 03 August 2006 17:50, K.S. Bhaskar wrote: > On 8/3/06, Mike Leone <turgon@mike-leone.com> wrote: > > [KSB] <...snip... > > > iwconfig: > > lo no wireless extensions. > > > > eth0 no wireless extensions. > > > > ath0 IEEE 802.11 ESSID:"mike-leone-54g" > > Mode:Managed Frequency:2.442 GHz Access Point: Not-Associated > > Bit Rate:1 Mb/s Tx-Power:18 dBm Sensitivity=0/3 > > Retry:off RTS thr:off Fragment thr:off > > Power Management:off > > Link Quality=0/94 Signal level=-95 dBm Noise level=-95 dBm > > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > [KSB] What happens when you try "sudo dhclient ath0"? ___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
|
|