[CUWiN-Dev] Boatload of WRAP node problems

[Seth Price]

As I have mentioned before, I just moved into the Race and Washington  
intersection and I am having issues with my connection. I'm not sure  
how many of these are isolated to my node (10.0.150.205), and how  
many are related, so I'll lump them into one email.

- wdogctl is using ~100% of my cpu time, all the time. top  
continually looks like this:

   PID USERNAME PRI NICE   SIZE   RES STATE      TIME   WCPU    CPU  
COMMAND
1800 root      64    0    20K  352K RUN      544:45 84.33% 84.33%  
wdogctl
6971 root       2    0   380K 1252K kqread    28:35  2.10%  2.10% hslsd

- node continually sends out packets. Judging by the lights on the  
switch, some of them are broadcast, most are not. And yes, I see  
these continually when both desktops are in Sleep mode.

- Node "freezes" randomly. I've seen it go for about an hour and  
freeze, and I've seen it go overnight without freezing (only once  
though). I say "freezes" because although it won't respond or route,  
but I can see that it's ethernet interface is very active by the  
blinkenlights on the switch. SSH sessions stop responding and the  
ping to the node goes from < 1 ms to nothing. I can reset it simply  
by pulling the plug for a second. More top and ping info is avl if  
requested.

- My connection is extremely unreliable. It goes out for very short  
stretches, and it goes out for very long stretches. Yesterday I left  
"ping google.com" going for a while on my desktop to see if I could  
come up with any interesting stats. Here is a sampling of the kinds  
of errors that I get (watch the ICMP seq # to see where I cut and  
pasted, generally I only get one or two dropped packets, 10% of the  
time):

64 bytes from 216.239.57.99: icmp_seq=2915 ttl=242 time=76.559 ms
64 bytes from 216.239.57.99: icmp_seq=2916 ttl=242 time=75.694 ms
36 bytes from 10.0.216.146: Destination Host Unreachable
Vr HL TOS  Len   ID Flg  off TTL Pro  cks      Src      Dst
4  5  00 0054 2e4d   0 0000  3e  01 4bf6 10.22.228.253  216.239.57.99

64 bytes from 216.239.57.99: icmp_seq=2918 ttl=242 time=78.686 ms
64 bytes from 216.239.57.99: icmp_seq=2919 ttl=242 time=81.250 ms
64 bytes from 216.239.57.99: icmp_seq=2925 ttl=243 time=75.067 ms
64 bytes from 216.239.57.99: icmp_seq=2926 ttl=243 time=79.249 ms
36 bytes from 10.0.216.146: Destination Net Unreachable
Vr HL TOS  Len   ID Flg  off TTL Pro  cks      Src      Dst
4  5  00 0054 2e92   0 0000  3e  01 4bb1 10.22.228.253  216.239.57.99

64 bytes from 216.239.57.99: icmp_seq=2928 ttl=243 time=76.052 ms
64 bytes from 216.239.57.99: icmp_seq=2929 ttl=243 time=88.143 ms
64 bytes from 216.239.57.99: icmp_seq=3192 ttl=242 time=75.345 ms
64 bytes from 216.239.57.99: icmp_seq=3193 ttl=242 time=81.344 ms
36 bytes from 10.0.216.146: Time to live exceeded
Vr HL TOS  Len   ID Flg  off TTL Pro  cks      Src      Dst
4  5  00 0054 3598   0 0000  01  01 82ab 10.22.228.253  216.239.57.99

64 bytes from 216.239.57.99: icmp_seq=3197 ttl=242 time=77.350 ms
64 bytes from 216.239.57.99: icmp_seq=3198 ttl=242 time=76.518 ms
64 bytes from 216.239.57.99: icmp_seq=3199 ttl=242 time=86.643 ms
64 bytes from 216.239.57.99: icmp_seq=5332 ttl=243 time=501.553 ms
64 bytes from 216.239.57.99: icmp_seq=5333 ttl=243 time=624.787 ms
36 bytes from 10.0.216.146: Time to live exceeded
Vr HL TOS  Len   ID Flg  off TTL Pro  cks      Src      Dst
4  5  00 0054 6efe   0 0000  01  01 4945 10.22.228.253  216.239.57.99

36 bytes from 10.0.216.146: Time to live exceeded
Vr HL TOS  Len   ID Flg  off TTL Pro  cks      Src      Dst
4  5  00 0054 6f07   0 0000  01  01 493c 10.22.228.253  216.239.57.99

36 bytes from 10.0.216.146: Time to live exceeded
Vr HL TOS  Len   ID Flg  off TTL Pro  cks      Src      Dst
4  5  00 0054 6f0b   0 0000  01  01 4938 10.22.228.253  216.239.57.99

36 bytes from 10.0.216.146: Time to live exceeded
Vr HL TOS  Len   ID Flg  off TTL Pro  cks      Src      Dst
4  5  00 0054 6f0e   0 0000  01  01 4935 10.22.228.253  216.239.57.99

36 bytes from 10.0.216.146: Time to live exceeded
Vr HL TOS  Len   ID Flg  off TTL Pro  cks      Src      Dst
4  5  00 0054 6f11   0 0000  01  01 4932 10.22.228.253  216.239.57.99

64 bytes from 216.239.57.99: icmp_seq=5339 ttl=243 time=1191.821 ms
36 bytes from 10.22.228.254: Destination Net Unreachable
Vr HL TOS  Len   ID Flg  off TTL Pro  cks      Src      Dst
4  5  00 0054 72e7   0 0000  3f  01 065c 10.22.228.253  216.239.57.99

64 bytes from 216.239.57.99: icmp_seq=5340 ttl=243 time=1125.487 ms
64 bytes from 216.239.57.99: icmp_seq=5342 ttl=242 time=144.673 ms
64 bytes from 216.239.57.99: icmp_seq=29456 ttl=243 time=80.380 ms
64 bytes from 216.239.57.99: icmp_seq=29457 ttl=243 time=74.989 ms
36 bytes from 10.0.216.146: Destination Net Unreachable
Vr HL TOS  Len   ID Flg  off TTL Pro  cks      Src      Dst
4  5  00 0054 4932   0 0000  3e  01 3111 10.22.228.253  216.239.57.99

64 bytes from 216.239.57.99: icmp_seq=29459 ttl=242 time=76.716 ms
36 bytes from 10.0.216.146: Destination Net Unreachable
Vr HL TOS  Len   ID Flg  off TTL Pro  cks      Src      Dst
4  5  00 0054 4968   0 0000  3e  01 30db 10.22.228.253  216.239.57.99

64 bytes from 216.239.57.99: icmp_seq=29461 ttl=243 time=86.816 ms
64 bytes from 216.239.57.99: icmp_seq=29462 ttl=243 time=95.842 ms
64 bytes from 216.239.57.99: icmp_seq=29463 ttl=243 time=84.905 ms

As you can see, I left ping going for a while...until the node froze  
as described previously.

- Both web connections and ssh connections to my node take about 30  
seconds to get an initial response, then they generally work fine.  
With intermittent pauses.

- I occasionally get DNS entries that direct me to the chambana.net  
server homepage. CNN.com became chambana.net yesterday, for example.

- Before I got the node's wireless interface online, the RouteViz web  
GUI showed only my node and a single horizontal green line to the  
right. It was like my node was connected to something off screen (no  
matter how far I zoomed out). It was rather confusing.

- Now that my node is connected to the mesh, the routeviz images are  
404 errors.


Is there something truly screwed up with my node, or are all these  
things normal? An idea for what is causing interference is I get  
strong (100%) reception all through my apartment for a 2Wire system  
(2WIRE286) on channel 6. Blech. (Anyone know the default WEP  
password? That would solve some problems. ;)

BTW, I got my WRAP kit complete for $299, which was the initial  
reason I chose it over the Metrix kit. It seems like that is a bit  
cheaper than what I normally hear of people spending for a complete  
Metrix kit.

The good news is that the connection works as expected 70% of the  
time. The bad news is that I'm probably going to have to break down  
and get DSL and a land phone line.
Thanks,
Seth
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.chambana.net/mailman/archive/cu-wireless-dev/attachments/20050831/47d6fae1/attachment.html