<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: network trace log to kernel log file in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/network-trace-log-to-kernel-log-file/m-p/4020968#M28787</link>
    <description>Thanks for the help... I see the iptables firewall rules and will disable them.&lt;BR /&gt;&lt;BR /&gt;Thanks again.&lt;BR /&gt;&lt;BR /&gt;Tammy</description>
    <pubDate>Mon, 18 Jun 2007 09:19:41 GMT</pubDate>
    <dc:creator>Tammy Liang</dc:creator>
    <dc:date>2007-06-18T09:19:41Z</dc:date>
    <item>
      <title>network trace log to kernel log file</title>
      <link>https://community.hpe.com/t5/operating-system-linux/network-trace-log-to-kernel-log-file/m-p/4020964#M28783</link>
      <description>There is network trace keep logging into kernel log file which filled up /var file system. How can I turn off this network trace log message, so won't put a line to kernel.log file evey time some one connect to this system via eth0 card?&lt;BR /&gt;&lt;BR /&gt;Tks.&lt;BR /&gt;&lt;BR /&gt;Tammy</description>
      <pubDate>Fri, 15 Jun 2007 09:30:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/network-trace-log-to-kernel-log-file/m-p/4020964#M28783</guid>
      <dc:creator>Tammy Liang</dc:creator>
      <dc:date>2007-06-15T09:30:29Z</dc:date>
    </item>
    <item>
      <title>Re: network trace log to kernel log file</title>
      <link>https://community.hpe.com/t5/operating-system-linux/network-trace-log-to-kernel-log-file/m-p/4020965#M28784</link>
      <description>Please post a sample record. Probably is caused by some iptables rules that LOGS the packets.&lt;BR /&gt;&lt;BR /&gt;You should check your iptables rules.</description>
      <pubDate>Fri, 15 Jun 2007 09:57:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/network-trace-log-to-kernel-log-file/m-p/4020965#M28784</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2007-06-15T09:57:48Z</dc:date>
    </item>
    <item>
      <title>Re: network trace log to kernel log file</title>
      <link>https://community.hpe.com/t5/operating-system-linux/network-trace-log-to-kernel-log-file/m-p/4020966#M28785</link>
      <description>How can I check iptable rules?&lt;BR /&gt;Below are the lines log to both dmesg.log and kernel.log files.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;BANDWIDTH_IN:IN=eth0 OUT= MAC=00:18:fe:71:31:11:00:13:72:a9:4e:a7:08:00 src=10.99.66.45 DST=10.99.66.43 LEN=53 TOS=0x00 PREC=0x00 TTL=128 ID=27450 DF PROTO=TCP SPT=1088 DPT=1521 WINDOW=16849 RES=0x00 ACK PSH URGP=0 &lt;BR /&gt;BANDWIDTH_OUT:IN= OUT=eth0 src=10.99.66.43 DST=10.99.66.45 LEN=57 TOS=0x00 PREC=0x00 TTL=64 ID=9796 DF PROTO=TCP SPT=1521 DPT=1088 WINDOW=32767 RES=0x00 ACK PSH URGP=0 &lt;BR /&gt;BANDWIDTH_IN:IN=eth0 OUT= MAC=00:18:fe:71:31:11:00:13:72:a9:4e:a7:08:00 src=10.99.66.45 DST=10.99.66.43 LEN=40 TOS=0x00 PREC=0x00 TTL=128 ID=27462 DF PROTO=TCP SPT=1088 DPT=1521 WINDOW=16832 RES=0x00 ACK URGP=0 &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 15 Jun 2007 10:27:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/network-trace-log-to-kernel-log-file/m-p/4020966#M28785</guid>
      <dc:creator>Tammy Liang</dc:creator>
      <dc:date>2007-06-15T10:27:13Z</dc:date>
    </item>
    <item>
      <title>Re: network trace log to kernel log file</title>
      <link>https://community.hpe.com/t5/operating-system-linux/network-trace-log-to-kernel-log-file/m-p/4020967#M28786</link>
      <description>iptables -nL --line&lt;BR /&gt;&lt;BR /&gt;Look for lines that have 'LOG' int he 2nd column, and 'BANDWIDTH_IN' or 'BANDWIDTH_OUT' on the right-hand-side.&lt;BR /&gt;&lt;BR /&gt;Starting from the bottm, use:&lt;BR /&gt;&lt;BR /&gt;iptables -D &lt;CHAIN&gt; &lt;NUM&gt;&lt;BR /&gt;&lt;BR /&gt;to remove then.&lt;BR /&gt;&lt;BR /&gt;If you want to leave the rules there, but only have them not trigger when the user is using 'eth0', then use:&lt;BR /&gt;&lt;BR /&gt;iptables -R &lt;CHAIN&gt; &lt;NUM&gt; -i !eth0 -j LOG ........&lt;BR /&gt;&lt;BR /&gt;(where ... makes up the rest of the rule (-s, -d, -p etc.)).&lt;BR /&gt;&lt;BR /&gt;Once complete, save the rules.  On a RH or SuSE system, use 'service iptables save'.&lt;/NUM&gt;&lt;/CHAIN&gt;&lt;/NUM&gt;&lt;/CHAIN&gt;</description>
      <pubDate>Fri, 15 Jun 2007 16:35:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/network-trace-log-to-kernel-log-file/m-p/4020967#M28786</guid>
      <dc:creator>Stuart Browne</dc:creator>
      <dc:date>2007-06-15T16:35:09Z</dc:date>
    </item>
    <item>
      <title>Re: network trace log to kernel log file</title>
      <link>https://community.hpe.com/t5/operating-system-linux/network-trace-log-to-kernel-log-file/m-p/4020968#M28787</link>
      <description>Thanks for the help... I see the iptables firewall rules and will disable them.&lt;BR /&gt;&lt;BR /&gt;Thanks again.&lt;BR /&gt;&lt;BR /&gt;Tammy</description>
      <pubDate>Mon, 18 Jun 2007 09:19:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/network-trace-log-to-kernel-log-file/m-p/4020968#M28787</guid>
      <dc:creator>Tammy Liang</dc:creator>
      <dc:date>2007-06-18T09:19:41Z</dc:date>
    </item>
    <item>
      <title>Re: network trace log to kernel log file</title>
      <link>https://community.hpe.com/t5/operating-system-linux/network-trace-log-to-kernel-log-file/m-p/4020969#M28788</link>
      <description>I stoped the iptables service. It stop the logging to dmesg.log file.</description>
      <pubDate>Mon, 18 Jun 2007 13:21:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/network-trace-log-to-kernel-log-file/m-p/4020969#M28788</guid>
      <dc:creator>Tammy Liang</dc:creator>
      <dc:date>2007-06-18T13:21:16Z</dc:date>
    </item>
  </channel>
</rss>

