Bug 41475

Summary: iptables logs to console too.
Product: [Retired] Red Hat Linux Reporter: Andrew Carson <andrewc>
Component: kernelAssignee: Arjan van de Ven <arjanv>
Status: CLOSED RAWHIDE QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.1   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-05-21 10:16:21 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Andrew Carson 2001-05-21 03:36:42 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows 98)

Description of problem:
When setting iptables to log packet matches, the output is sent to the 
console, as well the intended log file. Note that this even happens if the 
*only* entry in syslog.conf is for all logging to go to file, iptables 
data still clutters the console.

How reproducible:
Always

Steps to Reproduce:
1. iptables -A input -i eth0 -p tcp --syn -j LOG --log-level warning
2. Set syslog entry such as *.*  /var/log/logall
3. service syslog restart
4. ping the box
	

Actual Results:  iptables logging directly to console.

Expected Results:  No output to console, to /var/log/logall only.

Additional info:

Have demonstrated this on two different boxes, both low end pentiums.
Comment 1 Bernhard Rosenkraenzer 2001-05-21 10:16:17 UTC 
Packet matching (and logging) is done in the kernel part of iptables, 
assigning to kernel.
Comment 2 Arjan van de Ven 2001-05-21 12:18:10 UTC 
Added printk "level" to the printk for logging. Should appear in rawhide in a
week or so. Thanks for reporting!