Hi Josh, Inside the <remote> section, you can set the local IP address that you want the server to use. Ex:
<remote> <connection>secure</connection> <local_ip>192.168.1.1</local_ip> </remote> In that way it will bind to a specific interface instead of relying on the kernel for routing the messages. Thanks, -- Daniel B. Cid dcid ( at ) ossec.net On Fri, Jun 20, 2008 at 1:35 PM, Josh Albright <[EMAIL PROTECTED]> wrote: > Hi All, > > Is there a way to configure OSSEC to communicate only over a specific > interface or to listen on all interfaces on a multi-homed system? Our OSSEC > server is trying to communicate to certain agents over a different network > interface than OSSEC seems to be bound to and this is causing agent/server > communication issues. > > Any ideas or work arounds are greatly appreciated. Thanks! >
