123
edits
Difference between revisions of "Mesh/15 May 2018"
no edit summary
| Line 166: | Line 166: | ||
[[Category:Mesh/Minutes]] | [[Category:Mesh/Minutes]] | ||
== Special meeting on how the firmware works and how to proceed - May 15th 2018 == | |||
* Where are the builds? = | * Where are the builds? = | ||
| Line 173: | Line 173: | ||
See PR: https://github.com/sudomesh/sudowrt-firmware/pull/132 | See PR: https://github.com/sudomesh/sudowrt-firmware/pull/132 | ||
== To Do == | === To Do === | ||
'''Things to fix for nullconf build (previously zeroconf)''' | '''Things to fix for nullconf build (previously zeroconf)''' | ||
| Line 182: | Line 182: | ||
* Automated nightly builds? | * Automated nightly builds? | ||
== Where do we stand with ubiquiti 802.11ac gear? == | === Where do we stand with ubiquiti 802.11ac gear? === | ||
* Does it even have good openwrt support? | * Does it even have good openwrt support? | ||
| Line 191: | Line 191: | ||
A small script to install and configure the dependencies and get an IP from the secrets server? | A small script to install and configure the dependencies and get an IP from the secrets server? | ||
== How configuration works == | === How configuration works === | ||
Currently there are two directories in the sudowrt tree: | Currently there are two directories in the sudowrt tree: | ||
| Line 204: | Line 204: | ||
These are in turn potentially over-written by the zeroconf templates (described in the next section) which is the very last configuration step. | These are in turn potentially over-written by the zeroconf templates (described in the next section) which is the very last configuration step. | ||
== how nullconf (previously zeroconf) works == | === how nullconf (previously zeroconf) works === | ||
- `cron` checks for internet by pinging google every minute using `/opt/mesh/retrieve_ip`. | - `cron` checks for internet by pinging google every minute using `/opt/mesh/retrieve_ip`. | ||
| Line 213: | Line 213: | ||
In the template files you'll see hold-overs from `makenode` where some configs have e.g. `<% variable %>`. These used to be replaced by their appropriate values by makenode search-and-replacing them before copying them over to the node. Now the files are copied into `/etc/config/` as they are, including these unusable values, and then the values are replaced by the `/opt/mesh/zeroconf` script running `uci set` commands (`uci set` is a built-in openwrt command used to modify the files in `/etc/config/`). | In the template files you'll see hold-overs from `makenode` where some configs have e.g. `<% variable %>`. These used to be replaced by their appropriate values by makenode search-and-replacing them before copying them over to the node. Now the files are copied into `/etc/config/` as they are, including these unusable values, and then the values are replaced by the `/opt/mesh/zeroconf` script running `uci set` commands (`uci set` is a built-in openwrt command used to modify the files in `/etc/config/`). | ||
== Can we switch to IPv6 to get rid of the secrets server? == | === Can we switch to IPv6 to get rid of the secrets server? === | ||
* Maybe? We could set up 464LAT and give every home node the same IPv4 range. Then the nodes would translate from IPv4 to IPv6 and the exit node would NAT between IPv6 and IPv4 using NAT64. The software to do this is: | * Maybe? We could set up 464LAT and give every home node the same IPv4 range. Then the nodes would translate from IPv4 to IPv6 and the exit node would NAT between IPv6 and IPv4 using NAT64. The software to do this is: | ||
* TAYGA: http://www.litech.org/tayga/ | * TAYGA: http://www.litech.org/tayga/ | ||
* clatd: https://github.com/toreanderson/clatd | * clatd: https://github.com/toreanderson/clatd | ||