On Tue, Nov 8, 2016 at 9:13 AM, Kumar G wrote:
> Don't know if this falls under same issue. We are getting same error messages
> on one of the ossec server A, no new agents addition via manage_agents or
> ossec_authd were changing the status from "Never connected" to Active after
> adding them.
Don't know if this falls under same issue. We are getting same error messages
on one of the ossec server A, no new agents addition via manage_agents or
ossec_authd were changing the status from "Never connected" to Active after
adding them. Both manual and ossec auth worked out, these were the f
Hi Vipin,
Prior to connect to the manager, agents must be registered onto it. For
example, let the manager's IP be 1.1.1.1 and the agent's IP be 2.2.2.2.
In first place, use /var/ossec/bin/manage_agents to add an agent. Choose an
arbitrary name for it, then you'll be asked for the agent's IP. I
Hi,
Can you help me with detailed information (Does the IP address of the
packets from this agent (as seen with tcpdump on the OSSEC server) match
the IP address in client.keys on the server). I am new to this product.
Regards
Vipin Hooda
On Tuesday, October 25, 2016 at 6:22:45 PM UTC+5:30,
On Tue, Oct 25, 2016 at 8:49 AM, wrote:
> Hi,
>
> Agent to server communication issue is occurring on multiple machines and
> below logs are getting generated on client machine. We have requested
> customer to check packet drop on firewall but according to customer there is
> no packet drop on fi
Hi,
Agent to server communication issue is occurring on multiple machines and
below logs are getting generated on client machine. We have requested
customer to check packet drop on firewall but according to customer there
is no packet drop on firewall for client machines.
2016/10/25 16:33:19 o