20 Nov, 2011

1 commit


22 Aug, 2011

1 commit


20 Jun, 2011

2 commits

  • Using throw_uevent() is now possible to trigger uevent signal that can
    be recognised in userspace. Uevents will be triggered through the
    /devices/virtual/net/{MESH_IFACE} kobject.

    A triggered uevent has three properties:
    - type: the event class. Who generates the event (only 'gw' is currently
    defined). Corresponds to the BATTYPE uevent variable.
    - action: the associated action with the event ('add'/'change'/'del' are
    currently defined). Corresponds to the BATACTION uevent variable.
    - data: any useful data for the userspace. Corresponds to the BATDATA
    uevent variable.

    Signed-off-by: Antonio Quartulli
    Signed-off-by: Sven Eckelmann

    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: Antonio Quartulli
    Signed-off-by: Marek Lindner
    Signed-off-by: Sven Eckelmann

    Antonio Quartulli
     

10 Jun, 2011

1 commit


30 May, 2011

1 commit


08 May, 2011

2 commits

  • The hard_if_event is called by the notifier with rtnl_lock and tries to
    remove sysfs entries when a NETDEV_UNREGISTER event is received. This
    will automatically take the s_active lock.

    The s_active lock is also used when a new interface is added to a meshif
    through sysfs. In that situation we cannot wait for the rntl_lock before
    creating the actual batman-adv interface to prevent a deadlock. It is
    still possible to try to get the rtnl_lock and immediately abort the
    current operation when the trylock call failed.

    Signed-off-by: Sven Eckelmann

    Sven Eckelmann
     
  • hardif_list_lock is unneccessary because we already ensure that no
    multiple admin operations can take place through rtnl_lock.
    hardif_list_lock only adds additional overhead and complexity.

    Critical functions now check whether they are called with rtnl_lock
    using ASSERT_RTNL.

    It indirectly fixes the problem that orig_hash_del_if() expects that
    only one interface is deleted from hardif_list at a time, but
    hardif_remove_interfaces() removes all at once and then calls
    orig_hash_del_if().

    Reported-by: Linus Lüssing
    Signed-off-by: Sven Eckelmann

    Sven Eckelmann
     

05 Mar, 2011

2 commits


31 Jan, 2011

1 commit


17 Dec, 2010

1 commit

  • B.A.T.M.A.N. (better approach to mobile ad-hoc networking) is a routing
    protocol for multi-hop ad-hoc mesh networks. The networks may be wired or
    wireless. See http://www.open-mesh.org/ for more information and user space
    tools.

    Signed-off-by: Sven Eckelmann
    Signed-off-by: David S. Miller

    Sven Eckelmann