Jan 28
Comms to wvally4 went down last night, in a similar way that hiland3 dropped out the previous night. hiland3 was able to restablish comms itself via the router_check.sh script, but wvally4 has not come back online.
Steve and Tom are at the site.
11:20 am:
router LEDs:
power on
wan flashing
wlan off
usb off
modem led: solid green
ifconfig eth0 looks ok
host www.google.com
64.233.187.99
ping www.google.com works
host www.eol.ucar.edu
169.254.222.173
That 169.254. address is a "private APIPA" address, which is what some systems use if they can't find a DHCP server.
Pings to that address succeed, and so the router_check.sh script thinks everything is OK.
I'll update the router_check.sh scripts so that if the host command returns 169.254.. then it will restart the router.