From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S268868AbUHUHCf (ORCPT ); Sat, 21 Aug 2004 03:02:35 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S268869AbUHUHCf (ORCPT ); Sat, 21 Aug 2004 03:02:35 -0400 Received: from qfep04.superonline.com ([212.252.122.160]:43717 "EHLO qfep04.superonline.com") by vger.kernel.org with ESMTP id S268868AbUHUHCe (ORCPT ); Sat, 21 Aug 2004 03:02:34 -0400 From: "Josan Kadett" To: "'Aidas Kasparas'" Cc: Subject: RE: Entirely ignoring TCP and UDP checksum in kernel level Date: Sat, 21 Aug 2004 10:02:34 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 In-Reply-To: <4126F16D.1000507@gmc.lt> Thread-Index: AcSHS5VHAD8yA25VSci2zXgXImAHXgACKFZA X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 Message-Id: Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org It is definetely impossible to use IPTables to handle packets with incorrect checksums since NAT would drop the connection right away, otherwise I would not have been asking this question here. -----Original Message----- From: Aidas Kasparas [mailto:a.kasparas@gmc.lt] Sent: Saturday, August 21, 2004 8:54 AM To: Josan Kadett Subject: Re: Entirely ignoring TCP and UDP checksum in kernel level How about setting up a separate box which would listen on that 192.168.77.1 address and MASQUERADE connections to your crazy box from 192.168.1.x address? Maybe then you would no longer need to break things in kernel?