Skip to content

Gluon domain migration

Jan-Tarek Butt requested to merge gluon-domain-migration into master

This MR migrates our hoods into gluons domain template.

To Do points:

  • migrate default

  • migrate landkreis-steinfurt

  • migrate landkreis-friesland

  • migrate oldenburg

  • migrate osnabrueck

  • migrate butjadingen

  • migrate landkreis-wittmund

  • migrate rastede

  • migrate landkreis-vechta

  • migrate delmenhorst

  • migrate landkreis-osnabrueck

  • migrate leer

  • migrate landkreis-emsland

  • migrate wilhelmshaven

  • migrate lohne

  • migrate landkreis-wesermarsch

  • migrate suedost

  • migrate ibbenbueren

  • migrate landkreis-cloppenburg

  • migrate grafschaft-bentheim

  • migrate bad-iburg

  • migrate osnabrueck2

  • migrate aurich

  • migrate oldenburg2

  • migrate tossens

  • Fastd Traffic limitation parameters missing in configMode.

  • Ensure fastd use secure mode as default.

  • Integrate polygon defined hoods in new hood layout

  • prepare hoodselector for older gluon version.

  • backport VPN abstraction layer

  • backport gluon-configmode-osm

  • integrate geolocator

  • make sure that update while in a hood leads to the correspondig domain. if it is not taken care of, every router will be in domain 'default' after update

Edited by Jan-Tarek Butt

Merge request reports