Messages

Thanks for your kind words and visibility on the twitter feed. In the mean time I installed a 18.1-RC2 VM to play around with instead of my live environment :)

I'm slowly working my way through the api commands, implementing the low hanging fruit first: like the os-arp-scan plugin and new routes api.
Since Quagga is depricated in 18.1 the api percentage mentioned in my OP is probably a bit higher than estimated. I'm not sure which OPNsense plugins are most popular to implement next. Any thoughts?

There's also a need to implement some automated unit testing, because perfoming all tests manually on a new release is a chore and that time is better spend coding. And I'll be doing some testing in PowerShell Core 6.0 on linux to get a feel for what that's like and identify hurdles there.

The changes will be pushed to the /dev/ branch for the time being. I'll post back when there's more progress to report.

I am not experienced with PS but I can help you with the plugins I wrote. I'll have a deeper look :)

Thanks :D Would you mind sharing the names of some plugins, I'll have a look to implement them into the PS Module asap!

You can go to a mirror site and then go up one level to releases. There you'll find a 18.1 folder like this one:
http://mirror.ams1.nl.leaseweb.net/opnsense/releases/18.1/

In 18.1-RC2 the new page ui/routes/ show column header 'Beschreibung' instead of 'Description' in the English UI.
It's just a small detail I noticed while exploring the new RCs.

Of course if there is any security concern, then such a feature should not be implemented!

But ideas may give rise to even better ideas. :-)

What you can do is setup a small client or single board computer that has the required SMS features and talk to your OPNsense server via the REST api. Restarting services or your firewall should be quite trivial to automate in a script.

One of the major advantages that guided me towards OPNsense is its api framework. In my quest to learn more about the OPNsense REST api, I decided to combine it with my PowerShell learning path and turn this project into an OPNsense PowerShell Module. It turns out that these two work quite well together and I currently have a development preview working with about 25% of the api call's available in PowerShell. There is still a lot of room for improvement though, but the foundation is there.

I wanted to check with the users on this forum if there is any interest in an OPNsense PowerShell Module?
I made the source code available on github, in the spirit of the OPNsense project so users can test, review and contribute. It even has a wiki  :)

For Example:

Code Select Expand

# Connect to an OPNsense
Connect-OPNsense -Url 'https://opnsense.localdomain:8080' -Credential $apiCred -WebCredential $webCred -Verbose -Debug

# Get the config.xml
$xml = Backup-OPNsenseConfig -RRDdata

# Add some packages
Install-OPNsensePackage -Name 'unixODBC','xen-guest-tools' -Verbose

# Install updates & Reboot
Update-OPNsense -Verbose

Now that PowerShell Core 6.0 is available cross platform it is possible to run PowerShell scripts on Windows, Linux and MacOS.

Even if you want to use another scripting language, this module can help you learn the api as all of the cmdlets let you use the -Verbose and -Debug parameters so you can investigate which api calls are made in the background using which parameters.

Of course any feedback is very much appreciated.

Best regards,
/fvanroie