From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Eric B." Subject: Re: Packets not traversing the POSTROUTING table? Date: Tue, 8 Apr 2008 15:44:19 -0400 Message-ID: References: Return-path: Sender: netfilter-owner@vger.kernel.org List-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: netfilter@vger.kernel.org "Jan Engelhardt" wrote in message news:alpine.LNX.1.10.0804082135360.2229@fbirervta.pbzchgretzou.qr... > > On Tuesday 2008-04-08 21:28, Eric B. wrote: >>> >>> LOGMARK is an extension I wrote, and it being in the xtables-addons >>> package menas you need kernel 2.6.18 at least (but newer is always >>> better, we are approaching 2.6.25), and the xtables base package. >> >>*sigh* Running enterprise servers precludes me from manually installing >>those kernels. Although I'm not quite sure what release 67 of the RH >>kernel includes as updates to the 2.6.9 kernel... Might there be any >>chance >>of it working on the RH 2.6.9-67 kernel? > > Yes, though I suppose hacking up the place in ipt_LOG to print > you the info you need (which is?) would be faster than backporting > the entire xtables. Noting that simple rules like -m conntrack > --ctstate NEW are approaching the debug value of a direct log message > from the modules. Actually, ideally, I'd also like to be able to see the "mark" that is associated to the packet, if at all possible. Any hope of that? (Again, b/c I'm having trouble getting it to route through my kernel's routing table using iproute2). Thanks, Eric