[syslog-ng] syslog-ng and multiple interfaces
brandon
brandons.maillist at gmail.com
Fri Oct 24 18:38:14 CEST 2008
Hello Pavel-
This was exactly what I was looking for and it worked perfectly after I
removed the ';' after port(1999) in your example. So basically I have:
destination d_tcp { tcp("x.x.x.x" port(1999) localip("x.x.x.x")); };
Thanks again
-Brandon
On Fri, Oct 24, 2008 at 12:43 AM, Pavel Shaydo <pshaydo at elverils.com> wrote:
>
> On Thu, 2008-10-23 at 15:48 -0700, brandon askme wrote:
> > Hello-
> > I have successfully moved all of our servers over to syslog-ng. All
> > but a few are reporting to the remote "logging" server I have setup.
> > What I have found is that the clients that are not reporting have
> > multiple interfaces, IE eth0, eth0:1, eth1 etc.. Thus the current
> > firewall rules are not setup to allow all the ips. So my question is,
> > can I configure syslog-ng to only use a certain ip/interface when
> > sending the logs to the remote logging server? The clients and the
> > remote logging server are running Linux.
> >
>
> Hello,
>
> probably you should look on localip() option of destination driver.
>
> destination d_tcp { tcp("10.1.2.3" port(1999); localip("10.3.2.1") ); };
>
>
> --
> Best regards,
> Pavel Shaydo
>
>
> ______________________________________________________________________________
> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
> Documentation:
> http://www.balabit.com/support/documentation/?product=syslog-ng
> FAQ: http://www.campin.net/syslog-ng/faq.html
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.balabit.hu/pipermail/syslog-ng/attachments/20081024/39e39a70/attachment.htm
More information about the syslog-ng
mailing list