From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: Marek Lindner Date: Sun, 20 Dec 2009 01:21:32 +0800 References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200912200121.32560.lindner_marek@yahoo.de> Subject: Re: [B.A.T.M.A.N.] Mesh network advice Reply-To: The list for a Better Approach To Mobile Ad-hoc Networking List-Id: The list for a Better Approach To Mobile Ad-hoc Networking List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: The list for a Better Approach To Mobile Ad-hoc Networking Hey, > This whole feature stuff is still confusing to me. > > I wondering how to make it more obvious to mere users? could you be a bit more specific ? What exactly is not obvious ? We always try our best to keep our stuff as simple as possible. :) > Also, I am into wireless connected sensor systems, so it would be nice > if each node had a provision to address multiple local sensors which might > be connected VIA serial port, local ethernet port or just i/o pins and > then access those from either another local mesh node or the greater > internet. > > I have yet to get the latest open-mesh hardware to see what pins are > available on their PCB? Are you sure this is right mailing list to ask this question ? The hardware is coming from open-mesh.com and not from open-mesh.org. ;) Regards, Marek