23 Sep, 2011

1 commit

  • corrects a critical bug of the GW feature. This bug made all the unicast
    packets destined to a GW to be sent as broadcast. This bug is present even if
    the sender GW feature is configured as OFF. It's an urgent bug fix and should
    be committed as soon as possible.

    This was a regression introduced by 43676ab590c3f8686fd047d34c3e33803eef71f0

    Signed-off-by: Antonio Quartulli
    Signed-off-by: Marek Lindner

    Antonio Quartulli
     

13 Jul, 2011

1 commit

  • Almost all of these have long outstayed their welcome.

    And for every one of these macros, there are 10 features for which we
    didn't add macros.

    Let's just delete them all, and get out of habit of doing things this
    way.

    Signed-off-by: David S. Miller
    Acked-by: Stephen Hemminger
    Acked-by: Arnd Bergmann

    David S. Miller
     

08 Jul, 2011

5 commits


06 Jul, 2011

1 commit


05 Jul, 2011

6 commits


21 Jun, 2011

1 commit


20 Jun, 2011

12 commits

  • If a client issues a DHCPREQUEST for renewal, the packet is dropped
    if the old destination (the old gateway for the client) TQ is smaller
    than the current best gateway TQ less GW_THRESHOLD

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

    Antonio Quartulli
     
  • In case of new default gw, changing the default gw or deleting the default gw a
    uevent is triggered with type=gw, action=add/change/del and
    data={GW_ORIG_ADDRESS} (if any).

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

    Antonio Quartulli
     
  • The gateway election mechanism has been a little revised. Now the
    gw_election is trigered by an atomic_t flag (gw_reselect) which is set
    to 1 in case of election needed, avoding to set curr_gw to NULL.

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

    Antonio Quartulli
     
  • 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 local and the global translation-tables are now lock free and rcu
    protected.

    Signed-off-by: Antonio Quartulli
    Acked-by: Simon Wunderlich
    Signed-off-by: Sven Eckelmann

    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: 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
     
  • The amount of duplicated code in the receive and routing code can be
    reduced when all headers provide the packet type, version and ttl in the
    same first bytes.

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

    Antonio Quartulli
     
  • char was used in different places to store information without really
    using the characteristics of that data type or by ignoring the fact that
    char has not a well defined signedness.

    Signed-off-by: Sven Eckelmann

    Sven Eckelmann
     
  • count_real_packets() in batman-adv assumes char is signed, and returns -1
    through it:

    net/batman-adv/routing.c: In function 'receive_bat_packet':
    net/batman-adv/routing.c:739: warning: comparison is always false due to limited range of data type

    Use int instead.

    Signed-off-by: David Howells
    [sven@narfation.org: Rebase on top of current version]
    Signed-off-by: Sven Eckelmann

    David Howells
     
  • interface_tx is not used outside of soft-interface.c and thus doesn't
    need to be declared inside soft-interface.h

    Signed-off-by: Sven Eckelmann

    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: Sven Eckelmann

    Sven Eckelmann
     

10 Jun, 2011

7 commits


06 Jun, 2011

1 commit


30 May, 2011

5 commits