From: Andrew Morton <akpm@linux-foundation•org>
To: netdev@vger•kernel.org
Cc: "bugme-daemon@kernel-bugs•osdl.org"
<bugme-daemon@bugzilla•kernel.org>,
ernisv@gmail•com
Subject: Re: [Bugme-new] [Bug 8338] New: NAT of TCP connections broken
Date: Mon, 16 Apr 2007 13:48:28 -0700 [thread overview]
Message-ID: <20070416134828.5885b451.akpm@linux-foundation.org> (raw)
In-Reply-To: <200704162035.l3GKZlTI002693@fire-2.osdl.org>
> On Mon, 16 Apr 2007 13:35:47 -0700 bugme-daemon@bugzilla•kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=8338
>
> Summary: NAT of TCP connections broken
> Kernel Version: 2.6.20.7
> Status: NEW
> Severity: high
> Owner: networking_netfilter-iptables@kernel-bugs•osdl.org
> Submitter: ernisv@gmail•com
>
>
> Most recent kernel where this bug did *NOT* occur: 2.6.18
> Distribution: Debian
> Hardware Environment: amd64 4200x2
> Software Environment:
> Problem Description:
> I'm using my debian box for sharing internet connection. After update to
> debian's 2.6.20 kernel (and adjusting new kernel configuration for NAT) NAT of
> TCP connections stoped working, while ICMP and UDP is working (ping, traceroute
> and DNS). When trying to open web page on a PC from my LAN (tried with linux
> and winxp), it sends the request but is unable to receive correct response from
> any site. On the router PC www works ok.
>
> I tried both new "Independent connection tracking" as well as "Dependent
> (obsolete) connection tracking" options with no luck.
>
> tcp_window_scaling setting seems to have no effect.
>
next parent reply other threads:[~2007-04-16 20:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200704162035.l3GKZlTI002693@fire-2.osdl.org>
2007-04-16 20:48 ` Andrew Morton [this message]
2007-04-17 13:00 ` [Bugme-new] [Bug 8338] New: NAT of TCP connections broken Patrick McHardy
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=20070416134828.5885b451.akpm@linux-foundation.org \
--to=akpm@linux-foundation$(echo .)org \
--cc=bugme-daemon@bugzilla$(echo .)kernel.org \
--cc=ernisv@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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