From: Antonio Quartulli <antonio@meshcoding.com>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Cc: Sven Eckelmann <sven@narfation.org>
Subject: Re: [B.A.T.M.A.N.] [PATCH] batman-adv: Use safer default config for optional features
Date: Fri, 06 Feb 2015 08:26:04 +0100 [thread overview]
Message-ID: <54D46C8C.2040800@meshcoding.com> (raw)
In-Reply-To: <1423153373-17033-1-git-send-email-sven@narfation.org>
[-- Attachment #1: Type: text/plain, Size: 775 bytes --]
Hi Sven,
thanks for this patch!
On 05/02/15 17:22, Sven Eckelmann wrote:
> The distributed_arp_table is in theory a good solution to reduce connection
> problems in large networks caused by ARP packet loss. Unfortunatelly, it seems
> to also break ARP resolution in simple mesh setups. The only solution which
> seems to be used by AP firmwares seems to be the deactivation of this feature.
Could you please be a bit more specific about the issue you are talking
about?
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.
Cheers,
--
Antonio Quartulli
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-02-06 7:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 16:22 [B.A.T.M.A.N.] [PATCH] batman-adv: Use safer default config for optional features Sven Eckelmann
2015-02-06 7:26 ` Antonio Quartulli [this message]
2015-02-06 12:38 ` Sven Eckelmann
2015-02-06 13:20 ` Antonio Quartulli
2015-02-07 7:27 ` Sven Eckelmann
2015-02-07 8:58 ` Antonio Quartulli
2015-02-18 7:33 ` Marek Lindner
2015-02-18 17:18 ` Martin Hundebøll
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54D46C8C.2040800@meshcoding.com \
--to=antonio@meshcoding.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=sven@narfation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.