Hi all,i have a use-case where 18+ locations needs to be connected to their local DSL connection for white proxy internet usage. A Firewall like OpnSense should work as a WebProxy for all the users on site. In Future maybe the guest-wifi-coupon solution will be added for guests. This locations are connected to each other through MPLS but the standard internet browser traffic should not go via main location due to bandwith limitations when everybody is streaming ;-) So means, 18+ OpnSense's needs to be managed cenralized and with automated roll-outs of their configs.Quote from: Schroeffu on April 29, 2018, 02:59:36 pmIs the API ready to use to configure OpnSense after installation? In that case an ansible playbook can do it. A CLI is easyier but a fully working API will do it too.The API is available for some core things (captive portal, proxy, ips, static routes) and most plugins. Most things in core is not API capable. If the page you open has the "/ui" prefix, there is very likely an API behind.Quote from: Schroeffu on April 29, 2018, 02:59:36 pmIf not, whats the way to configure & manage 18+ OpnSense Installations? For sure i dont want click through 18+ WebUIs for any change.. ;-)API if possible, generate and upload the config.xml, edit config.xml remotely and update the services using a cron job or use something like selenium.Quote from: Schroeffu on April 29, 2018, 02:59:36 pmSo, whats the best practice here :-)?If possible, use the API - it is the most simple way to work (single HTTP request).
Is the API ready to use to configure OpnSense after installation? In that case an ansible playbook can do it. A CLI is easyier but a fully working API will do it too.
If not, whats the way to configure & manage 18+ OpnSense Installations? For sure i dont want click through 18+ WebUIs for any change.. ;-)
So, whats the best practice here :-)?
There is no API documentation. You can find the endpoints and how to use them with the network tab of the developer tools of the browser.