While working at Aspen, Andy came by and said the communication link from
Willow was down. So I stopped the work at Aspen to go to Willow. At Willow
I found the Breezecom communication light was read not green. I recycled
power on the breezecom and that got it going. Back at the CUFF trailer I
rebooted cosmos to get it going.

After Gordon's investigation, I followed-up by replacing the 16db patch antenna
at willow with a 24db parabolic.  I didn't get a chance to run the Breezecom
diagnostic utility (could we install it on aster using VMware and run it 
remotely?), but pinging seemed solid.

To do this, powered down the entire cosmos box about 1730-1800.

cosmos, aircoa1 and aircoa3 have not been transmitting since
the evening of Friday, Sep 10.

Came to C1 and started up the DS-11 wireless ethernet software on
the Panasonic.  (hook the network cable into the extra port on the
DLink hub, labeled Tower 10.0.0.x, next to CU's Dell).

I could connect to both station adaptors and the access point from
the trailer, so it isn't a power problem at willow.  I could ping
and log into cosmos - it reported an uptime of 9 days.

The 802.11 connection to willow does not have good signal strength:

The Station adaptor at willow is the breezecom unit B, which
has address 10.0.0.199

The DS.11 software reports the following statistics for  unit B,
unit C (10.0.0.197) (which is at pine), and the access point
(10.0.0.200):

       Signal Qual    RSSI             FCS Error rate
B         38%          -85dBm (42)        19%
C         86%          -74dBm (48)        1%
AP                                        35%
FYI: the SNMP write community password is what Dorothy told her dog.
The ESSID is "default", and the read password is "pubic".

As a hack I changed the channel to 6 from 11 on the access point.
Unit B had been fixed on channel 11, and I changed it to scanning mode, 
with preferred channels 1,6,11.  (That was the setting of unit C).
That change didn't help, but I left it.

I checked the antenna connections at willow and was able to turn the 
connector at the antenna about another quarter turn, but it didn't help 
the signal strength.  The antenna is pointed well to the CU tower.

Reset aircos3 and got things running again, but wasn't able to
make any improvements to the signal strength.

/var/log/messages back on aster reports  DHCPREQUEST and DHCPACKs about every
20 seconds for 10.0.0.199 - which I believe is a symptom of the bad
signal strength.

The wireless network link to willow is having problems.  It
ran poorly for about a day and a half then crapped out altogether.

Symptoms:  
  frequent dhcp requests from the Breezecom station adaptor
  at willow, often every 20 seconds!  Seen on aster:/var/log/messages.

  Network socket from willow data system shows many network
  temporarily not available errors, as seen with "ndaqstatus cosmos".

SteveS went to willow today to check things. He got it working again
but it is still showing the same symptoms.

aster
  eth0 (bottom PCMCIA card I believe - note the label above the keyboard)
    IPaddr: 10.0.0.3
    The 10.0.0 network is the data network,which we share with CU.
    The 10.0.0 hub is so marked in the trailer

  eth1
    IPaddr: 198.11.18.38 (isff.colorado.edu)
    The 198.11.18 network is the CU mountain research station
    network - the link to the internet. The 198.11.18 hub
    is to the right of the sparcstation.
russter (CU sparcstation): 
   le0: 10.0.0.1 (data network)
   le1:198.11.18.27  (CU MRS network)

quacker (CU data system)
   eth0: 10.0.0.2

cosmos (willow)
   eth0: 10.0.0.10
daisy (aspen?)
   eth0: 10.0.0.11
marigold (pine?)
   eth0: 10.0.0.12
aster is a DHCP server on the 10.0.0 network, giving 
out addresses in the range 10.0.0.100 - 10.0.0.200.  The Breezecom 
access point at the CU tower has been given 10.0.0.200, and it
will probably keep it the entire project.  The Breezecom at willow 
has been given 10.0.0.199.

So you can ping 10.0.0.2 to see if the link to the CU tower is up.
Ping 10.0.0.200 to see if the Breezecom on the CU tower is up,
and ping 10.0.0.199 to check if the wireless link to the
willow breezecom is working, then ping 10.0.0.10 to see if
the network and the prometheus are up.