From: Ming-Ching Tiew <mingching.tiew@redtone.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: bugme-daemon@bugzilla.kernel.org, netdev@vger.kernel.org
Subject: Re: [Bugme-new] [Bug 9719] New: when a system is configured as a bridge, and at the same time configured to have multipath weighted route, with one leg goes thru NAT and another without NAT, the nat path will intermittently get packets leaking out using internal IP without being SNAT-ted
Date: Thu, 10 Jan 2008 21:07:10 +0800 [thread overview]
Message-ID: <4786187E.3090000@redtone.com> (raw)
In-Reply-To: <20080109152813.83fb8168.akpm@linux-foundation.org>
Andrew Morton wrote:
> (switched to email. Please respond via emailed reply-to-all, not via the
> bugzilla web interface).
>
> On Wed, 9 Jan 2008 11:55:50 -0800 (PST)
> bugme-daemon@bugzilla.kernel.org wrote:
>
>
>> http://bugzilla.kernel.org/show_bug.cgi?id=9719
>>
>> Summary: when a system is configured as a bridge, and at the same
>> time configured to have multipath weighted route, with
>> one leg goes thru NAT and another without NAT, the nat
>> path will intermittently get packets leaking out using
>> internal IP without being SNAT-ted
>> Product: Networking
>> Version: 2.5
>> KernelVersion: 2.6.22.15 and 2.6.23
>> Platform: All
>> OS/Version: Linux
>> Tree: Mainline
>> Status: NEW
>> Severity: normal
>> Priority: P1
>> Component: Netfilter/Iptables
>> AssignedTo: networking_netfilter-iptables@kernel-bugs.osdl.org
>> ReportedBy: mingching.tiew@redtone.com
>>
>>
>> Latest working kernel version: 2.6.23
>> Earliest failing kernel version: 2.6.22.15
>>
>
> This doesn't make sense. What we're trying to ask here (and we've been
> unable to find a pair of questions which 100% of reporters can successfully
> answer) is whether this is a regression, and in which kernel release did we
> regress?
>
> In other words: did we break it, and if so, when did we break it?
>
Sorry for the confusion and for such a lousy first time bug reporter.
I realized that mistake immediately after I posted it on the web
interface. However, the web interface does not seem to allow me to
correct that.
What I meant was that it failed on both the kernel versions I tested. I
am afraid it is a problem which exists all a long. Perhaps it has been
broken quite sometime already. I need to go back to try some older
kernel version and see if I could repeat the problem.
Regards.
next prev parent reply other threads:[~2008-01-10 0:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-9719-10286@http.bugzilla.kernel.org/>
2008-01-09 23:28 ` [Bugme-new] [Bug 9719] New: when a system is configured as a bridge, and at the same time configured to have multipath weighted route, with one leg goes thru NAT and another without NAT, the nat path will intermittently get packets leaking out using internal IP without being SNAT-ted Andrew Morton
2008-01-10 13:07 ` Ming-Ching Tiew [this message]
2008-01-10 16:32 ` Ming-Ching Tiew
2008-01-10 17:25 ` Ming-Ching Tiew
2008-01-10 15:41 ` Patrick McHardy
2008-01-13 1:04 ` Ming-Ching Tiew
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=4786187E.3090000@redtone.com \
--to=mingching.tiew@redtone.com \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).