From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Sat, 24 Nov 2007 14:24:12 -0600
From: Jan Hetges <tran@ms20.net>
Subject: Re: [B.A.T.M.A.N.] batmand still doesn't start the right way
Message-ID: <20071124202412.GA29731@apoderado.ometepe.net>
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>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="bg08WKrSYDhXBjb5"
Content-Disposition: inline
In-Reply-To: <47484D33.8020209@absorb.it>
Reply-To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@open-mesh.net>
List-Id: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n.open-mesh.net>
List-Unsubscribe: <https://list.open-mesh.net/mm/listinfo/b.a.t.m.a.n>,
	<mailto:b.a.t.m.a.n-request@open-mesh.net?subject=unsubscribe>
List-Archive: <http://list.open-mesh.net/pipermail/b.a.t.m.a.n>
List-Post: <mailto:b.a.t.m.a.n@open-mesh.net>
List-Help: <mailto:b.a.t.m.a.n-request@open-mesh.net?subject=help>
List-Subscribe: <https://list.open-mesh.net/mm/listinfo/b.a.t.m.a.n>,
	<mailto:b.a.t.m.a.n-request@open-mesh.net?subject=subscribe>
To: The list for a Better Approach To Mobile Ad-hoc Networking <b.a.t.m.a.n@open-mesh.net>


--bg08WKrSYDhXBjb5
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Nov 24, 2007 at 09:41:31PM +0530, rene wrote:
> Hi,
>=20
> just installed batmand on around ten nodes with multiple interfaces
> today. At least four of them faced the described problem (maybe more and
> I didn't realized yet), batmand didn't used all recognized interfaces to
> send OGMs.
> Solution? Killed batman, started batman, killed batman, started batman,
> for an incredible amount of times and at some point it started running
> the way it should.
>=20
> But this seems really buggy, nobody else facing this problem?

that sounds quite familiar, 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=20
on i386.=20

cheers

  --Jan


--bg08WKrSYDhXBjb5
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHSIhslTtvZdk47D4RAkEUAJ9jnKZrXw7Clqm7sAbm8BdCKVRrAQCgqpiw
mh7S82zOkJsV6sLnLqot+lg=
=m1um
-----END PGP SIGNATURE-----

--bg08WKrSYDhXBjb5--