New Configuration Concept

Scenarios:

• Setting up a node via tablet/phone without LAN port
• Setting up a node in an existing network environment
• Setting up a node in a hard reachable location

Possible goals, under which the config system may need redesigning (numbered for reference, not ordered importance):

1. No initial setup necessary
2. Setup via WiFi only possible
3. Avoiding "rogue" DHCP servers in config mode
4. Easier changing of settings after initial setup

Possible things to change with targeted goals in []:

• [1] Always enable mesh-vpn (remove the option in the config mode to deactivate)
• [1,2,4] Create nextnode config page:
  • Settings to move there:
    • hostname
    • location
    • bandwidth limitation
  • Security considerations:
    • Enable (re)setting the nextnode config password in config mode
    • default password? (secure by default)
    • Only allow setting nextnode config options via direct connection or via a direct neighbour
    • SSL certificate?
  • Usability considerations:
    • How to guarantee that the owner of a node is connected to his own node/the node he wants to configure when there are multiple nodes nearby?
• [1] Announce fastd public key via alfred (or alternatively, announce key servers via alfred and push to these)
• [1,3] After the initial flashing, always boot in general operating instead of config mode