1. 22 3月, 2014 1 次提交
  2. 09 1月, 2014 1 次提交
    • A
      batman-adv: add isolation_mark sysfs attribute · c42edfe3
      Antonio Quartulli 提交于
      This attribute can be used to set and read the value and the
      mask of the skb mark which will be used to classify the
      source non-mesh client as ISOLATED. In this way a client can
      be advertised as such and the mark can potentially be
      restored at the receiving node before delivering the skb.
      
      This can be helpful for creating network wide netfilter
      policies.
      
      This sysfs file expects a string of the shape "$mark/$mask".
      Where $mark has to be a 32-bit number in any base, while
      $mask must be a 32bit mask expressed in hex base. Only bits
      in $mark covered by the bitmask are really stored.
      Signed-off-by: NAntonio Quartulli <antonio@open-mesh.com>
      Signed-off-by: NMarek Lindner <mareklindner@neomailbox.ch>
      c42edfe3
  3. 19 10月, 2013 4 次提交
  4. 10 10月, 2013 1 次提交
  5. 14 3月, 2013 1 次提交
    • M
      batman-adv: network coding - add the initial infrastructure code · d353d8d4
      Martin Hundebøll 提交于
      Network coding exploits the 802.11 shared medium to allow multiple
      packets to be sent in a single transmission. In brief, a relay can XOR
      two packets, and send the coded packet to two destinations. The
      receivers can decode one of the original packets by XOR'ing the coded
      packet with the other original packet. This will lead to increased
      throughput in topologies where two packets cross one relay.
      
      In a simple topology with three nodes, it takes four transmissions
      without network coding to get one packet from Node A to Node B and one
      from Node B to Node A:
      
       1.  Node A  ---- p1 --->  Node R                Node B
       2.  Node A                Node R  <--- p2 ----  Node B
       3.  Node A  <--- p2 ----  Node R                Node B
       4.  Node A                Node R  ---- p1 --->  Node B
      
      With network coding, the relay only needs one transmission, which saves
      us one slot of valuable airtime:
      
       1.  Node A  ---- p1 --->  Node R                Node B
       2.  Node A                Node R  <--- p2 ----  Node B
       3.  Node A  <- p1 x p2 -  Node R  - p1 x p2 ->  Node B
      
      The same principle holds for a topology including five nodes. Here the
      packets from Node A and Node B are overheard by Node C and Node D,
      respectively. This allows Node R to send a network coded packet to save
      one transmission:
      
         Node A                  Node B
      
          |     \              /    |
          |      p1          p2     |
          |       \          /      |
          p1       > Node R <       p2
          |                         |
          |         /      \        |
          |    p1 x p2    p1 x p2   |
          v       /          \      v
                 /            \
         Node C <              > Node D
      
      More information is available on the open-mesh.org wiki[1].
      
      This patch adds the initial code to support network coding in
      batman-adv. It sets up a worker thread to do house keeping and adds a
      sysfs file to enable/disable network coding. The feature is disabled by
      default, as it requires a wifi-driver with working promiscuous mode, and
      also because it adds a small delay at each hop.
      
      [1] http://www.open-mesh.org/projects/batman-adv/wiki/CatwomanSigned-off-by: NMartin Hundebøll <martin@hundeboll.net>
      Signed-off-by: NMarek Lindner <lindner_marek@yahoo.de>
      Signed-off-by: NAntonio Quartulli <ordex@autistici.org>
      d353d8d4
  6. 21 11月, 2012 1 次提交
  7. 11 4月, 2012 1 次提交
  8. 17 2月, 2012 1 次提交
  9. 22 8月, 2011 1 次提交
  10. 17 12月, 2010 1 次提交
  11. 30 11月, 2010 2 次提交
    • M
      Staging: batman-adv: adding gateway functionality · dfaf9dd3
      Marek Lindner 提交于
      Via the /sys filesystem you can change the gateway mode of a node using
      gw_mode. Adjustments to it can be done using gw_bandwidth for server
      mode and gw_sel_class for client mode.
      Signed-off-by: NMarek Lindner <lindner_marek@yahoo.de>
      [sven.eckelmann@gmx.de: Rework on top of current version]
      Signed-off-by: NSven Eckelmann <sven.eckelmann@gmx.de>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      dfaf9dd3
    • L
      Staging: batman-adv: Make hop_penalty configurable via sysfs · 1341a00a
      Linus Lüssing 提交于
      When having a mixed topology of both very mobile and rather static
      nodes, you are usually best advised to set the originator interval on
      all nodes to a level best suited for the most mobile node.
      
      However, if most of the nodes are rather static, this can create a lot
      of undesired overhead as a trade-off then. If setting the interval too
      low on the static nodes, a mobile node might be chosen as a router for
      too long, not switching away from it fast enough because of its
      mobility and the low frequency of ogms of static nodes.
      
      Exposing the hop_penalty is especially useful for the stated scenario: A
      static node can keep the default originator interval, a mobile node can
      select a quicker one resulting in faster route updates towards this
      mobile node. Additionally, such a mobile node could select a higher hop
      penalty (or even set it to 255 to disable acting as a router for other
      nodes) to make it less desirable, letting other nodes avoid selecting
      this mobile node as a router.
      Signed-off-by: NLinus Lüssing <linus.luessing@ascom.ch>
      Signed-off-by: NSven Eckelmann <sven.eckelmann@gmx.de>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      1341a00a
  12. 20 10月, 2010 1 次提交
  13. 09 7月, 2010 1 次提交
  14. 19 6月, 2010 1 次提交