Rainer, thanks for your reply. For now , I just started rsyslog in the foreground using the -d option. That was enough to see that the messages from the remote host did not come in. I checked tcpdump again and saw the messages were actually delivered to the interface.
We restored a broken install for iptables and that showed that all traffic should come in. So we started a test with netcat listening on port UDP 514 instead of rsyslog (stopped). That showed indeed nothing was coming in, which ruled out an error in the configuration of rsyslog. We checked the other settings for the OS. We have both ipv6 and ipv4 configured in this system. For Ipv6 there is a gateway configured. For ipv4 there was not. Actually, this was one of the things that David mentioned earlier. Well, it seems he was exacly right! we configured a default gateway for ipv4 as well, and after starting the rsyslog service, messages were logged in the way they are supposed to, in a separate directory using the %FROMHOST% option. I want to thank you very much for your most welcome help. Best Regards, Geert Liesveld. -- View this message in context: http://rsyslog-users.1305293.n2.nabble.com/Remote-syslog-setup-unsuccesful-tp7589216p7589263.html Sent from the rsyslog-users mailing list archive at Nabble.com. _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
