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

Punky Tse (spam-protected)
Thu Nov 10 12:04:01 HKT 2005


Jerry

I have tried to understand you problem in these few days, but I got no 
idea because I really don't understand about you network topology.  What 
is the purpose of you network.  And from what prespective (client side, 
within network, which node, etc.) you found it lost communication? Can 
you explain you case use the following diagram?

client ----- (eth0) voyage (br0 or ath0?) ---- (???) StarOS (???)

please highlight some key points so that we are able to help:
- state clearly you interface setup, e.g. what interface you used to 
build the bridge.
- what do you mean by ping from outside?
- what do you mean by official release? voyage-0.1sarge? and kernel 
version? (uname -a)

Thanks,
Punky

Jerry wrote:

> 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
>     
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Voyage-linux mailing list
>Voyage-linux at list.voyage.hk
>http://list.voyage.hk/mailman/listinfo/voyage-linux
>  
>


-- 
Regards,
Punky
P U N K N ! X  . c o m
Technology + Lifestyle
(http://www.punknix.com)

Voyage Linux
(http://www.voyage.hk/software/voyage.html)






More information about the Voyage-linux mailing list