From: Jeho Park <jhpark-nf-user@kernelproject.org>
To: Lars Nixdorf <lars.nixdorf@genion.de>
Cc: netfilter@lists.netfilter.org
Subject: Re: netfilter .. (openswan) nat problem ..
Date: Wed, 07 Jun 2006 08:06:48 +0900 [thread overview]
Message-ID: <44860A88.4000502@kernelproject.org> (raw)
In-Reply-To: <01e201c689ac$c55351b0$c964a8c0@sol>
as i know, this problem was patched from 2.6.16
so you will need to upgrade kernel or apply that patch
Lars Nixdorf wrote:
>i have to solv the following problem (debian 3.1, kernel 2.6.14 from kernel
>org, no patches, openswan 2.x.x maybe important):
>
>netA - gwA - gwB - netB - internet, where
>
>netA: 192.168.0.0/24
>gwA: 192.168.0.1 + pppoe-ip-addr
>gwB: 100.100.100.100 (static official ip)
>netB: 100.100.100.100/32 (no real subnet)
>
>gwA and gwB are both real gateways
>
>tunnel works in the following way:
>
>netA/gwA to netB/gwB and netB/gwB to netA/gwA, all I think .
>
>now I want to forward a spezial port on gwB, perhaps 50000 to an address in
>netA (192.168.0.100:50000), ok np from gwB, but ! I could not connect from
>the internet over gwB to this spezial host
>
>my nat rules, nothing else ..
>
>iptables -t nat -A PREROUTING -j DNAT -p tcp -s 0/0 --dport 50000
>--to-destination 192.168.0.100:50000 -i eth0 iptables -t nat -A POSTROUTING
>-j SNAT -p tcp -d 192.168.0.100 --dport 50000 --to 100.100.100.100 -o eth0
>
>tcpdump tell me that all nat works, but no traffic on gwA interfaces
>received. gwB send it, but I have a [DF] in that lines, maybe important, I
>doesn't know
>
>any suggestions? someone could help?
>
>
>
>regards, ji
>
>
>
>
>
>
>
>
next prev parent reply other threads:[~2006-06-06 23:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-06 21:04 netfilter .. (openswan) nat problem Lars Nixdorf
2006-06-06 23:06 ` Jeho Park [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-06 21:00 ji'e'toh
2006-06-07 11:36 ` Sietse van Zanen
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=44860A88.4000502@kernelproject.org \
--to=jhpark-nf-user@kernelproject.org \
--cc=lars.nixdorf@genion.de \
--cc=netfilter@lists.netfilter.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.