Switch to next generation routing protocol aka babel

[spolack]

Lets get this topic waiting for too long started

• Craft target configuration
• Identify conceptional differences between old and new Scheme, Design and implement migration procedure
• Implement forward and reverse name resolution - to lookup IPv4, IPv6 Loopback Addresses and advertised services
• Implement OLSR-Like Status Page in LuCi which is publically accessible
• Publish neighborships on Hopglass
• Find mechanism to resolve neighbor link local addresses to neighbors. Something like lldp?

[Noki]

From an organizational point of view, this should probably be the migration process:

• Implement to give out IPv6 subnets with "IP assignment (standard/wizard)" in the config wizard (babel: give out IPv6 subnets with "IP assignment (standard/wizard)" config.berlin.freifunk.net#75)
• Add an IPv6 subnets for all existing nodes that are currently IPv4 only and notify those users via E-Mail (babel: add IPv6 subnets for all existing nodes that are currently IPv4 only config.berlin.freifunk.net#76)
• Add an API route to the IP assignment that allows fetching all IPs of a node (babel: add API route to ip assignment that returns all IPs based on one IP of the node config.berlin.freifunk.net#77)
• Integrate IPv6 via Babel into the next falter release (e.g. 1.2.3), and add an auto-config feature that fetches and assigns the newly assigned IPv6 addresses via an API call to IP address assignment (provide an IPv4 address assigned to the node to get the IPv6 subnet)
• Announce a migration date and process for also switching the IPv4 routing protocol over to Babel
• Release a new falter release (e.g. 1.2.4) that can autoupdate via IPv6 (already Babel at that point) and migrates all nodes with enabled auto update within a couple of hours in a single night.

[akira25]

Really important point from my view:

• implement network-wide, decentralized service announcement/discovery