I could, but in testing restarting the service didn't work 100% of the time. In our environment users change networks a lot and I see this product failing.
On Monday, August 10, 2015 at 8:15:49 AM UTC-7, dan (ddpbsd) wrote: > > On Fri, Aug 7, 2015 at 11:30 AM, Ed C <[email protected] <javascript:>> > wrote: > > I'm seeing an issue on Windows and Mac clients where the client is > unable to > > send logs after the network adapter changes. If I'm on wireless and > then > > connect to VPN the client logs say the agent is unable to communicate > with > > the server. However if I restart the service or run ossec-control stop > and > > ossec-control-start it starts sending logs again. Anyone have any > ideas? > > > > Can you setup the systems to restart the processes when the network > changes? > > > -- > > > > --- > > 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] <javascript:>. > > 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.
