Balazs Scheidler wrote:

2004-06-03, cs keltezéssel 13:12-kor Benjamin.Zoeller@salt-solutions.de ezt írta:

...

Hi Bazsi, hier the tcpdump: 13:13:19.293263 xxx.xxx.xxx.xx.514 > xx.xxx.x.xxx.514: udp 72 (ttl 28, id 41895, len 100) 13:13:19.327089 xxx.xxx.xxx.xx.514 > xx.xxx.x.xxx.514: [udp sum ok] udp 42 (ttl 28, id 41896, len 70) 13:13:21.819284 xxx.xxx.xxx.xx.514 > xx.xxx.x.xxx.514: udp 57 (ttl 28, id 41897, len 85) 13:13:21.945776 xxx.xxx.xxx.xx.514 > xx.xxx.x.xxx.514: [udp sum ok] udp 48 (ttl 28, id 41898, len 76)

At the moment I am using version 1.5.26 which also works correctly.

The problem is that I can't see the log line itself, thus I am unable to determine why syslog-ng adds that '^@' character.

Are you sure you were using 1.6.4 ? 1.6.0rc4 contained support for parsing PIX timestamps and it added this additional NUL character when PIX or PIX like stamps were received, but this was fixed in 1.6.1

Hi, here my Changelog: 2004-05-14 Balazs Scheidler <bazsi@bzorp.balabit> * configure.in: bumped version number to 1.6.4 here my log: May 27 10:16:25 XX.XXX.X.XXX PPP: XXX : outgoing connection established^@ May 27 10:16:25 XX.XXX.X.XXX SNMP: sent TRAP(linkUp,0) 112 bytes to XX.XXX.XXX.XXX Port 162^@ May 27 10:16:26 XX.XXX.X.XXX SNMP: sent TRAP(linkUp,0) 112 bytes to XX.XXX.XXX.XXX Port 162^@ May 27 10:19:42 XX.XXX.X.XXX PPP: XXX : outgoing connection closed, duration 197 sec, 104450 bytes received, 9237 bytes sent, 3 charging units, 0 charging amounts^@ I compiled with --enable-debug is this a problem? Our routers are from bintec. Modelname is BIANCA/BRICK.