From: Eric Dumazet <eric.dumazet@gmail.com>
To: Changli Gao <xiaosuo@gmail.com>
Cc: Patrick McHardy <kaber@trash.net>,
Jan Engelhardt <jengelh@medozas.de>,
Franchoze Eric <franchoze@yandex.ru>,
wensong@linux-vs.org, lvs-devel@vger.kernel.org,
netdev@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: Re: Fwd: LVS on local node
Date: Thu, 22 Jul 2010 11:59:52 +0200 [thread overview]
Message-ID: <1279792792.2467.15.camel@edumazet-laptop> (raw)
In-Reply-To: <AANLkTimLZG_-4wbKy8nrajHVKQvvGtRKEd8qHNoU3swJ@mail.gmail.com>
Le jeudi 22 juillet 2010 à 17:52 +0800, Changli Gao a écrit :
>
> FYI: the random option is documented in the manual page of iptables.
>
> REDIRECT
> This target is only valid in the nat table, in the PREROUTING and OUT-
> PUT chains, and user-defined chains which are only called from those
> chains. It redirects the packet to the machine itself by changing the
> destination IP to the primary address of the incoming interface
> (locally-generated packets are mapped to the 127.0.0.1 address).
>
> --to-ports port[-port]
> This specifies a destination port or range of ports to use:
> without this, the destination port is never altered. This is
> only valid if the rule also specifies -p tcp or -p udp.
>
> --random
> If option --random is used then port mapping will be randomized
> (kernel >= 2.6.22).
>
>
Note my patch has nothing to do with the man page, its already up2date.
I usually dont read the Fine manuals, do you ?
Try :
iptables -t nat -A PREROUTING -p tcp --dport 1234 -j REDIRECT --help
REDIRECT target options:
--to-ports <port>[-<port>]
Port (range) to map to.
You see [--random] is missing.
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-07-22 9:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-22 3:51 Fwd: LVS on local node Franchoze Eric
2010-07-22 6:56 ` Eric Dumazet
2010-07-22 9:10 ` Changli Gao
2010-07-22 9:46 ` Eric Dumazet
2010-07-22 9:52 ` Changli Gao
2010-07-22 9:59 ` Eric Dumazet [this message]
2010-07-22 10:06 ` Changli Gao
2010-07-23 10:54 ` Patrick McHardy
2010-07-22 12:24 ` Simon Horman
2010-07-22 12:59 ` Eric Dumazet
2010-07-22 13:20 ` Simon Horman
2010-07-22 18:45 ` Franchoze Eric
2010-07-22 13:25 ` Simon Horman
2010-07-22 16:59 ` Franchoze Eric
2010-09-20 5:56 ` Simon Horman
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=1279792792.2467.15.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=franchoze@yandex.ru \
--cc=jengelh@medozas.de \
--cc=kaber@trash.net \
--cc=lvs-devel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=wensong@linux-vs.org \
--cc=xiaosuo@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox