On Mon, Oct 17, 2005 at 02:37:11PM -0600, Chris Kuethe wrote: > On 17/10/05, Marcus Glocker <[EMAIL PROTECTED]> wrote: > > Hi Chris, List, > > > > Thanks for pointing out the problem. Your patch is not exactly right, > > as you are passing now 2 times the signal value to draw_signal. But we > > need the speed (speed) and signal strength (r) to calculate the bar. > > The problem is if we can't catch the speed for a moment, the speed > > pointer contains NULL, and if NULL is passed to atoi(3) it cores. > > > > I fixed it now in version 0.2. Attached the new port. > > OK, this time it doesn't core. > > All the "LEDs" are dark on an unconfigured iwi. That's what I'd expect. > > Ifconfig'ing iwi0 up, there seems to be a discrepancy between what > ifconfig says the signal strength is "100dBm" and what wmwlmon says it > is "88dB". I'm about 8ft away from the AP, and traffic is flowing > across it. > > iwi0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > lladdr 00:12:f0:c4:56:97 > media: IEEE802.11 autoselect (DS1) > status: active > ieee80211: nwid linksys chan 6 bssid 00:06:25:61:1d:ea 100dBm > inet6 fe80::212:f0ff:fec4:5697%iwi0 prefixlen 64 scopeid 0x2 > inet 10.0.0.66 netmask 0xffffff00 broadcast 10.0.0.255 > > No errors in dmesg from the card locking up though. I'm definately > looking forward to getting rid of the iwi in favor of an ath... >
My ipw(4) stucks at 100dBm as well. I think is is some kind of Intel issue. Whereas "tcpdump -y IEEE802_11_RADIO -n -i ipw0" shows a more correct signal strength: 22:45:25.639195 802.11: data: truncated-ip - 186 bytes missing!192.168.0.1.1900 > 239.255.255.250.1900: udp 252, <radiotap v0, chan 1, 11b, signal 17dB> BTW this is the AP somewhere across the street. -- :wq Claudio
