After trying the usual sorts of things (power cycle, power cycle again in a fit of sheer optimism, opwer cycle with it next to the access point, tcpdump on the network looking for it's MAC address) it was clear that things had gone badly wrong.
10:38:04.919893 00:18:56:10:1d:b6 > Broadcast, 802.3, length 60: LLC, dsap Null (0x00) Individual, ssap Null (0x00) Response, ctrl 0xaf: Unnumbered, xid, Flags [Response], length 46: 01 00
10:38:09.174952 00:18:56:10:1d:b6 > Broadcast, 802.3, length 60: LLC, dsap Null (0x00) Individual, ssap Null (0x00) Response, ctrl 0xaf: Unnumbered, xid, Flags [Response], length 46: 01 00
10:38:13.444594 00:18:56:10:1d:b6 > Broadcast, 802.3, length 60: LLC, dsap Null (0x00) Individual, ssap Null (0x00) Response, ctrl 0xaf: Unnumbered, xid, Flags [Response], length 46: 01 00
10:38:17.707051 00:18:56:10:1d:b6 > Broadcast, 802.3, length 60: LLC, dsap Null (0x00) Individual, ssap Null (0x00) Response, ctrl 0xaf: Unnumbered, xid, Flags [Response], length 46: 01 00
It was basically just broadcasting an invalid ethernet frame over and over again. Curses. Looks like it had corrupted its configuration.
After laboriously re-installing the windows software, it wanted a firmware update (2.0396 -> 2.0400 ) which I did. Pulling the log from the card showed things like..
[111:32] Disconnected from WLAN (reason = 4).
[111:32] Connection dropped (previous state is 2)
looping. Yuck. No idea what causes it to corrupt it's settings. It's "fixed" now in the sense that it's uploading images again, but I'm a little perturbed. (Luckily the firmware update didn't break the perl server).
I need to find out why Dave Hansens linux utility doesn't work and fix it. It's very annoying having to fire up a windows instance all the time.
No comments:
Post a Comment