[Mesh] Changing the MAC address

[Mitar]

Hi!

> In the same way that the exit node serves as a barrier for the mesh
> to the internet, I think a node can do the same for MAC addresses of
> phones and it's locally connected devices.

OK. Guys, you are rediscovering L3 routing protocols. :-)

If you want this, then just use a L3 routing protocol. Then MAC
addresses are used only for local network around each particular node,
that MAC address is mapped to internal IP for the whole mesh, and then
on the gateway this internal IP is NATed to public IP.

The minus is that you cannot then roam between nodes. Or at least you
would have to implement roaming between nodes on L3 into some routing
protocol. Currently this is implemented only for BATMAN, as far as I know.

You can still traceroute the person based on internal IP, but not based
on MAC.

> This should eliminate the need for disabling the traceroute function,
> which from what understand needs to be there in order for batman to
> determine a reliable and quick connection between nodes.

No, BATMAN does not need traceroute. But it is really handy tool when
debugging the network.

> The only complication I can think of being able to create
> your own unique key is to verify on the network that it's unique. It
> probably can be figured out with working with the DAT files.
> http://www.open-mesh.org/projects/batman-adv/wiki/DistributedArpTable

Or just use big enough key. :-) UUID for example.

The main thing you have to have in mind is that client programs should
work as expected without modifications. So if you modify network stack
(introduce some new routing keys) probably operating system of the
client needs support for that as well?


Mitar

-- 
http://mitar.tnode.com/
https://twitter.com/mitar_m