Geordon, Extracted from /etc/rc.config.d/firewall2.rc.config # 16.) # Which logging level should be enforced? # You can define to log packets which were accepted or denied. # You can also the set log level, the critical stuff or everything. # Note that logging *_ALL is only for debugging purpose ... # Choice: "yes" or "no", FW_LOG_*_CRIT defaults to "yes", # FW_LOG_*_ALL defaults to "no" FW_LOG_DROP_CRIT="yes" FW_LOG_DROP_ALL="no" FW_LOG_ACCEPT_CRIT="yes" FW_LOG_ACCEPT_ALL="no" # only change/activate this if you know what you are doing! FW_LOG="--log-level warning --log-tcp-options --log-ip-option --log-prefix SuSE-FW" I think that your you should play with those parameters... Saludos, Alberto mailto:linux@opc.com.uy Linux User #242064 UyLug Member #195 Con fecha Lunes, 13 de Mayo de 2002, 16:59:21, escribió: GV> -----BEGIN PGP SIGNED MESSAGE----- GV> Hello , GV> I am pulling my hair out trying to figure out how to stop logging the GV> following: GV> May 13 14:54:43 gvantass kernel: SuSE-FW-TRACEROUTE-ATTEMPT GV> IN= OUT=eth1 SRC=192.168.1.1 DST=192.168.1.20 LEN=56 TOS=0x00 GV> PREC=0xC0 TTL=255 ID=3878 PROTO=ICMP TYPE=11 CODE=0 [SRC=192.168.1.20 GV> DST=207.26.131.137 LEN=28 TOS=0x00 PREC=0x00 TTL=1 ID=12025 GV> PROTO=ICMP GV> TYPE=8 CODE=0 ID=1024 SEQ=5377 ] GV> Can someone please point me to the right direction to look to stop GV> logging this particular thing? I can't even figure out why the GV> Windows computer at 192.168.1.20 is trying to ping 207.26.131.137, GV> which isn't alive even, but that's a different story. GV> I would really appreciate some assistance, as I've tried looking in GV> /sbin/SuSEfirewall2 and /etc/sysconfig/SuSEfirewall2 but haven't been GV> able to figure out how to stop this. GV> TIA GV> - -- GV> Best regards, GV> Geordon mailto:gvantass@interaccess.com GV> PGP Key ID: 0xFCF06B79 Your Fortune ==>> "Hegel was right when he said that we learn from GV> history that man can never learn anything from history." (George GV> Bernard Shaw) GV> il\J J GV> -----BEGIN PGP SIGNATURE----- GV> Version: PGP 6.5i GV> iQEVAwUBPOAbIN77fDX88Gt5AQGbZwgAg9igkJZP/dn8sIgq5B8PAsrGjK0aRBLu GV> /WgSjaJzVabB/N45vPnbgVtu+RQWzDECZNHgk672HmUEFiNpOkvOzdTMNzdwXWqR GV> IVscMQqw9fFsUTR6OSrqsfmrKo5RqELLzZHDowcYQcUGULZpRAW/ZykodC4yG/AI GV> nX+3KQs82+JrjTaEr3xS0r1PCKXETxQqNsAzzT2G0594y2Fsj3yh4+WmzQ9AZSP4 GV> Q6UPbhaTxmR5Yrhlq1gQPWSafuWG+52wL5nSJCzsRKcHcLhLjDe4/clhCEwlXSET GV> A/7PMhwIGIWORjEHTl4+z1zI88M9teW9/vC0mQAY5aWZD6hHWRVRKQ== GV> =ZdzE GV> -----END PGP SIGNATURE-----