.comment-link {margin-left:.6em;}

Wireless Mesh

Saturday, December 17, 2005

Cause and Effect

I remember the Matrix movie and there was a line about Cause and Effect. Nevertheless, I had a problem with one of MeshAP, it would link to the mesh and I was able to ping it but I was not able to SSH into the node. The client was complaining that he was not able to get in and was having problems.

I wasn't able to talk with the client directly but a reboot would have corrected the problem. I couldn't get the client to reboot nor was I able to physically go to the client Meshap. However, asking the Locustworld list for a solution gave me a number of different responses, of which none of them resolve the problem.

This morning I got up and it came to me that the problem may not be the Client's MeshAP but the Uplink Node. So I rebooted the uplink node and the clients node in question started to operate again. I notice that this sometimes happens with the intel boards. I use a Compaq computer for my uplink nodes and every few weeks they need a little reboot.

I instantly ssh into the MeshAP and did a remotemanagement and everything worked ok. I also noticed that some of the other Mesh nodes where now talking with each other. Rebooting the uplink node is sometimes more important that booting the MeshAP.

0 Comments:

Post a Comment

Links to this post:

Create a Link

<< Home