Bonjour!
I'd like to do the same as you, limit my config.json and use only the GUI when possible. What left do you have to configure in the GUI if I were to use your config file?
I took a look at your config.json and it looks like you don't have IPv6 set up. Are you not using IPv6, or did you set it up through the GUI as well?
Je parle un peu de français, donc si vous comprends pas mon question, je vais essayer traduire en francais
Merci beaucoup !
My config file contains only what is not available in the controller UI, which are
- dhcp options for the 832 VLAN (aka "client-option") and the QoS setting (aka "egress-qos")
- the complete 840 VLAN definition (as the controller UI supports only one WAN VLAN)
- the igmp proxy settings (which are totally absent in the UI)
All other settings are defined via the controller UI, and specifically the WAN VLAN (which is very usefull for the defining the right WAN interface for several services). Nothing more.
With this setting, you can obviously define also the DynDNS, VPN, specific firewall rules (when needed) directly into the controller UI. No conflict with the json, it works !
Regarding IPv6, as the Orange specific options are not supported at all by neither the controller nor the USG (nothing available at the json level), I give up as I consider the dibbler workaround not persistent/reliable when regularly updating the controller software and USG firmware.