On Tue, Aug 27, 2013 at 10:07 AM, Brent Phillips <[email protected]> wrote: > > > On Monday, August 26, 2013 4:34:20 PM UTC-4, Michael Starks wrote: >> >> On 26.08.2013 14:28, Brent Phillips wrote: >> > I have two network cards with two separate IP address's. The only way >> > I can get the OSSEC server to see the agent on the Windows Server is >> > if I use an IP range rather than one of the IP's. >> > >> > The network cards IP's are 172.27.86.18 and 172.27.86.19. I have to >> > use the 172.27.86.0/24 when adding the agent to the OSSEC HIDS, for >> > the agent to connect to the server. >> >> I would find out which interface the OSSEC traffic is exiting from and >> use that IP on the manager. But it sounds like you have tried that. Is >> the traffic multi-pathed through both interfaces? Can you add a static >> route to force the traffic to go through one interface? > > > Yes, I tried both IP's and it wouldn't work. I'm not sure how to force the > agent through a particular network card. Maybe someone else knows? >
There has to be a way to add a static route or something. > -- > > --- > 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/groups/opt_out. -- --- 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/groups/opt_out.
