From: Patrick McHardy <kaber@trash.net>
To: wijata@nec-labs.com
Cc: Andrew Morton <akpm@linux-foundation.org>,
netdev@vger.kernel.org,
"bugme-daemon@kernel-bugs.osdl.org"
<bugme-daemon@bugzilla.kernel.org>
Subject: Re: [Bugme-new] [Bug 8325] New: -j REDIRECT --to-ports 1000-1009, always first choosen
Date: Mon, 16 Apr 2007 07:12:33 +0200 [thread overview]
Message-ID: <462305C1.9030007@trash.net> (raw)
In-Reply-To: <20070413144702.8ebf1cfe.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Fri, 13 Apr 2007 13:53:12 -0700
> bugme-daemon@bugzilla.kernel.org wrote:
>
>
>>http://bugzilla.kernel.org/show_bug.cgi?id=8325
>>
>> Summary: -j REDIRECT --to-ports 1000-1009, always first choosen
>> Kernel Version: 2.6.19-1.2911.fc6PAE 2.6.19-gentoo-r4
>> Status: NEW
>> Severity: normal
>> Owner: networking_netfilter-iptables@kernel-bugs.osdl.org
>> Submitter: wijata@nec-labs.com
>>
>>
>>Most recent kernel where this bug did *NOT* occur:
>>Distribution: FC6, gentoo
>>Hardware Environment:
>>Software Environment:
>>Problem Description:
>>
>>Steps to reproduce:
>>Try redirecting to range of ports with iptables, kernel(?) will always redirect
>>to first port from given range.
It will use a different port if there is a clash (a connection with the
same identity already exists). I'm guessing you're expecting that it
will use the ports in order. We might be able to change that, but I
don't really see a case where it would make sense. Please describe what
you're trying to do.
next prev parent reply other threads:[~2007-04-16 5:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200704132053.l3DKrC9X000466@fire-2.osdl.org>
2007-04-13 21:47 ` [Bugme-new] [Bug 8325] New: -j REDIRECT --to-ports 1000-1009, always first choosen Andrew Morton
2007-04-16 5:12 ` Patrick McHardy [this message]
2007-04-16 5:26 ` Denys
2007-04-16 5:30 ` Patrick McHardy
2007-04-16 5:45 ` Denys
2007-04-16 5:52 ` 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=462305C1.9030007@trash.net \
--to=kaber@trash.net \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=wijata@nec-labs.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.