From: "Linus Lüssing" <linus.luessing@web.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: [B.A.T.M.A.N.] [PATCHv2 0/3] batctl: multicast related patches
Date: Sun, 2 Mar 2014 23:17:59 +0100 [thread overview]
Message-ID: <1393798682-7703-1-git-send-email-linus.luessing@web.de> (raw)
The first two patches are unchanged. The third one made the -u and -m
options exclusive and now uses the first bit of the first byte of
the mac address to check whether it's a multicast address
(instead of checing for IPv4/IPv6 multicast mac prefix), as Antonio
suggested (thanks!).
Cheers, Linus
next reply other threads:[~2014-03-02 22:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-02 22:17 Linus Lüssing [this message]
2014-03-02 22:18 ` [B.A.T.M.A.N.] [PATCHv2 1/3] batctl: fix wrong header lines number for local translation table Linus Lüssing
2014-03-11 10:43 ` Marek Lindner
2014-03-02 22:18 ` [B.A.T.M.A.N.] [PATCHv2 2/3] batctl: add switch for setting multicast_mode Linus Lüssing
2014-03-11 10:46 ` Marek Lindner
2014-03-02 22:18 ` [B.A.T.M.A.N.] [PATCHv2 3/3] batctl: add unicast/multicast address filter option for TT output Linus Lüssing
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=1393798682-7703-1-git-send-email-linus.luessing@web.de \
--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