Zabbix over WAN

[tomras]

Wow! Thanks guys! People in here are very helpfull!

I will test the above as soon as possible, dont know if I mention it but the clients on the other network is all in active checks, so I dont think I need to open any ports on the outgoing traffic?

In my router to the zabbix server I tryed:

CLIENT 1 > port 10055 > IP to zabbix srv 192.168.1.124
In host configuration I use port 10055
and in agent config server=xxx.xxx.xxx.xxx:10055

[markclark]

Shouldn't need to open any ports for outbound traffic.

once you make any changes to the config, restart the zabbix service for the listening ports to take affect

[ingus.vilnis]

Wow! Thanks guys! People in here are very helpfull!

I will test the above as soon as possible, dont know if I mention it but the clients on the other network is all in active checks, so I dont think I need to open any ports on the outgoing traffic?

In my router to the zabbix server I tryed:

CLIENT 1 > port 10055 > IP to zabbix srv 192.168.1.124
In host configuration I use port 10055
and in agent config server=xxx.xxx.xxx.xxx:10055

It is just normal to be helpful and answer the questios of community members.

Regarding your issue, I think that you should not change anything on the router where you have your main Zabbix server. The only case would be if you have all ports closed by default, than you should open some, but that is another chapter.

Not sure if it is a good idea to simply change the ports on which you run your Zabbix agents. (More exerienced members correct me if I am wrong.) You will only mess up by diong that. Keep things simple at the beginning while you establish connection with default settinggs and then you can try to learn and modify.

Simply try the port forwarding on your router at that remote location as described in all the posts above. And note that external incoming port should not necessarily be the same as the port you use on your host in internal network. That's what that mapping is for.

Good luck!

[tomras]

It is just normal to be helpful and answer the questios of community members.

Regarding your issue, I think that you should not change anything on the router where you have your main Zabbix server. The only case would be if you have all ports closed by default, than you should open some, but that is another chapter.

Not sure if it is a good idea to simply change the ports on which you run your Zabbix agents. (More exerienced members correct me if I am wrong.) You will only mess up by diong that. Keep things simple at the beginning while you establish connection with default settinggs and then you can try to learn and modify.

Simply try the port forwarding on your router at that remote location as described in all the posts above. And note that external incoming port should not necessarily be the same as the port you use on your host in internal network. That's what that mapping is for.

Good luck!

Im not an expert on routers/port forwarding but I dont understand why I would open any ports on the remote site, all ports are open for outgoing taffic. And active checks sends from the agent only, not listen to any port.

In my router where I have the Zabbix server I open port 10051 translating that port to local 10055 pointing to my zabbix server, in the zabbix host configuration I set port 10055, but with no luck

I dont give up

[aib]

Im not an expert on routers/port forwarding but I dont understand why I would open any ports on the remote site, all ports are open for outgoing taffic. And active checks sends from the agent only, not listen to any port.

In my router where I have the Zabbix server I open port 10051 translating that port to local 10055 pointing to my zabbix server, in the zabbix host configuration I set port 10055, but with no luck

Why you didn't create a simple rule

Translate all traffic to {EXTERNAL_IP}:10051 to {INTERNAL_IP}:10051

It's not important to translate correct port number to something different.

first check after creating all FW rules - it's connect from Zabbix Agent PC to Zabbix Server.

# telnet {EXTERNAL_IP} 10051