zabbix packages - update to 3.0 #126
Conversation
|
|
|
@dbaio can you please rebase your fork and remove changes to net-mgmt/zabbiz* ports? Keep only changes to pfSense specific ports please |
|
Hi @rbgarga, It's done. Thanks. |
| @@ -250,4 +298,14 @@ EOF; | |||
| conf_mount_ro(); | |||
| } | |||
|
|
|||
| // Based on openvpn_add_keyfile() function | |||
| function zabbix_agent_add_keyfile(& $data, $directive) { | |||
There was a problem hiding this comment.
Why is $data a reference here if it's not modified inside the function?
|
Hi Guys, We desperately need to get the Zabbix Proxy working so we can forward SNMP traps back to a Zabbix server in a Colo. I've engaged the original package writer, but he doesn't seem interested. I've got $1000 that I'm willing to throw at this, if it will help. network at montgomerytech dot net if you'd like to claim the prize. Thanks in advance and happy new year! CT |
|
@MontgomeryTechnologies I am not interest on a bounty. What version of zabbix (server) are you running? This package is following zabbix 3.0 LTS Unfortunately zabbix proxy and server needs to be on the same version to work properly. And I think is better you open a thread on pfSense forum. Regards. |
|
Danilo,
Thanks for the response!
We are running Zabbix version 3.0.3 The version of proxy package and zabbix
are compatible. Everything is working except SNMP traps being sent to
zabbix from pfsense proxy.
Make sense?
FYI
[image: Inline image 1]
[image: Inline image 2]
Eli Fogel
NOC Engineer
[image: cid:[email protected]]
Technology Manager for Premier Commercial Buildings Nationally
*Office **(844) 824.0100 <%28844%29%20824.0100> *| *Direct 415.918.2312
<+415.918.2312>* | efogel <http://goog_1187986303>*@montgomerytech.net
<http://montgomerytech.net>*
…On Tue, Jan 3, 2017 at 11:06 AM, Danilo G. Baio ***@***.***> wrote:
@MontgomeryTechnologies <https://github.com/MontgomeryTechnologies> I am
not interest on a bounty.
What version of zabbix (server) are you running?
This package is following zabbix 3.0 LTS
http://www.zabbix.com/img/cycle/zabbix-standard-and-
zabbix-lts-release-life-cycle_v3.2.png
Unfortunately zabbix proxy and server needs to be on the same version to
work properly.
And I think is better you open a thread on pfSense forum
<https://forum.pfsense.org/index.php?board=15.0>.
Regards.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#126 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AXvvS34HrQAbnScQrmMFcqtvUCa9PdDAks5rOpxJgaJpZM4IZuzH>
.
|
|
1) Right now on the Zabbix-Proxy-LTS package that PFSense uses there is a
service that is being used to send snmp data called 'bsnmp'
2) This service will not pass device snmp traps (port 162) through the
proxy package loaded on PFSense to the zabbix server. All other snmp data
is being sent.
3) Zabbix support has verified that this 'bsnmp' service will not do the
functions required for traps to be sent through the proxy agent.
4) The service that needs to be used is 'snmptrapd' which is part of
net-snmp tools.
Is there any way that this service 'snmptrapd' could be loaded when the
package is loaded onto a PFSense box? That way the snmp traps generated
from local network devices can be sent through the proxy agent to the
zabbix server?
Hope this explains it. Please let me know if you have any other questions.
Thank you so much!
Eli Fogel
NOC Engineer
[image: cid:[email protected]]
Technology Manager for Premier Commercial Buildings Nationally
*Office **(844) 824.0100 <%28844%29%20824.0100> *| *Direct 415.918.2312
<+415.918.2312>* | efogel <http://goog_1187986303>*@montgomerytech.net
<http://montgomerytech.net>*
On Tue, Jan 3, 2017 at 11:11 AM, Eli Fogel <[email protected]>
wrote:
… Danilo,
Thanks for the response!
We are running Zabbix version 3.0.3 The version of proxy package and
zabbix are compatible. Everything is working except SNMP traps being sent
to zabbix from pfsense proxy.
Make sense?
FYI
[image: Inline image 1]
[image: Inline image 2]
Eli Fogel
NOC Engineer
[image: ***@***.***
Technology Manager for Premier Commercial Buildings Nationally
*Office **(844) 824.0100 <%28844%29%20824.0100> *| *Direct 415.918.2312
<+415.918.2312>* | efogel ***@***.***
<http://montgomerytech.net>*
On Tue, Jan 3, 2017 at 11:06 AM, Danilo G. Baio ***@***.***>
wrote:
> @MontgomeryTechnologies <https://github.com/MontgomeryTechnologies> I am
> not interest on a bounty.
>
> What version of zabbix (server) are you running?
>
> This package is following zabbix 3.0 LTS
> http://www.zabbix.com/img/cycle/zabbix-standard-and-zabbix-
> lts-release-life-cycle_v3.2.png
>
> Unfortunately zabbix proxy and server needs to be on the same version to
> work properly.
>
> And I think is better you open a thread on pfSense forum
> <https://forum.pfsense.org/index.php?board=15.0>.
>
> Regards.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#126 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AXvvS34HrQAbnScQrmMFcqtvUCa9PdDAks5rOpxJgaJpZM4IZuzH>
> .
>
|
|
I have had a chance to test 2.4 Beta on a test PFSense box in our lab. When I first installed the Beta version of software we were not getting any traps. But the snmptrapd service was running on pfsense box and verified. After working with Zabbix and Danilo for the last month we have configured the PFSense proxy to pass traps to Zabbix in real time. Port status, coldstart, authentication etc. Amongst a few config hurdles we discovered that everything on PFSense was configured correctly. A little more digging proved that the settings in the SNMP Trap GUI in PFSense were not being applied. The community names in the GUI were being overwritten by snmptrapd.conf file on PFSense. In the file the default public community is being applied. As soon as we modified this file to match our community name traps starting passing. My summary and feedback is as follows: The SNMP Trap GUI settings for community should be applied to the snmptrapd.conf file. Instead of going into the file manually, all changes made in the GUI should be final and applied across the board. Thanks for reading. And thank you Danilo for all of your efforts and hard work. |
Upstream Enhancements: * Detect future Intel AVX/AMX features #128 * Add support for Tiger Lake and Sapphire rapids Intel microarchitectures #127 * Update features for AArch64 to Linux 5.8 #126 * AVX-512 FMA count detection #120 Port Changes: * Add license file * Change libcpu_features to a shared library PR: 253037 Submitted by: yuri@
ChangeLog: Bacula-Web 8.6.1 (October 19th 2022) Changelog General User will stay on current page when switching to another catalog (see Fixed Bacula catalog selector Using several Bacula catalog, the catalog selector was broken for some pages (see #120) Web browser will not ask a form submission while moving back from Job logs report page (see #30) Fixed how pagination count rows per page (see #123) Bump Composer dependencies to latest version Fixed pagination next button (see #125) Link to official documentation is now available from top navigation bar Jobs report Fixed pagination not using applied filters and options (see #122) Job endtime filter is now working as expected Ordering options are kept while using pagination (see #122) You can reach Job files report from Jobs report page from now (see #126) Job logs report More job information are now displayed (see #124) Pools report Fixed the Volumes button which now list volumes in the right pool (see Volumes report Fixed pagination not using applied filters and options (see #122) Settings Removed extra flash message which appear when a user is created Fixed bug(s) (filtered) job overview page New feature(s)
ChangeLog: Bacula-Web 8.6.1 (October 19th 2022) Changelog General User will stay on current page when switching to another catalog (see Fixed Bacula catalog selector Using several Bacula catalog, the catalog selector was broken for some pages (see #120) Web browser will not ask a form submission while moving back from Job logs report page (see #30) Fixed how pagination count rows per page (see #123) Bump Composer dependencies to latest version Fixed pagination next button (see #125) Link to official documentation is now available from top navigation bar Jobs report Fixed pagination not using applied filters and options (see #122) Job endtime filter is now working as expected Ordering options are kept while using pagination (see #122) You can reach Job files report from Jobs report page from now (see #126) Job logs report More job information are now displayed (see #124) Pools report Fixed the Volumes button which now list volumes in the right pool (see Volumes report Fixed pagination not using applied filters and options (see #122) Settings Removed extra flash message which appear when a user is created Fixed bug(s) (filtered) job overview page New feature(s)
zabbix packages - update to 3.0
Upgrade for zabbix agent and proxy packages
Pull TLS commit (cherry-pick) from masterChange web gui to TLS related options