Skip to content
Snippets Groups Projects
  1. Apr 21, 2021
  2. May 12, 2020
  3. Oct 29, 2019
  4. Sep 25, 2019
  5. Sep 21, 2019
    • Linus Lüssing's avatar
      Revert "gluon-mesh-batman-adv: reenable batman-adv multicast optimizations" · 302a7951
      Linus Lüssing authored
      This reverts commit 9b1eb40f.
      
      With the batman-adv v2019.2 upgrade reverted (c1a77339), the batman-adv
      multicast-to-multi-unicast feature is not available yet. Without that it is
      going to be very unlikely of the batman-adv multicast optimizations to
      take effect. E.g. some outdated nodes would disable it.
      
      To avoid confusion and diversion with a few communities having it enabled
      and most implicitly deactivated, just deactivate it for all for now
      until batman-adv is updated to v2019.2 or greater again.
      302a7951
  6. Aug 22, 2019
  7. Jun 18, 2019
  8. Jun 16, 2019
  9. Jun 07, 2019
  10. Jul 22, 2018
    • Sven Eckelmann's avatar
      gluon-client-bridge: Revert "move IPv4 local subnet route to br-client (#1312)" · 3ef28a46
      Sven Eckelmann authored
      The commit b3762fc6 ("gluon-client-bridge: move IPv4 local subnet route
      to br-client (#1312)") moves the IPv4 prefix from the local-port interface
      to br-client. A client requesting an IPv4 connection to the IPv4 anycast
      address of the node (the device running gluon) will create following
      packets:
      
      1. ARP packet from client to get the MAC of the mac address of the anycast
         IPv4 address
      2. ARP reply from node to client with the anycast MAC address for the IPv4
         anycast address
      3. IPv4 packet from client which requires reply (for example ICMP echo
         request)
      4. ARP request for the client MAC address for its IPv4 address in prefix4
         (done with the mac address of br-client and transmitted over br-client)
      5. IPv4 packet from node (transmitted over br-client with br-client MAC
         address) as reply for the client IPv4 packet (for example ICMP echo
         reply)
      
      The step 4 and 5 are problematic here because packets use the node specific
      MAC addresses from br-client instead of the anycast MAC address. The client
      will receive the ARP packet with the node specific MAC address and change
      their own neighbor IP (translation) table. This will for example break the
      access to the status page to the connected device or the anycast DNS
      forwarder implementation when the client roams to a different node.
      
      This reverts commit b3762fc6 and adds an
      upgrade code to remove local_node_route on on existing installations.
      3ef28a46
  11. Apr 13, 2018
  12. Mar 11, 2018
    • Matthias Schiffer's avatar
      gluon-mesh-batman-adv: increase bridge multicast querier robustness to 9 · c80c294b
      Matthias Schiffer authored
      The RFC standard multicast querier interval is 120s. Our querier uses in
      interval of 20s for better support of roaming clients, but our robustness
      setting of 3 leads to external queriers using the standard interval to be
      timeout after only 60s, leading to frequent "querier appeared/disappeared"
      messages. Increase robustness so that external queriers with any interval
      <180s are supported.
      c80c294b
  13. Feb 15, 2018
  14. Nov 25, 2017
    • Christof Schulze's avatar
      gluon-core: firewall rework, make base policy more restrictive · 1c1c9f8f
      Christof Schulze authored
       * gluon-core, gluon-client-bridge: introduce new firewall zone: local_client
       * gluon-core: put clients in local_client zone, introduce drop-zone,
         set dns-rules and zones
       * gluon-respondd: allow respondd on mesh
       * gluon-status-page-api: allow http input on mesh and client
      1c1c9f8f
  15. Aug 11, 2017
  16. Jul 25, 2017
  17. Jul 19, 2017
  18. May 12, 2017
  19. Apr 27, 2017
  20. Apr 12, 2017
    • Matthias Schiffer's avatar
      gluon-mesh-batman-adv: refactor interface management · e45c3033
      Matthias Schiffer authored
      We now create bat0 and primary0 independently of the lower mesh interfaces,
      making the whole setup a lot more robust. In particular:
      
      - we can't accidentially destroy primary0 because of concurrent setup and
        teardown runs of different interfaces
      - bat0 will always exist, even when no mesh interfaces are up (e.g. no link
        on wired mesh)
      - interfaces going down and up again will never tear down the whole of
        batman-adv
      - we can enable and disable bat0 independently of the lower interface
        states
      e45c3033
    • Matthias Schiffer's avatar
      gluon-mesh-batman-adv-*: unify into a single source package · 4ca67dcc
      Matthias Schiffer authored
      For simplicity, we don't use different MTUs for compat 14 and 15 anymore,
      there's no harm in using 1532 for batman-adv-legacy as well.
      4ca67dcc
Loading