From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: Sven Eckelmann <sven@narfation.org>
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [PATCHv2 2/2] batman-adv: Snoop DHCPACKs for DAT
Date: Tue, 23 Aug 2016 03:31:00 +0200 [thread overview]
Message-ID: <20160823013100.GC27083@otheros> (raw)
In-Reply-To: <2069472.CH1chEaXG0@sven-edge>
On Sun, Jul 10, 2016 at 01:42:32PM +0200, Sven Eckelmann wrote:
> It sounds like the patch didn't help. So I will postpone my review.
Right. As discussed with Antonio on IRC, we might go with
Andreas's original patch to snoop IP traffic - but only to update
already existing, local DAT entries. So some changes still needed
in that patch there.
The approach is similar to what the Linux IP stack does for it's own
neighbor tables already.
Then we will see how much ARP traffic is still left afterwards.
I'm marking this patch as "Defered" in patchwork.
Further revelations, test results, ideas and progress will be
probably be tracked here:
https://www.open-mesh.org/issues/291
next prev parent reply other threads:[~2016-08-23 1:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-05 18:01 [B.A.T.M.A.N.] [PATCHv2 1/2] batman-adv: Add wrapper for ARP reply creation Linus Lüssing
2016-07-05 18:01 ` [B.A.T.M.A.N.] [PATCHv2 2/2] batman-adv: Snoop DHCPACKs for DAT Linus Lüssing
2016-07-07 9:24 ` Antonio Quartulli
2016-07-07 9:43 ` Sven Eckelmann
2016-07-07 10:14 ` Linus Lüssing
2016-07-07 13:40 ` Linus Lüssing
2016-07-08 0:33 ` Antonio Quartulli
2016-07-10 11:42 ` Sven Eckelmann
2016-08-23 1:31 ` Linus Lüssing [this message]
2016-07-10 11:18 ` [B.A.T.M.A.N.] [PATCHv2 1/2] batman-adv: Add wrapper for ARP reply creation Sven Eckelmann
2016-10-18 13:01 ` [B.A.T.M.A.N.] [v2, " Sven Eckelmann
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=20160823013100.GC27083@otheros \
--to=linus.luessing@c0d3.blue \
--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.