1. 11 4月, 2012 1 次提交
  2. 11 3月, 2012 1 次提交
  3. 28 2月, 2012 1 次提交
  4. 17 2月, 2012 3 次提交
  5. 20 11月, 2011 1 次提交
    • A
      batman-adv: fixed hash functions type to uint32_t instead of int · c90681b8
      Antonio Quartulli 提交于
      There are two reasons for this fix:
      - the result of choose_orig() and vis_choose() is an index and therefore it can't
        be negative. Hence it is correct to make the return type unsigned too.
      
      - sizeof(int) may not be the same on ALL the architectures. Since we plan to use
        choose_orig() as DHT hash function, we need to guarantee that, given the same
        argument, the result is the same. Then it is correct to explicitly express
        the size of the return type (and the second argument). Since the expected
        length is currently 4, uint32_t is the most convenient choice.
      Signed-off-by: NAntonio Quartulli <ordex@autistici.org>
      Signed-off-by: NSven Eckelmann <sven@narfation.org>
      c90681b8
  6. 08 9月, 2011 2 次提交
  7. 22 8月, 2011 1 次提交
  8. 08 7月, 2011 1 次提交
  9. 05 7月, 2011 1 次提交
  10. 20 6月, 2011 3 次提交
    • A
      batman-adv: improved roaming mechanism · cc47f66e
      Antonio Quartulli 提交于
      With the current client announcement implementation, in case of roaming,
      an update is triggered on the new AP serving the client. At that point
      the new information is spread around by means of the OGM broadcasting
      mechanism. Until this operations is not executed, no node is able to
      correctly route traffic towards the client. This obviously causes packet
      drops and introduces a delay in the time needed by the client to recover
      its connections.
      
      A new packet type called ROAMING_ADVERTISEMENT is added to account this
      issue.
      
      This message is sent in case of roaming from the new AP serving the
      client to the old one and will contain the client MAC address. In this
      way an out-of-OGM update is immediately committed, so that the old node
      can update its global translation table. Traffic reaching this node will
      then be redirected to the correct destination utilising the fresher
      information. Thus reducing the packet drops and the connection recovery
      delay.
      Signed-off-by: NAntonio Quartulli <ordex@autistici.org>
      Signed-off-by: NSven Eckelmann <sven@narfation.org>
      cc47f66e
    • A
      batman-adv: improved client announcement mechanism · a73105b8
      Antonio Quartulli 提交于
      The client announcement mechanism informs every mesh node in the network
      of any connected non-mesh client, in order to find the path towards that
      client from any given point in the mesh.
      
      The old implementation was based on the simple idea of appending a data
      buffer to each OGM containing all the client MAC addresses the node is
      serving. All other nodes can populate their global translation tables
      (table which links client MAC addresses to node addresses) using this
      MAC address buffer and linking it to the node's address contained in the
      OGM. A node that wants to contact a client has to lookup the node the
      client is connected to and its address in the global translation table.
      
      It is easy to understand that this implementation suffers from several
      issues:
       - big overhead (each and every OGM contains the entire list of
         connected clients)
       - high latencies for client route updates due to long OGM trip time and
         OGM losses
      
      The new implementation addresses these issues by appending client
      changes (new client joined or a client left) to the OGM instead of
      filling it with all the client addresses each time. In this way nodes
      can modify their global tables by means of "updates", thus reducing the
      overhead within the OGMs.
      
      To keep the entire network in sync each node maintains a translation
      table version number (ttvn) and a translation table checksum. These
      values are spread with the OGM to allow all the network participants to
      determine whether or not they need to update their translation table
      information.
      
      When a translation table lookup is performed in order to send a packet
      to a client attached to another node, the destination's ttvn is added to
      the payload packet. Forwarding nodes can compare the packet's ttvn with
      their destination's ttvn (this node could have a fresher information
      than the source) and re-route the packet if necessary. This greatly
      reduces the packet loss of clients roaming from one AP to the next.
      Signed-off-by: NAntonio Quartulli <ordex@autistici.org>
      Signed-off-by: NMarek Lindner <lindner_marek@yahoo.de>
      Signed-off-by: NSven Eckelmann <sven@narfation.org>
      a73105b8
    • S
      batman-adv: Move compare_orig to originator.c · b8e2dd13
      Sven Eckelmann 提交于
      compare_orig is only used in context of orig_node which is managed
      inside originator.c. It is not necessary to keep that function inside
      the header originator.h.
      Signed-off-by: NSven Eckelmann <sven@narfation.org>
      b8e2dd13
  11. 30 5月, 2011 3 次提交
  12. 08 5月, 2011 3 次提交
  13. 02 5月, 2011 1 次提交
  14. 18 4月, 2011 2 次提交
  15. 05 3月, 2011 16 次提交