Re: [B.A.T.M.A.N.] [PATCH] batman-adv: Use safer default config for optional features

From: Sven Eckelmann <sven@narfation.org>
To: Antonio Quartulli <antonio@meshcoding.com>
Cc: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] [PATCH] batman-adv: Use safer default config for optional features
Date: Fri, 06 Feb 2015 13:38:42 +0100	[thread overview]
Message-ID: <2688831.HMc8mZG1gy@bentobox> (raw)
In-Reply-To: <54D46C8C.2040800@meshcoding.com>

[-- Attachment #1: Type: text/plain, Size: 1301 bytes --]

On Friday 06 February 2015 08:26:04 Antonio Quartulli wrote:
> Could you please be a bit more specific about the issue you are talking
> about?

I can only talk about the simple two node installation I had when I was forced 
to write the wireshark-batman-adv dissector for v15. I just placed them next 
to each other and tried to ping the other one (not sure anymore if it was the 
node directly or two other devices plugged in the ethernet port of the 
devices). And I think there was a reboot of one node and a ARP cache flush 
involved. I've expected to see the 4addr packets when capturing on the 
wireless and then having both nodes talking to each other. This was not 
working. I could only communicate after disabling DAT... but of course the 
communication which I wanted to capture wasn't happening.

Either I got a dump from you or I've tried again until it worked.

> So far the only situation where I personally switched DAT off did not
> really get fixed and continued to show the issue. Therefore I am not
> really sure that DAT can be blamed for this.
> 
> So far I don't know anybody else who complained about DAT.

You have to ask Marek why DAT is disabled in many installations for which he 
is more or less responsible. Maybe he has more to contribute than me.

Kind regards,
	Sven

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]