Messages

A few weeks ago we posted "a Terraform module for OPNsense on Digital Ocean" and we are now following up with the same thing for creating Amazon Machine Images (AMI) for EC2 instances on AWS.
- https://github.com/verbnetworks/terraform-aws-opnsense-image
- https://registry.terraform.io/modules/verbnetworks/opnsense-image/aws

This now means you are free to create multi compute-provider private networks, allowing you to establish private networks between providers and shift workloads to more cost effective providers/regions/zones as appropriate.

Or connect your onsite OPNsense hosts with OPNsense instances running in your cloud provider(s) of choice to create your own inter-office transit links.

Read more about our OPNsense stuff here:-
- https://verbnetworks.com/projects/devops-for-opnsense/

N

Hi,

Anyone wanting to get OPNsense running on Digital Ocean will find this Terraform module helpful:-
- https://github.com/verbnetworks/terraform-digitalocean-opnsense-image
- https://registry.terraform.io/modules/verbnetworks/opnsense-image/digitalocean

The module is designed to create a Digital Ocean Droplet snapshot-image that can subsequently be used to start an OPNsense instance within Digital Ocean.

Of particular note is the support for the Digital Ocean (OpenStack based) approach to providing Droplets their seed data, including public-IPv4, public-IPv6, private-IPv4, root-sshkey and user-data which is all be parsed and injected into the OPNsense /conf/config.xml file at boot time. This allows the resulting OPNsense image to be used in Terraform devops automation situations.

By adding appropriate User Data to a Droplet when establishing it becomes possible to fetch an external confg.xml which will be loaded at startup thus making devops automated OPNsense in Digital Ocean possible.

Love to hear feedback, suggestions and the like.

... currently working on AWS and Azure implementations next with a view to making automated multi-cloud private network infrastructure possible.

N

I'm working on putting together an OPNsense plugin at the moment and have run into what would otherwise seem like a trivial problem to resolve if I could observe what the OPNsense web-app framework is doing under the covers.

I've tried switching debug=true in opnsense/mvc/app/config/config.php but I can't really see where the debug or logging messages are going or where to find them.

Could anyone point me in the right direction?