On Thu, May 29, 2014 at 11:16 AM, Devendra Agarwal <[email protected]> wrote: > 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? >
No idea. I'd start by looking at your routing table. There has to be a reason your OS would choose to use that IP instead. > > On Thursday, 29 May 2014 10:48:03 UTC-4, dan (ddpbsd) wrote: >> >> On Thu, May 29, 2014 at 10:46 AM, Devendra Agarwal >> <[email protected]> wrote: >> > 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? >> > >> >> ossec-agentd doesn't have any way to control which IPs it uses, you'll >> have to rely on the system's routing to do this. >> >> > -- >> > >> > --- >> > You received this message because you are subscribed to the Google >> > Groups >> > "ossec-list" group. >> > To unsubscribe from this group and stop receiving emails from it, send >> > an >> > email to [email protected]. >> > For more options, visit https://groups.google.com/d/optout. > > -- > > --- > You received this message because you are subscribed to the Google Groups > "ossec-list" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- --- You received this message because you are subscribed to the Google Groups "ossec-list" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
