Re: [B.A.T.M.A.N.] alfred and batadv-vis issue

["gary" <guohuizou2000@sina.com>]

Hi Sven and Jon,

Can you add a payload in multicast packets to carry the mac address, so we
can get the mac from the payload without concerning about whether it is IPv4
or IPv6?

Regards,
Gary

-----Original Message-----
From: Sven Eckelmann <sven@narfation.org> 
Sent: 2018年10月23日 14:29
To: Jonathan Haws <jhaws@sdl.usu.edu>
Cc: guohuizou2000@sina.com; b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] alfred and batadv-vis issue

On Dienstag, 23. Oktober 2018 04:04:42 CEST Jonathan Haws wrote:
[...]
> > I have a doubt for the issue.
> > Alfred should send the info by multicast packets. So the packet's 
> > dst mac address should be multicast mac address.
> > The packet with multicast mac address should be received by all 
> > group member, isn't it?
> > Why does the mesh point need peer's mac address for sending the info?
> 
> The rest of the devs may be able to answer better, but I believe it is 
> how alfred does its data storage and mapping of the source.

Correct, alfred is storing the data from each server using its mac address.
It is also looking up the TQ of master servers via the mac address. And the
mac address is expected to be extractable from the EUI64 based link-local
IPv6 address.

And of course, Jonathan's IPv4 implementation must get the mac address using
different methods. It is using the function ipv4_arp_request to get the
information from IPv4 neighbor table. And it looks like his implementation
is missing a reliable way to fill this neighbor table.

Kind regards,
	Sven