Kent West wrote: > Kent West wrote: > >> Mathew Moore suggested I use wicd-curses. >> >> So I did; found the ACUWireless node; tried pressing "c" to connect; >> nothing happened; then tried "C", and the machine froze up again. >> >> >> > > Wait, wait. The machine came back to life after a few minutes. > > But still, no indication of being connected wirelessly: > > > we...@evoljasen:~$ sudo ifconfig > > > wlan0 Link encap:Ethernet HWaddr 00:18:f8:29:b5:96 > UP BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:1 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:0 (0.0 B) TX bytes:108 (108.0 B) > > wmaster0 Link encap:UNSPEC HWaddr > 00-18-F8-29-B5-96-65-74-00-00-00-00-00-00-00-00 > UP RUNNING MTU:0 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) > >
After a couple of reboots, and after running wicd-client from the actual machine instead of over ssh, the machine did not lock up; it did see the various ACUWireless networks, but when I tried clicking on the first one, it thought for a minute or two, then reported "Connection failed: Unable to get IP Address". -- Kent West <*)))>< http://kentwest.blogspot.com Praise Yah! \o/ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
