From: "Linus Lüssing" <linus.luessing@web.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [PATCH 2/2] batman-adv: Fix aggregation direct-link bug
Date: Sat, 20 Mar 2010 10:36:15 +0100 [thread overview]
Message-ID: <20100320093615.GA3753@Linus-Debian> (raw)
In-Reply-To: <1269055908-20369-2-git-send-email-linus.luessing@web.de>
[-- Attachment #1: Type: text/plain, Size: 469 bytes --]
And there are two more things I'm wondering about:
- Why should primary interface OGMs from a different originator
which already travelled over 49 hops not be aggregated to other
primary interface OGMs?
- Why should secondary interface OGMs from neighbours not be
aggregated on our own, neighboring secondary interface OGMs?
As far as I can tell, those two combinations are not being
aggregated at the moment. Is there a reason why they shouldn't?
Cheers, Linus
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2010-03-20 9:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-20 3:31 [B.A.T.M.A.N.] [PATCH 1/2] batman-adv: fix aggregation timing bug Linus Lüssing
2010-03-20 3:31 ` [B.A.T.M.A.N.] [PATCH 2/2] batman-adv: Fix aggregation direct-link bug Linus Lüssing
2010-03-20 9:36 ` Linus Lüssing [this message]
2010-03-20 14:48 ` Marek Lindner
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=20100320093615.GA3753@Linus-Debian \
--to=linus.luessing@web.de \
--cc=b.a.t.m.a.n@lists.open-mesh.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox