netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Kris Op de Beeck <kris.op.de.beeck@newtec.eu>
Cc: Ulrik De Bie <ulrik.debie@newtec.eu>,
	netdev@vger.kernel.org,
	Netfilter Development Mailinglist
	<netfilter-devel@vger.kernel.org>
Subject: Re: DNAT sporadically doesn't replace destination IP address
Date: Thu, 22 May 2008 17:36:27 +0200	[thread overview]
Message-ID: <483592FB.7070900@trash.net> (raw)
In-Reply-To: <4835AE9B.B932.00FE.0@newtec.eu>

Kris Op de Beeck wrote:
>>> [  927.204000] nf_ct_tcp: invalid SYNIN= OUT= SRC=192.168.1.30 DST=10.9.9.29 
>> LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=25745 DF PROTO=TCP SPT=52775 DPT=80 
>> SEQ=2154890499 ACK=0 WINDOW=5840 RES=0x00 SYN URGP=0 OPT 
>> (020405B40402080A000264810000000001030307) UID=1000
>>> For those DST ip addresses I've got failures
>> Which kernel is this test running on? That message
>> is gone since 2.6.22.
> 
> s3p@burnin:~$ uname -a
> Linux burnin 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux
> 
> This was the config where I detected the problem. (Ubuntu 7.10)

Odd. I'll have a look at the ubuntu kernel.

  reply	other threads:[~2008-05-22 15:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-22 14:33 DNAT sporadically doesn't replace destination IP address Kris Op de Beeck
2008-05-22 14:57 ` Patrick McHardy
2008-05-22 15:22   ` Kris Op de Beeck
2008-05-22 15:28     ` Patrick McHardy
2008-05-22 15:34       ` Kris Op de Beeck
2008-05-22 15:36         ` Patrick McHardy [this message]
2008-05-22 16:29         ` Patrick McHardy
2008-05-22 17:45           ` Kris Op de Beeck
2008-05-23 14:16           ` Kris Op de Beeck
2008-05-26 14:21             ` Patrick McHardy
2008-05-27 14:27               ` Kris Op de Beeck
2008-05-27 14:44                 ` Patrick McHardy
2008-05-29 10:12                   ` Kris Op de Beeck
  -- strict thread matches above, loose matches on Subject: below --
2008-05-26 12:11 Ulrik De Bie

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=483592FB.7070900@trash.net \
    --to=kaber@trash.net \
    --cc=kris.op.de.beeck@newtec.eu \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=ulrik.debie@newtec.eu \
    /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;
as well as URLs for NNTP newsgroup(s).