So, Why and how does it picks up the 3.144.255.X to bind though I am only
putting 3.144.90.X at every stage of the agent installation?
On Thursday, 29 May 2014 10:48:03 UTC-4, dan (ddpbsd) wrote:
>
> On Thu, May 29, 2014 at 10:46 AM, Devendra Agarwal
> > wrote:
> > I have a
I have a server with 2 IPs (3.144.255.X & 3.144.90.X). I am trying to use
3.144.90.X for OSSEC. No matter what I do, ossec-agentd always binds to
3.144.255.X interface on the client. How can I force ossec-agentd to bind
to 3.144.90.X?
--
---
You received this message because you are subscrib
nt Solutions On-Site at the NIH
>> NIH / NIA / IRP
>> Tel : 410 558 8013
>> mailto: bin...@nia.nih.gov
>>
>>
>> NCTS performance comments and survey at:
>> https://niairpkiosk.irp.nia.nih.gov/content/ncts-user-survey
>>
>> On Apr 10, 2014, at 9:43
>
> Valère Binet [C]
> IT Security Administrator
> Kelly Government Solutions On-Site at the NIH
> NIH / NIA / IRP
> Tel : 410 558 8013
> mailto: bin...@nia.nih.gov
>
>
> NCTS performance comments and survey at:
> https://niairpkiosk.irp.nia.nih.
hey should be in /var/ossec/logs
>
> Valère Binet [C]
> IT Security Administrator
> Kelly Government Solutions On-Site at the NIH
> NIH / NIA / IRP
> Tel : 410 558 8013
> mailto: bin...@nia.nih.gov
>
>
> NCTS performance comments and survey at:
> https://n
d issues with systems running multiple IP addresses. If
> that is the case I would recommend to check with tcpdump which is the one
> that the agent uses to send data to the server, and be sure it matches the
> one configured for the agent.
>
> I hope it helps
>
>
>
>
I installed ossec-hids-2.4.1 agent on a server running on Red Hat Linux
5.4. The agent is not communicating. Other agents are fine. It seems if I
hace NIC bonding setup, this isue happens. Is there any known issue with
ossec if there is NIC bonding setup?
2014/04/09 16:23:28 ossec-agentd: INFO:
