From: Simon Wunderlich <sw@simonwunderlich.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [PATCH] alfred: Make sure only link-local EUI64 is used as source
Date: Tue, 05 May 2015 12:21 +0200 [thread overview]
Message-ID: <2479424.tFhBkT1Z6y@prime> (raw)
In-Reply-To: <1427309467-31768-1-git-send-email-sven@narfation.org>
[-- Attachment #1: Type: text/plain, Size: 1223 bytes --]
On Wednesday 25 March 2015 19:51:07 Sven Eckelmann wrote:
> The linux kernel automatically chooses the source address. This can make
> problems when the metric prefers an address which is not the link-local
> EUI64 address. For example an user can add an additional address which also
> can be used for link-local communication but has a higher value in the
> metric. This can cause alfred to send UDP link-local packets with an
> address which cannot be decoded by the receiver to get the MAC address of
> the device. The communication with this device would then fail.
>
> It is possible to define the source address when we directly bind to it.
> This has the problem that this address cannot receive packets with a
> multicast address as destination. The workaround is to create two sockets
> for one netsock structure. One is the socket which can send all data and
> receives unicast packets. The second one is receiving the multicast traffic
> like the announcements from master alfred server processes.
>
> Signed-off-by: Sven Eckelmann <sven@narfation.org>
Applied in revision 986ca57, added Moritz Warnings "Tested-by" as per ticket
#208 [1].
Thanks a lot!
Simon
[1] http://www.open-mesh.org/issues/208
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2015-05-05 10:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-25 18:51 [B.A.T.M.A.N.] [PATCH] alfred: Make sure only link-local EUI64 is used as source Sven Eckelmann
2015-05-05 10:21 ` Simon Wunderlich [this message]
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=2479424.tFhBkT1Z6y@prime \
--to=sw@simonwunderlich.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