The scenario starts by setting up a new node. So, you flashed your router with the amazing HwmnOS and you need setup the switch, interfaces, babel etc. In this process there are some mandatory steps that depend on node information, especially on the assigned ip range of the node, making it impossible to solve it with shipped static configuration. So a script for dynamic configuration is needed.
Step 1: Configure your lan interface
You expect that your lan interface should use portion of the assigned subnet. Also, best practices tell us to assign the first IP address to the router. For the mean user the lan will never have more than 20 parallel devices, doubling it (being on the safe side) and rounding it to a power of 2 leads to 64 maximum hosts. Eventually the lan interface could be configured as 10.X.X.1/26.
Step 2: Configure wireless interfaces
In both cases where a HwmnOS is installed on mikrotik or on ubiquity feeders (for routing purposes) we need to declare the peering interface (neighbor connection). In some tests (no reference available atm) we could assign IP address from the peer's local subnet per side (so two different subnet on the link) and babel can do the trick to advertise routes. For the purpose of subnet assigning on these interfaces a simple strategy could be followed. Each interface is assigned the first unused /30 subnet starting from the end of the nodes authoritative range. In the case of mikrotik, it would be nice to have a switch configuration and a vlan assigned per peer interface.
Step 3: Babeld configuration
Babel is pretty straightforward to configure and the majority of the configuration (filters) is static. The only exception is the advertisement interface which depend on the previous step. Here an extra step is needed, to declare appropriate peer interfaces that babel must run on.
The scenario starts by setting up a new node. So, you flashed your router with the amazing HwmnOS and you need setup the switch, interfaces, babel etc. In this process there are some mandatory steps that depend on node information, especially on the assigned ip range of the node, making it impossible to solve it with shipped static configuration. So a script for dynamic configuration is needed.
Step 1: Configure your lan interface
You expect that your lan interface should use portion of the assigned subnet. Also, best practices tell us to assign the first IP address to the router. For the mean user the lan will never have more than 20 parallel devices, doubling it (being on the safe side) and rounding it to a power of 2 leads to 64 maximum hosts. Eventually the lan interface could be configured as 10.X.X.1/26.
Step 2: Configure wireless interfaces
In both cases where a HwmnOS is installed on mikrotik or on ubiquity feeders (for routing purposes) we need to declare the peering interface (neighbor connection). In some tests (no reference available atm) we could assign IP address from the peer's local subnet per side (so two different subnet on the link) and babel can do the trick to advertise routes. For the purpose of subnet assigning on these interfaces a simple strategy could be followed. Each interface is assigned the first unused /30 subnet starting from the end of the nodes authoritative range. In the case of mikrotik, it would be nice to have a switch configuration and a vlan assigned per peer interface.
Step 3: Babeld configuration
Babel is pretty straightforward to configure and the majority of the configuration (filters) is static. The only exception is the advertisement interface which depend on the previous step. Here an extra step is needed, to declare appropriate peer interfaces that babel must run on.
Feel free to add more ideas here....