Skip to content
Snippets Groups Projects
Select Git revision
  • 8c4403ba115f5901203a069ea52c03458b9c5fbd
  • experimental
  • master
  • v2021.1.2-ffs
  • v2021.1.1-ffs
  • nrb/gluon-master-cpe510
  • v2021.1-ffs
  • v2020.2.3-ffs
  • nrbffs/fastd-remove-delay
  • v2020.2.2-ffs
  • v2020.2.1-ffs
  • v2020.2-ffs
  • v2020.2.x
  • v2020.1.3-ffs
  • v2020.1.1-ffs
  • v2020.1-ffs
  • v2019.1.2-ffs
  • v2019.1.1-ffs
  • nrb/test-radv-filter
  • v2019.1-ffs
  • nrbffs/netgear-ex6120
  • v2021.1.2-ffs0.2
  • v2021.1.2-ffs0.1
  • v2021.1.1-ffs0.4
  • v2021.1.1-ffs0.3
  • v2021.1.1-ffs0.2
  • v2021.1.1-ffs0.1
  • v2021.1-ffs0.1
  • v2020.2.3-ffs0.3
  • v2020.2.3-ffs0.2
  • v2020.2.3-ffs0.1
  • v2020.2.2-ffs0.1
  • v2020.2.1-ffs0.1
  • v2020.2-ffs0.1
  • v2020.2
  • v2020.2.x-ffs0.1
  • v2020.1.3-ffs0.1
  • v2020.1.1-ffs0.1
  • v2020.1-ffs0.1
  • v2019.1.2-ffs0.1
  • v2019.1.1-ffs0.1
41 results

respondd.c

Blame
  • Forked from firmware / FFS Gluon
    Source project has a limited visibility.
    • Matthias Schiffer's avatar
      8c4403ba
      gluon-client-bridge, gluon-mesh-batman-adv-core: switch roles of br-client and... · 8c4403ba
      Matthias Schiffer authored
      gluon-client-bridge, gluon-mesh-batman-adv-core: switch roles of br-client and local-node interfaces
      
      MAC and IP addresses are switched. This makes the gluon-client-bridge
      package more useful for different routing protocols that don't need a
      unique address on the client bridge.
      
      As a side effect, gluon-radvd is now using the next-node address, which had
      been considered before, but was dismissed to avoid having gluon-radvd
      depend on gluon-next-node and gluon-mesh-batman-adv. This will be useful
      for announcing default routes via gluon-radvd.
      
      One downside is that this introduces a minor dependency on batman-adv in
      gluon-respondd: the hotplug script that checked for the client interface
      before will now check for local-node. This doesn't really matter: for mesh
      protocols without a local-node interface, the check will do nothing (which
      makes sense, as there is no interface to bind to for mesh-wide respondd).
      gluon-client-bridge, gluon-mesh-batman-adv-core: switch roles of br-client and...
      Matthias Schiffer authored
      gluon-client-bridge, gluon-mesh-batman-adv-core: switch roles of br-client and local-node interfaces
      
      MAC and IP addresses are switched. This makes the gluon-client-bridge
      package more useful for different routing protocols that don't need a
      unique address on the client bridge.
      
      As a side effect, gluon-radvd is now using the next-node address, which had
      been considered before, but was dismissed to avoid having gluon-radvd
      depend on gluon-next-node and gluon-mesh-batman-adv. This will be useful
      for announcing default routes via gluon-radvd.
      
      One downside is that this introduces a minor dependency on batman-adv in
      gluon-respondd: the hotplug script that checked for the client interface
      before will now check for local-node. This doesn't really matter: for mesh
      protocols without a local-node interface, the check will do nothing (which
      makes sense, as there is no interface to bind to for mesh-wide respondd).
    roland 0 B