From: Ming-Ching Tiew <mingching.tiew@redtone.com>
To: Ming-Ching Tiew <mingching.tiew@redtone.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
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: Fri, 11 Jan 2008 01:25:49 +0800 [thread overview]
Message-ID: <4786551D.8010700@redtone.com> (raw)
In-Reply-To: <47864892.9010605@redtone.com>
Ming-Ching Tiew wrote:
> Ming-Ching Tiew wrote:
>>
>> 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.
>
> OK based on the I repeat the problem, so far I could not find such
> misbehaviour on kernel 2.6.18. I will do more tests to make it more
> conclusive.
>
Sorry for jumping the gun. Kernel 2.6.18 has the same problem too.
I think from now on, I will refrain from early posting until conclusive
results.
next prev parent reply other threads:[~2008-01-10 4:26 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
2008-01-10 16:32 ` Ming-Ching Tiew
2008-01-10 17:25 ` Ming-Ching Tiew [this message]
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=4786551D.8010700@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).