From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: What is missed for port forwarding
Date: Sat, 6 Mar 2004 18:47:28 +0000 [thread overview]
Message-ID: <200403061847.28569.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <20040306183657.GB836@glorybox.de>
On Saturday 06 March 2004 6:36 pm, Kai Weber wrote:
> I have a router where only masquerading and some QOS is enabled. I have
> a problem with port forwarding HTTP.
>
> The only rules I use (sorry for long lines):
(Sorry my mailer has wrapped them)
> $IPTABLES -t nat -A POSTROUTING -o ppp0 -j MASQUERADE
> $IPTABLES -t nat -A PREROUTING -p tcp --dport 10143 -j DNAT --to
> 192.168.1.2:22
> $IPTABLES -t nat -A PREROUTING -p tcp --dport 8888 -i ppp0
> -j DNAT --to 192.168.1.2:80
>
> The first DNAT rule works without a problem. I can ssh directly to my
> machine.
Which machine is that (192.168.1.2)? Is it the machine running the above
rules, or another machine on yur internal LAN, with packets being routed by
the netfilter box?
> But the requests to port 8888 seems not to be answered or come
> through. To bad I only have switch which has no port mirroring to listen
> to the whole traffic and find out the problem.
>
> Any ideas what I should try or I miss?
Do you have a FORWARD rule allowing traffic to 192.168.1.2:80?
Do you have a rule allowing the reply packets (probably an ESTABLISHED,RELATED
rule)?
What happens if you telnet to port 80 on 192.168.1.2? Is there a service
listening on that port?
Antony.
--
If builders made buildings the way programmers write programs, then the first
woodpecker to come along would destroy civilisation.
Please reply to the list;
please don't CC me.
next prev parent reply other threads:[~2004-03-06 18:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-06 18:36 What is missed for port forwarding Kai Weber
2004-03-06 18:47 ` Antony Stone [this message]
2004-03-07 9:40 ` Kai Weber
2004-03-07 9:53 ` Antony Stone
2004-03-07 15:49 ` Kai Weber
2004-03-07 16:02 ` Antony Stone
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=200403061847.28569.Antony@Soft-Solutions.co.uk \
--to=antony@soft-solutions.co.uk \
--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