From: "Василий Свиридов" <netspider@mail.ru>
To: netfilter@lists.netfilter.org
Subject: Re: Fedora Core 2. Port Forwarding Problems
Date: Sat, 24 Jul 2004 13:12:19 -0700 [thread overview]
Message-ID: <4102C2A3.5090007@mail.ru> (raw)
In-Reply-To: <200407241555.16611.Antony@Soft-Solutions.co.uk>
[-- Attachment #1: Type: text/plain, Size: 2471 bytes --]
Antony Stone wrote:
>On Saturday 24 July 2004 4:25 am, Василий Свиридов wrote:
>
>
>
>>I've installed fedora core 2 and tried to reuse my old settings i
>>retained from redhat9 system.
>>
>>Masqeurading works fine, but when i try to do port forwarding like this
>>iptables -t nat -A PREROUTING -p tcp -d <domainname.com> --dport 80 -j
>>DNAT --to 192.168.20.40:80
>>rule adds itself fine, but port 80 is not accessible from outside.
>>
>>
>
>Are you sure about the resolving of domainname.com? What does the rule get
>added as?
>
>
It simply resolves the address and adds the IP.
>
>
>>when i try to connect from outside it doesn't say connection refused, it
>>dies after a timeout.
>>/proc/net/ip_conntrack doesn't show any presence of connection, I tried
>>to send it to -j LOG & ULOG but both end up empty.
>>
>>
>
>Please show us your ruleset. We would like to see:
> - what IP address the above PREROUTING rule gets installed with
> - the corresponding FORWARD rule for the packets
> - an appropriate reply packet rule
> - how you have been LOGging packets for testing
>
>I suggest the output of "iptables -L -nvx; iptables -L -t nat -nvx" and if
>appropriate also "iptables -L -t mangle -nvx" is a good format for us to
>understand where you're starting from.
>
>Regards,
>
>Antony.
>
>
>
iptables -L -nvx doesn't contain any rules yet.
[root@border root]# iptables -L -t nat -nvx
Chain PREROUTING (policy ACCEPT 5913 packets, 353422 bytes)
pkts bytes target prot opt in out
source destination
8 408 DNAT tcp -- * *
0.0.0.0/0 207.6.196.64 tcp dpt:80 to:192.168.20.40:80
Chain POSTROUTING (policy ACCEPT 4 packets, 244 bytes)
pkts bytes target prot opt in out
source destination
744 42337 MASQUERADE all -- * eth0
0.0.0.0/0 0.0.0.0/0
11 588 SNAT tcp -- * *
0.0.0.0/0 192.168.20.40 ctstate DNAT tcp dpt:80
to:207.6.196.64
Chain OUTPUT (policy ACCEPT 123 packets, 7641 bytes)
pkts bytes target prot opt in out
source destination
3 180 DNAT tcp -- * *
0.0.0.0/0 207.6.196.64 tcp dpt:80 to:192.168.20.40:80
This kind of configuration worked just fine on RH9. But it wasn't
working on it when I've tried to install kernel 2.6.6.
Thanks.
[-- Attachment #2: Type: text/html, Size: 3393 bytes --]
next prev parent reply other threads:[~2004-07-24 20:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-24 3:25 Fedora Core 2. Port Forwarding Problems Василий Свиридов
2004-07-24 14:55 ` Antony Stone
2004-07-24 20:12 ` Василий Свиридов [this message]
[not found] ` <+nfcan+jimlaur+c1d788382f.netspider#mail.ru@spamgourmet.com>
[not found] ` <netspider@mail.ru>
2004-07-25 23:48 ` Fedora Core 2. Port Forwarding Problems (nfcan: addressed to exclusive sender for this address) Jim Laurino
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=4102C2A3.5090007@mail.ru \
--to=netspider@mail.ru \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox