On Sun, June 8, 2008 9:58 pm, James G. Sack (jim) wrote: > Lan Barnes wrote: >> I finally got a clean compile of CentOS with 4K stacks disabled, and the >> Airlink drivers under ndiswrapper no longer freeze the machine. And the >> iwlist scan can now find hotspots even through walls and at a distance, >> si >> it's beating the hell out of the on-board wireless. > > Hey! > >> >> But I'm not connecting. It's probably me (tired, hurried() and as soon >> as >> I remember how to configure a box, it'll fall into place. >> >> FWIW >> >> iwlist wlan0 scan >> >> wlan0 IEEE 802.11g ESSID:"marconi" Nickname:"clinton" >> Mode:Ad-Hoc Frequency:2.437 GHz Cell: 02:E0:1C:55:45:16 >> Bit Rate=54 Mb/s Tx-Power:20 dBm Sensitivity=0/3 >> RTS thr=2347 B Fragment thr=2346 B >> Power Management:off >> Link Quality:0 Signal level:0 Noise level:0 >> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 >> Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > The above doesn't look like iwlist output -- bad cut-n-paste? > >> >> iwcongig >> >> wlan0 IEEE 802.11g ESSID:"marconi" Nickname:"clinton" >> Mode:Ad-Hoc Frequency:2.437 GHz Cell: 02:E0:1C:55:45:16 >> Bit Rate=54 Mb/s Tx-Power:20 dBm Sensitivity=0/3 >> RTS thr=2347 B Fragment thr=2346 B >> Power Management:off >> Link Quality:0 Signal level:0 Noise level:0 >> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 >> Tx excessive retries:0 Invalid misc:0 Missed beacon:0 >> >> iwcongig >> >> wlan0 Link encap:Ethernet HWaddr 00:11:A3:08:4F:B2 >> inet addr:192.168.100.60 Bcast:192.168.100.255 >> Mask:255.255.255.0 >> UP BROADCAST MULTICAST MTU:1500 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) > > This last iwcongig was most likely an ifcongig, eh? ;-) > > Where did the IP address 192.168.100.60 come from? Unless it's > somehow-or-other left-over from a static address (or manually > assigned??), it seems like you are actually connecting!?! You do only > have one wireless device currently active in this box, I assume? Ad-hoc > doesn't look right to me -- I thought it should be mode managed (the > iwlist output should show mode master for the AP). Or maybe I'm confused? > > It would be good to get a good post of the output from > iwlist wlan0 scan > > Is the wireless AP at 192.168.100.1, maybe? have you tried pinging that? > What kind of AP is it? How do you admin it? > > Maybe dhcp is not working correctly. What do these commands show? > route -n > cat /etc/resolv.conf > and just for my curiosity (assuming CentOS uses dhclient), > ps -ef | grep dhclient > > Regards, > ..jim
Yup. And since the &^%$# proxy here at work refuses to let anything meaningful through (have to ask Wolfie how to circumvent that ... Mark'd know if anybody), I can't give you the real poop until this evening. But suffice to say that the scan picked up my access point plus three neighbors. -- Lan Barnes SCM Analyst Linux Guy Tcl/Tk Enthusiast Biodiesel Brewer -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
