[ZBXNEXT-7520] Template for OPNsense Created: 2022 Feb 23 Updated: 2024 Apr 10 Resolved: 2022 Sep 12 |
|
Status: | Closed |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | Templates (T) |
Affects Version/s: | 6.0.0 |
Fix Version/s: | 6.0.8rc1, 6.2.2rc1, 6.4.0alpha1, 6.4 (plan) |
Type: | New Feature Request | Priority: | Major |
Reporter: | Marco Hofmann | Assignee: | Natalija Burisina (Inactive) |
Resolution: | Fixed | Votes: | 4 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Attachments: |
![]() |
||||
Issue Links: |
|
||||
Team: | |||||
Sprint: | Sprint 90 (Jul 2022), Sprint 91 (Aug 2022), Sprint 92 (Sep 2022) | ||||
Story Points: | 2 |
Description |
Similiar to Since pfSense has gone more of a commercial route, with new features only being added for paying customers, quite different from the approach Zabbix and OPNsense are following, same software for everyone, paying only for support, which was the same with pfSense in the past ;-( many pfSense users switch over to OPNsense. https://opnsense.org/ |
Comments |
Comment by Jonathan Woodard [ 2022 Mar 14 ] |
I would be happy to help work on a template. I already have one based on their API calls. Would be happy to collaborate on this. |
Comment by Jonathan Woodard [ 2022 Mar 14 ] |
Part of the problem is the loss of BEGEMOT-PF-MIB when the switch to NET-SMNP was made.... https://forum.opnsense.org/index.php?topic=19753.msg94821#msg94821 |
Comment by Marco Hofmann [ 2022 Aug 08 ] |
I see this has been marked as resolved, but the template is not part of git, yet? |
Comment by Aleksandre Sebiskveradze [ 2022 Aug 09 ] |
starko Hello, yes at the moment template is on internal review stage, should be ready for next release ± 22.08. |
Comment by Natalija Burisina (Inactive) [ 2022 Sep 01 ] |
Documentation updated:
|
Comment by Marco Hofmann [ 2022 Sep 06 ] |
IMHO this template has an error asebiskveradze and nburisina in the default macros, I just tested it with a real OPNsense Firewall (official hardware). The default macros {$NET.IF.IFNAME.MATCHES} & {$NET.IF.IFNAME.NOT_MATCHES} have values set, that prevent any interface from ever being discovered. I assume that you maybe missed correcting this after developing the template. I'll attach a real world JSON from our OPNsense hardware, as an example for you to correct this.opnsense.net.if.discovery.json.txt |
Comment by Aleksandre Sebiskveradze [ 2022 Sep 06 ] |
starko Thank you for pointing, we'll check everything. |