Wazuh Client not Sending Data to Manager #2218
Replies: 4 comments 2 replies
-
Did you solve the issue? I'm having the same problem on Windows. |
Beta Was this translation helpful? Give feedback.
-
Did you also open TCP/1515? https://documentation.wazuh.com/3.13/user-manual/registering/index.html |
Beta Was this translation helpful? Give feedback.
-
If you look in |
Beta Was this translation helpful? Give feedback.
-
Hello @rdemars-zcorum Did you manage to resolve.? Am having the same issue |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
There seems to be an issue with the Wazuh on SO Manager getting data from the clients.
On the SO manager:
so-wazuh-agent-manage -l
Available agents:
ID: 001, Name: so-manager, IP: 10.75.236.225
ID: 002, Name: ansible, IP: 172.16.7.4
ID: 003, Name: repos, IP: 10.75.236.245
ID: 004, Name: freeipa, IP: 172.16.10.10
ID: 005, Name: ticketing, IP: 10.75.236.109
ID: 006, Name: bluesky-map, IP: 10.75.236.3
ID: 007, Name: ctbacula, IP: 10.75.236.122
iptables -nvL |grep 1514
0 0 ACCEPT tcp -- !docker0 docker0 0.0.0.0/0 172.17.0.11 tcp dpt:1514
0 0 ACCEPT udp -- !docker0 docker0 0.0.0.0/0 172.17.0.11 udp dpt:1514
135 14405 ACCEPT udp -- * * 10.75.236.122 0.0.0.0/0 udp dpt:1514
2 88 ACCEPT tcp -- * * 10.75.236.122 0.0.0.0/0 tcp dpt:1514
197 22261 ACCEPT udp -- * * 10.75.236.3 0.0.0.0/0 udp dpt:1514
0 0 ACCEPT tcp -- * * 10.75.236.3 0.0.0.0/0 tcp dpt:1514
393 44409 ACCEPT udp -- * * 172.16.0.0/16 0.0.0.0/0 udp dpt:1514
0 0 ACCEPT tcp -- * * 172.16.0.0/16 0.0.0.0/0 tcp dpt:1514
0 0 ACCEPT udp -- * * 10.75.235.0/24 0.0.0.0/0 udp dpt:1514
0 0 ACCEPT tcp -- * * 10.75.235.0/24 0.0.0.0/0 tcp dpt:1514
404 45142 ACCEPT udp -- * * 10.75.236.0/24 0.0.0.0/0 udp dpt:1514
4 176 ACCEPT tcp -- * * 10.75.236.0/24 0.0.0.0/0 tcp dpt:1514
0 0 ACCEPT udp -- * * 10.75.236.109 0.0.0.0/0 udp dpt:1514
0 0 ACCEPT tcp -- * * 10.75.236.109 0.0.0.0/0 tcp dpt:1514
0 0 ACCEPT udp -- * * 172.16.10.10 0.0.0.0/0 udp dpt:1514
0 0 ACCEPT tcp -- * * 172.16.10.10 0.0.0.0/0 tcp dpt:1514
0 0 ACCEPT udp -- * * 10.75.236.245 0.0.0.0/0 udp dpt:1514
0 0 ACCEPT tcp -- * * 10.75.236.245 0.0.0.0/0 tcp dpt:1514
0 0 ACCEPT udp -- * * 172.16.7.4 0.0.0.0/0 udp dpt:1514
0 0 ACCEPT tcp -- * * 172.16.7.4 0.0.0.0/0 tcp dpt:1514
0 0 ACCEPT udp -- * * 10.75.236.225 0.0.0.0/0 udp dpt:1514
0 0 ACCEPT tcp -- * * 10.75.236.225 0.0.0.0/0 tcp dpt:1514
0 0 ACCEPT udp -- * * 127.0.0.1 0.0.0.0/0 udp dpt:1514
0 0 ACCEPT tcp -- * * 127.0.0.1 0.0.0.0/0 tcp dpt:1514
On a client:
cat /var/ossec/log/ossec.log
2020/12/04 12:22:24 ossec-agentd: WARNING: Unable to connect to any server.
2020/12/04 12:22:24 ossec-agentd: INFO: Closing connection to server (10.75.236.225:1514/udp).
2020/12/04 12:22:24 ossec-agentd: INFO: Trying to connect to server (10.75.236.225:1514/udp).
2020/12/04 12:23:29 ossec-agentd: INFO: Closing connection to server (10.75.236.225:1514/udp).
2020/12/04 12:23:29 ossec-agentd: INFO: Trying to connect to server (10.75.236.225:1514/udp).
2020/12/04 12:24:34 ossec-agentd: INFO: Closing connection to server (10.75.236.225:1514/udp).
nmap -P0 -p1514 -sU 10.75.236.225
Starting Nmap 6.40 ( http://nmap.org ) at 2020-12-04 13:29 EST
Nmap scan report for av-ossim.zcorum.com (10.75.236.225)
Host is up (0.00048s latency).
PORT STATE SERVICE
1514/udp open|filtered fujitsu-dtcns
MAC Address: 00:50:56:90:20:8E (VMware)
Nmap done: 1 IP address (1 host up) scanned in 0.50 seconds
Beta Was this translation helpful? Give feedback.
All reactions