Data scope
Request parameters, retrieved NAT rules and rule-creation data. NAT rules are resources inside OPNsense.
17 / Integrations
BAS interacts with network rules
A separate routine calls the OPNsense API to retrieve and create NAT rules in an agreed workflow.
Discuss a custom integration ↗
Conceptual illustration. See the interaction diagram for data scope and directions.
The task
BAS × OPNsense API
An accounting routine needs a programmatic interface for defined network infrastructure operations.
Interaction diagram
BAS × OPNsense API
Selected connectionBAS routine → OPNsense API
Request existing rules
Architecture
Technical description
A BAS routine makes API requests to OPNsense. Reading existing NAT rules and creating a rule are separate scenarios.
Our implementation
Custom API requests, rule retrieval and a creation procedure. Editing, deletion and complete firewall administration are outside the described scope.
Requirements for a new project
Agree permitted operations and access parameters. The website does not call a production API or display real addresses and rules.
What we developed
Custom OPNsense API routine
- Developed OPNsense API requests.
- Implemented retrieval of NAT rules.
- Added a rule-creation procedure.
Implementation result
Implementation result
BAS has a separate programmatic tool for the agreed network-rule workflow.
Discuss your task ↗Related projects
02 / Integrations
BAS product master data in a warehouse management system
Products, barcodes, warehouses and classifications are sent to WMS through a custom HTTP/JSON integration.
Project details ↗
03 / Integrations
Controlled message exchange through RabbitMQ
Sending, reading and processing incoming messages, with a separate option to resend batches, in custom BAS routines.
Project details ↗NEXT STEP
Discuss your task
Describe your current system, task and intended result. We will agree the scope and prepare a proposal.
[email protected] ↗Contact us on Telegram ↗Vyvick Engineering on Telegram ↗