From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: Marek Lindner Date: Thu, 3 Jan 2013 09:57:03 +0800 References: <50E31C20.6010604@altermundi.net> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <201301030957.04081.lindner_marek@yahoo.de> Subject: Re: [B.A.T.M.A.N.] Unterstanding gateway-mode - why do nodes have a "sticky" gateway 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 On Thursday, January 03, 2013 07:28:02 Jan L=FChr wrote: > >> The client should use 6a:4b:93:de:00:84 as a gatway, since it provides > >> much higher data rates - however, it is stuck at aa:31:0e:4a:0f:1d. > >=20 > > I have observed the same behavior. >=20 > That's quite frustrating. Can I debug, when and why batman-adv actually > chooses as specific gateway? Yes, you can. Enable the batman-adv debug log at compile and runtime. While= =20 retrieving the 'batman' log messages you should see something like: Adding route to gateway .. Changing route to gateway .. =46ound new gateway .. etc Maybe you can post the result here ? Cheers, Marek