RE: [ossec-list] Windows OSSEC Agent on a multihomed device

2013-07-15 Thread LostInTheTubez
This can be resolved by the route command on Server 2008. You'll want to do a 'route PRINT' to determine the interface number that you want the traffic to be sent out on. Let's presume your OSSEC server's IP is 192.168.23.23. To add a static route to your configuration, you'd open a commandline and

Re: [ossec-list] Windows OSSEC Agent on a multihomed device

2013-07-15 Thread dan (ddp)
On Mon, Jul 15, 2013 at 2:14 PM, Tim Brigham wrote: > I have one specific 2008 R2 server that is set up in the following fashion > using port forwarding to a protected subnet. > > 192.168.100.4 (main server IP) > 192.168.100.60 -> 192.168.103.xx > 192.168.100.61 -> 192.168.103.xy > 192.168.100.62