From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4748F8DC.9040302@absorb.it> Date: Sun, 25 Nov 2007 09:53:56 +0530 From: rene MIME-Version: 1.0 Subject: Re: [B.A.T.M.A.N.] batmand still doesn't start the right way References: <4747BE35.3040307@absorb.it> <59044.85.41.146.90.1195884923.squirrel@krisma.oltrelinux.com> <4747C553.6020701@absorb.it> <200711241205.16596.axel@open-mesh.net> <47484D33.8020209@absorb.it> <20071124202412.GA29731@apoderado.ometepe.net> In-Reply-To: <20071124202412.GA29731@apoderado.ometepe.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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 Hi, Jan Hetges wrote: > that sounds quite familiar, at least ... > but for me it looks more like a > hardware-problem, or combination of hardware/firmware/arch. > i see problems like that only on atheros, especially atheros > on i386. no, sure it's not hardware-specific. The problems documented here had been on WRAP-boards(x86) with atheros, this is true, cause they had the majority in the testbed and we have more tools available on them. But had the problem on mipsel/broadcom (1 Buffalo, 1 unknown) too. hope to post more Information soon, Rene