public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Josan Kadett <corporate@superonline.com>
Cc: "'Aidas Kasparas'" <a.kasparas@gmc.lt>, linux-kernel@vger.kernel.org
Subject: Re: Entirely ignoring TCP and UDP checksum in kernel level
Date: Sat, 21 Aug 2004 11:14:41 +0200	[thread overview]
Message-ID: <20040821091441.GA691@ucw.cz> (raw)
In-Reply-To: <S268889AbUHUIAZ/20040821080025Z+1903@vger.kernel.org>

On Sat, Aug 21, 2004 at 11:00:27AM +0200, Josan Kadett wrote:
> The problem is that the interface 192.168.1.1 does not allow any tranmission
> to occur. An implementation error I think... We send packets to 192.168.1.1,
> we get no reply, but when we send packets to 192.168.77.1 we get the replies
> (that is where the abnormality begins). However; the replies are now sourced
> from 192.168.1.1 instead. That is, the blasted code in the device calculates
> the checksum using the wrong IP address which it thinks it is assigned to...

How about assigning an IP address that generates the same checksum to
the second interface? That'd solve your problem.

Or assign both interfaces the same IP address, maybe the device allows it.

> 
> -----Original Message-----
> From: Aidas Kasparas [mailto:a.kasparas@gmc.lt] 
> Sent: Saturday, August 21, 2004 9:47 AM
> To: Josan Kadett
> Subject: Re: Entirely ignoring TCP and UDP checksum in kernel level
> 
> But will these checksums be incorect if crazy box would communicate with 
> address in 192.168.1.x only?
> 
> The whole idea was based on the fact, that if that box works well in 
> 192.168.1.x networkd, then let it think it works in the network it knows 
> how to work!
> 
> Josan Kadett wrote:
> > 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?
> > 
> > 
> > 
> 
> -- 
> Aidas Kasparas
> IT administrator
> GM Consult Group, UAB
> 
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

  parent reply	other threads:[~2004-08-21  9:16 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4126FDD8.1090101@gmc.lt>
2004-08-21  9:00 ` Entirely ignoring TCP and UDP checksum in kernel level Josan Kadett
2004-08-21  8:11   ` Denis Vlasenko
2004-08-21  9:18     ` Josan Kadett
2004-08-21  8:26       ` Lee Revell
2004-08-21  9:35         ` Josan Kadett
2004-08-21  9:14   ` Vojtech Pavlik [this message]
     [not found] <41285DB3.6070605@wasp.net.au>
2004-08-22 10:14 ` Josan Kadett
2004-08-22 11:48   ` James Courtier-Dutton
2004-08-22 10:25 ` Josan Kadett
2004-08-22  9:36   ` Brad Campbell
2004-08-22 10:48     ` Josan Kadett
2004-08-22 13:10       ` Brad Campbell
2004-08-22 13:13       ` Brad Campbell
2004-08-22 19:27         ` Josan Kadett
2004-08-22 20:28         ` Josan Kadett
2004-08-23  3:38           ` David Meybohm
2004-08-23  5:26             ` Josan Kadett
2004-08-23  8:40             ` Josan Kadett
2004-08-22  9:19 Brad Campbell
  -- strict thread matches above, loose matches on Subject: below --
2004-08-22  6:17 Brad Campbell
2004-08-22  7:18 ` Josan Kadett
2004-08-22  7:24 ` Josan Kadett
2004-08-22  7:04   ` Brad Campbell
2004-08-22  8:12     ` Josan Kadett
2004-08-22  8:29       ` Brad Campbell
     [not found] <04Aug21.205911edt.41960@gpu.utcc.utoronto.ca>
2004-08-22  2:08 ` Josan Kadett
2004-08-22  6:01   ` Brad Campbell
2004-08-22  7:06     ` Josan Kadett
     [not found] <1093120934.854.155.camel@krustophenia.net>
2004-08-21 20:46 ` Lee Revell
2004-08-21 21:53   ` Josan Kadett
     [not found] <1093078213.854.76.camel@krustophenia.net>
2004-08-21  8:58 ` Lee Revell
2004-08-21 21:41   ` Josan Kadett
2004-08-21  8:27 Denis Vlasenko
2004-08-21  8:41 ` Lee Revell
2004-08-21  9:50   ` Josan Kadett
2004-08-21  9:06     ` Kalin KOZHUHAROV
2004-08-21 21:46       ` Josan Kadett
2004-08-21  9:39 ` Josan Kadett
     [not found] <4126F16D.1000507@gmc.lt>
2004-08-21  8:02 ` Josan Kadett
2004-08-21  7:36   ` Kalin KOZHUHAROV
2004-08-21  8:54     ` Josan Kadett
2004-08-21  6:15 Josan Kadett
2004-08-21  7:10 ` Willy Tarreau

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040821091441.GA691@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=a.kasparas@gmc.lt \
    --cc=corporate@superonline.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox