Switch back roles of br-client and local-node interfaces
When preparing the migration from macvlan to veth for local-node, MAC address conflicts occurred as some ports of br-client had the same address as local-node. Reverting the roles of both interfaces fixes this. By default, br-client is left as an interface without addresses and firewall rules that drop everything, so the bridge is used to connect its ports only. gluon-mesh-batman-adv-core changes this to the usual set of addresses and firewall rules.
Showing
- package/gluon-alfred/luasrc/lib/gluon/upgrade/500-enable-alfred 1 addition, 1 deletion...e/gluon-alfred/luasrc/lib/gluon/upgrade/500-enable-alfred
- package/gluon-client-bridge/luasrc/lib/gluon/upgrade/300-gluon-client-bridge-network 25 additions, 27 deletions.../luasrc/lib/gluon/upgrade/300-gluon-client-bridge-network
- package/gluon-client-bridge/luasrc/lib/gluon/upgrade/310-gluon-client-bridge-local-node 17 additions, 3 deletions...asrc/lib/gluon/upgrade/310-gluon-client-bridge-local-node
- package/gluon-mesh-batman-adv-core/files/lib/gluon/radvd/arguments 1 addition, 1 deletion...luon-mesh-batman-adv-core/files/lib/gluon/radvd/arguments
- package/gluon-mesh-batman-adv-core/files/lib/gluon/respondd/client.dev 1 addition, 1 deletion...-mesh-batman-adv-core/files/lib/gluon/respondd/client.dev
- package/gluon-mesh-batman-adv-core/luasrc/lib/gluon/upgrade/320-gluon-mesh-batman-adv-core-client-bridge 39 additions, 7 deletions...luon/upgrade/320-gluon-mesh-batman-adv-core-client-bridge
- package/gluon-mesh-batman-adv-core/luasrc/lib/gluon/upgrade/330-gluon-mesh-batman-adv-core-local-node 0 additions, 51 deletions...b/gluon/upgrade/330-gluon-mesh-batman-adv-core-local-node
- package/gluon-mesh-batman-adv-core/src/respondd.c 1 addition, 1 deletionpackage/gluon-mesh-batman-adv-core/src/respondd.c
Loading
Please register or sign in to comment