1. 08 11月, 2012 1 次提交
  2. 29 10月, 2012 3 次提交
  3. 23 8月, 2012 4 次提交
  4. 11 7月, 2012 1 次提交
  5. 02 7月, 2012 3 次提交
  6. 28 6月, 2012 2 次提交
  7. 25 6月, 2012 1 次提交
  8. 21 6月, 2012 3 次提交
  9. 19 6月, 2012 2 次提交
  10. 14 5月, 2012 1 次提交
  11. 11 5月, 2012 1 次提交
  12. 11 4月, 2012 4 次提交
  13. 11 3月, 2012 1 次提交
  14. 17 2月, 2012 5 次提交
  15. 20 11月, 2011 1 次提交
  16. 08 9月, 2011 1 次提交
  17. 22 8月, 2011 2 次提交
  18. 05 7月, 2011 1 次提交
  19. 20 6月, 2011 3 次提交
    • A
      batman-adv: improved gateway tq-based selection · 43676ab5
      Antonio Quartulli 提交于
      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: NAntonio Quartulli <ordex@autistici.org>
      Signed-off-by: NMarek Lindner <lindner_marek@yahoo.de>
      Signed-off-by: NSven Eckelmann <sven@narfation.org>
      43676ab5
    • A
      batman-adv: add wrapper function to throw uevent in userspace · c6bda689
      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: NAntonio Quartulli <ordex@autistici.org>
      Signed-off-by: NSven Eckelmann <sven@narfation.org>
      c6bda689
    • 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