[Voyage-linux] Lost communications with Voyage AP...

[Jerry]

Hello!

I have a p][ computer running Voyage (most recent official "release" i believe).  It has a intelPro100 network and a dwl g520 (atheros) in a bridge (ap0) with another (rtl8139) net card (for use like a serial port) with a private address on it (but is not used, only the intel is physically hooked to anything, but of course the IP is on the AP (ap0)).  anyway...

This is a simple "g" mode bridge to an ap (wrap using StarOS) that is broadcasting.  (I get a good 15 to 20Mbs across the link, which i would expect, its about 1/2 mile).  Within 18 hours, I have lost contact with the bridge...  But, it is still passing information as if it is working normally.   It would seem to have "lost its gateway"  as I cannot ping it from out side the network it is on.  I can ping it from within the network, however, but it actively refuses ssh, it would seem.  If I connect to it from the StarOS (which has to go THROUGH the voyage bridge), I get the following error:

Connecting to: xx.xx.xx.9
Local: Bad packet length 1349676916.

SSH session ended with exit code: 0

The wisp-dist machines I have on the same net just act as if I just pressed enter with out putting any command when I try to ssh into it... 

Any ideas how to get into the device?  or for that matter, how long the bridge will remain intact? Its "working", in that it is doing what I placed it in service for, however, I have no communication with it.

Oh, it is 1 1/2 hr away...   :(  and, of course, if it is gonna break, it will on friday night. :(

Suggestions?

Ideas?

Thanks

Jerryf
    
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.voyage.hk/pipermail/voyage-linux/attachments/20051109/0db966a8/attachment-0001.html>