From: ZHOU Xiaobo <xb.zhou@qq.com>
To: netfilter@vger.kernel.org
Subject: Re: Problem with NAT rule
Date: Sun, 25 Jul 2010 00:29:35 +0800 (CST) [thread overview]
Message-ID: <31824524.281279988971776.JavaMail.ZHOU-PC$@zhou-PC> (raw)
In-Reply-To: <AANLkTimObW0P6o+Ei8=PXVuHfU07KBqMFcMWNepvpEVW@mail.gmail.com>
I think you should use IPROUTE2 instead of IPTABLES.
----- Original Message -----
From: "Pete Kay" <petedao@gmail.com>
To: "Jan Engelhardt" <jengelh@medozas.de>
Cc: netfilter@vger.kernel.org
Sent: 2010年 7 月 24日, 星期六 下午 10:09:46 GMT +08:00 Beijing / Chongqing / Hong Kong / Urumqi
Subject: Re: Problem with NAT rule
Hi Jan,
Sorry I am new to iptables setup. Could you give me some insight as
to how I can configure iptables to achieve the packet forwarding
function?
thanks,
P
On Sat, Jul 24, 2010 at 9:51 PM, Jan Engelhardt <jengelh@medozas.de> wrote:
> On Saturday 2010-07-24 15:41, Pete Kay wrote:
>
>>Hi,
>>
>>I would like to setup my iptable rules to forward udp packet from one
>>device to another:
>>
>>192.168.1.100:16385 <---------> 192.168.1.114:29848 :: 192.168.1.200
>>:29850 <----------> 192.168.1.300:10112
>>
>>What I want to do is forward all packets from 192.168.1.100:16385 to
>>192.168.1.300:10112 and all packets from 192.168.1.300:10112 to
>>192.168.1.100:16385
>>
>>Here is my iptables rule:
>
>
> Routing does forwarding; nf_nat does NAT, those are two separate things.
>
>
--
To unsubscribe from this list: send the line "unsubscribe netfilter" 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-24 16:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-24 13:41 Problem with NAT rule Pete Kay
2010-07-24 13:51 ` Jan Engelhardt
2010-07-24 14:09 ` Pete Kay
2010-07-24 16:29 ` ZHOU Xiaobo [this message]
2010-07-24 16:13 ` Pieter Smit
2010-07-25 8:38 ` Pete Kay
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='31824524.281279988971776.JavaMail.ZHOU-PC$@zhou-PC' \
--to=xb.zhou@qq.com \
--cc=netfilter@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 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.