From mboxrd@z Thu Jan 1 00:00:00 1970 From: Patrick McHardy Date: Thu, 01 Jun 2006 20:10:24 +0000 Subject: Re: [LARTC] iptables CLASSIFY and MARK not working? Message-Id: <447F49B0.90804@trash.net> List-Id: References: <0633E0EDB4F25F43A2D7179CA11FAFAB25541B@xavier.staff.greatlakes.net> In-Reply-To: <0633E0EDB4F25F43A2D7179CA11FAFAB25541B@xavier.staff.greatlakes.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: "Eliot, Wireless and Server Administrator, Great Lakes Internet" Cc: lartc@mailman.ds9a.nl, Netfilter Development Mailinglist Eliot, Wireless and Server Administrator, Great Lakes Internet wrote: > THANK YOU! > > That solved the problem. I found the file you specified and it was > indeed enabled. After disabling it, it is now working! Good to hear. This crap is causing one weird problem after another, we really need to get rid of it. _______________________________________________ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc From mboxrd@z Thu Jan 1 00:00:00 1970 From: Patrick McHardy Subject: Re: [LARTC] iptables CLASSIFY and MARK not working? Date: Thu, 01 Jun 2006 22:10:24 +0200 Message-ID: <447F49B0.90804@trash.net> References: <0633E0EDB4F25F43A2D7179CA11FAFAB25541B@xavier.staff.greatlakes.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Cc: lartc@mailman.ds9a.nl, Netfilter Development Mailinglist Return-path: To: "Eliot, Wireless and Server Administrator, Great Lakes Internet" In-Reply-To: <0633E0EDB4F25F43A2D7179CA11FAFAB25541B@xavier.staff.greatlakes.net> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: netfilter-devel-bounces@lists.netfilter.org Errors-To: netfilter-devel-bounces@lists.netfilter.org List-Id: netfilter-devel.vger.kernel.org Eliot, Wireless and Server Administrator, Great Lakes Internet wrote: > THANK YOU! > > That solved the problem. I found the file you specified and it was > indeed enabled. After disabling it, it is now working! Good to hear. This crap is causing one weird problem after another, we really need to get rid of it.