Repository : ssh://git@open-mesh.org/doc

On branches: backup-redmine/2017-07-13,master

commit 8720a7bb0a0d8470a551ae8e203132ad1c4c9d10 Author: Antonio Quartulli a@unstable.cc Date: Thu Mar 22 16:15:22 2012 +0000

doc: batman-adv/DistributedArpTable

8720a7bb0a0d8470a551ae8e203132ad1c4c9d10 batman-adv/DistributedArpTable.textile | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/batman-adv/DistributedArpTable.textile b/batman-adv/DistributedArpTable.textile index 794722b2..7676f7cb 100644 --- a/batman-adv/DistributedArpTable.textile +++ b/batman-adv/DistributedArpTable.textile @@ -55,10 +55,12 @@ h2. Technical details The snooping mechanism is actually made up by 4 events, which trigger different actions. The 4 possibilities are the following:

-# _Outgoing ARP Request_: The packet is intercepted, then the node checks if the requested IP is in the local cache: -* it is: the node drops the request and immediately forge a reply that is delivered to the client +# _Outgoing ARP Request_: The packet is intercepted and the source entry [MAC,IP] (contained in the packet) is stored for caching purposes, then the node checks if the requested IP is in the local repository: +* it is: the node drops the request and immediately forges a reply that is delivered to the client * it is not: the node queries the DHT table using the requested IP as search key. If no answer is received within a fixed amount of time (actually 250ms) the ARP request is broadcasted like it is usually done.

-# _Incoming ARP Request_: +# _Incoming ARP Request_: The packet is intercepted and the source entry [MAC,IP] (contained in the packet) is stored for caching purposes, then the node checks if the requested IP is in the local repository: +* it is: the node drops the request and immediately forges a reply that is sent over the mesh towards the client. +* it is not: the request is delivered to the local soft interface (to the local clients) # _Incoming ARP Reply_: # _Outgoing ARP Reply_: \ No newline at end of file