Hello,
I was wondering if one of the developers might address this issue.
It appears that the OSSEC agent always binds itself to the highest
numbered interface. At present we have been able to work around this
at the OS/Networking configuration level on the client (e.g. by
disabling /etc/sysconf
Hello,
I have no socket programming experience, but I have been doing some
digging:
1.
../src/config/client-config allows for an element within the
element in the agent ossec.conf called local_ip.
I have tried adding local_ip to the ossec.conf file but the agent
doesn't bind to that address. W
On 06/08/2010 04:29 PM, tm wrote:
Hello,
I was wondering if one of the developers might address this issue.
It appears that the OSSEC agent always binds itself to the highest
numbered interface.
I second that! I know this is going to be an issue in some of my
environments, too. This is a nee
