Gui

so, in a nutshell, even if "in theory" a lower mtu in router interfaces would be the "right" thing to do, in practice it creates hard to debug problems that...

just to give more context, this proposal is a prerequisite to https://github.com/libremesh/lime-packages/issues/133 that issue is more epic in terms of implementation, but probably no-one would oppose merging such a wonderful...

this is the start of getting DNS "right" some notes to self: * `shared-state-dnsmasq_hosts` and `shared-state-dnsmasq_leases` have no concept of "cloud domain", and they should. both dhcp leases and dns...

now it works nicely. tested this on a virtual testbed with 12 nodes split among 4 different clouds. i spotted some quirks and added some fixes in various files.

wishlist: implement `rev-servers` as well right now, each node publishes it's own domain and ipv6 and the result is the following ``` server=/cloudA.test/fdeb:75d8:5c6d::1 server=/cloudD.test/fd30:7030:8ee3::1 server=/cloudB.test/fd54:721a:3043::1 ``` ideally, each node would...

> * [custom mtu](https://github.com/libremesh/lime-packages/blob/develop/packages/lime-proto-anygw/src/anygw.lua#L84) seems unsupported but may works automatically? according to https://openwrt.org/docs/techref/odhcpd custom mtu is now supported with option `ra_mtu`

i've spent some time (re)evaluating the possibility of using odhcpd as dhcpv6 server in libremesh (instead of dnsmasq-dhcpv6) to converge with upstream and benefit from all the progress done into...

until now, we had infrequent releases with codenames (`azeno`, next `bizono`) and no [semantic versioning](https://semver.org/) azeno had a tagged release https://github.com/vocdoni/vocdoni-node/releases/tag/v1.3.0 and there's also a branch named `release-azeno` which after...

until now, how we dealt with branches: ## master * default branch in github (i.e. `git clone https://github.com/vocdoni/vocdoni-node` pulls `master`) * all PRs are made against `master` branch * `master`...

# Proposal 1 all in all, the way we handle branches until now is aligned with "Trunk Based Development" https://www.atlassian.com/continuous-delivery/continuous-integration/trunk-based-development so i'd propose to simply rename `master` to `main` but...