Skip to content
Snippets Groups Projects
Forked from ffbs / ffbs-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).