Zabbix Documentation 4.4

2.23.04.04.2 (current)In development:4.4 (devel)Unsupported:1.82.02.43.23.4

User Tools

Site Tools


manual:appendix:config:zabbix_proxy

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
manual:appendix:config:zabbix_proxy [2019/05/31 07:40]
martins-v fixing copy-paste error
manual:appendix:config:zabbix_proxy [2019/07/05 07:35] (current)
akozlovs
Line 65: Line 65:
 | StatsAllowedIP| no |  |  |List of comma delimited IP addresses, optionally in CIDR notation, or DNS names of external Zabbix instances. Stats request will be accepted only from the addresses listed here. If this parameter is not set no stats requests will be accepted.\\ If IPv6 support is enabled then '​127.0.0.1',​ '::​127.0.0.1',​ '::​ffff:​127.0.0.1'​ are treated equally and '::/​0'​ will allow any IPv4 or IPv6 address. '​0.0.0.0/​0'​ can be used to allow any IPv4 address.\\ Example: StatsAllowedIP=127.0.0.1,​192.168.1.0/​24,::​1,​2001:​db8::/​32,​zabbix.example.com\\ This parameter is supported since Zabbix 4.2.0. ​ | | StatsAllowedIP| no |  |  |List of comma delimited IP addresses, optionally in CIDR notation, or DNS names of external Zabbix instances. Stats request will be accepted only from the addresses listed here. If this parameter is not set no stats requests will be accepted.\\ If IPv6 support is enabled then '​127.0.0.1',​ '::​127.0.0.1',​ '::​ffff:​127.0.0.1'​ are treated equally and '::/​0'​ will allow any IPv4 or IPv6 address. '​0.0.0.0/​0'​ can be used to allow any IPv4 address.\\ Example: StatsAllowedIP=127.0.0.1,​192.168.1.0/​24,::​1,​2001:​db8::/​32,​zabbix.example.com\\ This parameter is supported since Zabbix 4.2.0. ​ |
 | Timeout| no | 1-30 |3 |Specifies how long we wait for agent, SNMP device or external check (in seconds). | | Timeout| no | 1-30 |3 |Specifies how long we wait for agent, SNMP device or external check (in seconds). |
-| TLSAccept| yes, if TLS certificate or PSK parameters are defined (even for //​unencrypted//​ connection),​ otherwise no |  | |What incoming connections to accept from Zabbix server. Used for a passive proxy, ignored on an active proxy. Multiple values can be specified, separated by comma: \\ //​unencrypted//​ - accept connections without encryption (default) \\ //psk// - accept connections with TLS and a pre-shared key (PSK) \\ //cert// - accept connections with TLS and a certificate\\ This parameter is supported since Zabbix 3.0.0. ​ |+| TLSAccept| yes for passive proxy, if TLS certificate or PSK parameters are defined (even for //​unencrypted//​ connection),​ otherwise no |  | |What incoming connections to accept from Zabbix server. Used for a passive proxy, ignored on an active proxy. Multiple values can be specified, separated by comma: \\ //​unencrypted//​ - accept connections without encryption (default) \\ //psk// - accept connections with TLS and a pre-shared key (PSK) \\ //cert// - accept connections with TLS and a certificate\\ This parameter is supported since Zabbix 3.0.0. ​ |
 | TLSCAFile| no |  | |Full pathname of a file containing the top-level CA(s) certificates for peer certificate verification,​ used for encrypted communications between Zabbix components.\\ This parameter is supported since Zabbix 3.0.0. ​ | | TLSCAFile| no |  | |Full pathname of a file containing the top-level CA(s) certificates for peer certificate verification,​ used for encrypted communications between Zabbix components.\\ This parameter is supported since Zabbix 3.0.0. ​ |
 | TLSCertFile| no |  | |Full pathname of a file containing the proxy certificate or certificate chain, used for encrypted communications between Zabbix components.\\ This parameter is supported since Zabbix 3.0.0. ​ | | TLSCertFile| no |  | |Full pathname of a file containing the proxy certificate or certificate chain, used for encrypted communications between Zabbix components.\\ This parameter is supported since Zabbix 3.0.0. ​ |
-| TLSConnect| yes, if TLS certificate or PSK parameters are defined (even for //​unencrypted//​ connection),​ otherwise no |  | |How the proxy should connect to Zabbix server. Used for an active proxy, ignored on a passive proxy. Only one value can be specified: \\ //​unencrypted//​ - connect without encryption (default) \\ //psk// - connect using TLS and a pre-shared key (PSK) \\ //cert// - connect using TLS and a certificate\\ This parameter is supported since Zabbix 3.0.0. ​ |+| TLSConnect| yes for active proxy, if TLS certificate or PSK parameters are defined (even for //​unencrypted//​ connection),​ otherwise no |  | |How the proxy should connect to Zabbix server. Used for an active proxy, ignored on a passive proxy. Only one value can be specified: \\ //​unencrypted//​ - connect without encryption (default) \\ //psk// - connect using TLS and a pre-shared key (PSK) \\ //cert// - connect using TLS and a certificate\\ This parameter is supported since Zabbix 3.0.0. ​ |
 | TLSCRLFile| no |  | |Full pathname of a file containing revoked certificates.This parameter is used for encrypted communications between Zabbix components.\\ This parameter is supported since Zabbix 3.0.0. ​ | | TLSCRLFile| no |  | |Full pathname of a file containing revoked certificates.This parameter is used for encrypted communications between Zabbix components.\\ This parameter is supported since Zabbix 3.0.0. ​ |
 | TLSKeyFile| no |  | |Full pathname of a file containing the proxy private key, used for encrypted communications between Zabbix components.\\ This parameter is supported since Zabbix 3.0.0. ​ | | TLSKeyFile| no |  | |Full pathname of a file containing the proxy private key, used for encrypted communications between Zabbix components.\\ This parameter is supported since Zabbix 3.0.0. ​ |