Artigos‎ > ‎Configuração de Hardware‎ > ‎OpenWrt‎ > ‎

Libre Mesh no TP-Link TL-MR3420


Primeiramente gostaria de salientar que não sou o autor principal do conteúdo deste artigo. A minha intenção é de mostrar o que outros autores tem realizado (referenciando links para o conteúdo original) neste blog até como um guia pessoal para uso próprio e ainda compartilhar minhas anotações e pequenas modificações que realizo no conteúdo, desejando que possa ajudar mais alguém em algum lugar.
First and foremost, I take no credit for any of this post’s content. I am really just taking what others have done (which I have links to bellow) and am putting it on my blog for a personal reference and hopefully the small changes that I made to their guides will help someone somewhere.


link: http://libre-mesh.org/

Por que o Libre Mesh?

A arquitetura ou topologia de rede proposta pelo Libre Mesh é praticamente única: http://libre-mesh.org/projects/libre-mesh/wiki/Network_Architecture

 
The network architecture designed for libre-mesh is based in two layers: The cloud layer 2 which runs Batman-Adv and The network layer 3 which runs BMX6

By default all nodes are runing BMX6 and BATADV at same time in the same WiFi devices but different VLANS. However this can be changed by the user, both BMX6 and BATADV can be disabled according to the specific needs and requirements.
The BMX6 VLAN is always the same, so all link-layer connected nodes will see each other.

The BATADV VLAN depends on the cloud identifier (CID) which is calculed (by default) from the AP SSID.

This configuration allows to isolate the layer 2 clouds. 
For instance a neighborhood, a company complex or a street level hotsposts network can choose isolate their LAN from the rest of the network. 
However at the same time, they will be able to reach the rest of the community network using the layer 3 routed network.

In case an entire network community wants to have a single cloud, they can just use the same cloud identifier (CID).

 All WiFi Access Points from the same layer 2 cloud share the same SSID, a special anycast IPv4/IPv6 address and a special anycast MAC address.
It will allow real roaming inside the network, so the clients does not need to renew their IP configuration when they change from one AP to the other.
 
 All mesh nodes have a DHCP/RA server to provide valid IPs from the cloud to the clients.
The DHCP leasses file is shared among the cloud to prevent colisions (using A.L.F.R.E.D).
As long as all nodes share the same anycast MAC/IP, from the client point of view it is fully transparent. Thus the gateway is always the same nonetheless the mesh node where they are attached is different.
 
 When a client wants to reach the Internet or any other network which is not the one used in the layer 2 cloud, it sends the packet to the anycast gateway address.
An ebtables rule in the LAN/AP bridge prevents the layer 2 packets propagation in the cloud sent to the anycast address. So the mesh node where the client is associated gets the packet but not the others.
 
 The packet is routed throw the BMX6 layer 3 network to the best Internet gateway (according to the BMX6 metrics). It may be a node from the same cloud or any other from another far away cloud.
In the way back the packet will arrive to some node in the cloud but it may not be the same, it will depend on the routing protocol metrics.
 
 LibreMesh uses both IPv4 and IPv6. While the routed network layer is done only with IPv6, the IPv4 is tunneled using IPIP tunnels between the layer 2 clouds. Each cloud uses a /22 of IPv4 addresses (1024 ips), and /48 of IPv6 addresses (2^80 ips). 


Instalação:
https://dev.libre-mesh.org/projects/libre-mesh
https://dev.libre-mesh.org/projects/libre-mesh/wiki/Compile_Manually
https://github.com/libre-mesh/lime-build












O URL específico do gadget não foi encontrado



Comments