[syslog-ng] [Bug 266] localport option does not bind to a specific port

bugzilla at bugzilla.balabit.com bugzilla at bugzilla.balabit.com
Thu Dec 19 10:15:21 CET 2013


https://bugzilla.balabit.com/show_bug.cgi?id=266





--- Comment #3 from Balazs Scheidler <bazsi at balabit.hu>  2013-12-19 10:15:13 ---
Seems to be a bug indeed. be aware though that specifying the full connection tuple (srcip, dstip and both ports)
can cause trouble, especially when there are stateful firewalls between the hosts.

I'll look into this. Thanks for the report.


--- Comment #4 from Balazs Scheidler <bazsi at balabit.hu>  2013-12-19 10:15:18 ---
Seems to be a bug indeed. be aware though that specifying the full connection tuple (srcip, dstip and both ports)
can cause trouble, especially when there are stateful firewalls between the hosts.

I'll look into this. Thanks for the report.


--- Comment #5 from Balazs Scheidler <bazsi at balabit.hu>  2013-12-19 10:15:20 ---
Seems to be a bug indeed. be aware though that specifying the full connection tuple (srcip, dstip and both ports)
can cause trouble, especially when there are stateful firewalls between the hosts.

I'll look into this. Thanks for the report.


-- 
Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.


More information about the syslog-ng mailing list