From: Joel Newkirk <netfilter@newkirk.us>
To: "James D. Parra" <JamesP@MusicReports.com>
Cc: "Netfilter (E-mail)" <netfilter@lists.netfilter.org>
Subject: Re: iptable woes
Date: 21 Apr 2003 19:25:57 -0400 [thread overview]
Message-ID: <1050967556.24606.144.camel@alpha.newkirk.us> (raw)
In-Reply-To: <9EC6A5A6B11DA843A551CC9AD9323FAC3014@exchange.musicreports.com>
On Mon, 2003-04-21 at 17:55, James D. Parra wrote:
> Hello,
>
> Try as I may, I cannot get packets to go through the firewall from the
> public side to the private side. I have set up scripts that should work, as
> written from Netfilter, but there must be something I am overlooking.
Yep... ;^)
> # TCP Rules
> iptables -A INPUT -p TCP -i eth1 -s 0/0 --destination-port 1723 -j okay
> iptables -A INPUT -p tcp -i eth1 -s 0/0 --destination-port 80 -j okay
dport 80 not needed, since you're DNATting it anyway.
> # (4) FORWARD chain rules
> # Accept packets we want to forward
> iptables -A FORWARD -i eth0 -j ACCEPT
> iptables -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT
> iptables -A FORWARD -i eth1 -o eth0 -p tcp --sport 1024:65535 -d
> PVT.XXX.XXX.XXX --dport 80 \
> -m state --state NEW -j ACCEPT
> iptables -A FORWARD -i eth1 -o eth0 -m state --state ESTABLISHED,RELATED -j
> ACCEPT
This last is also unneeded, since you have a more general state rule
just above it.
> # (6) PREROUTING chain rules
> iptables -t nat -A PREROUTING -i eth1 -p tcp --sport 80 -d PUB.XXX.XXX.XXX
> --dport 80 \
> -j DNAT --to-destination PVT.XXX.XXX.XXX:80
> iptables -t nat -A PREROUTING -p tcp -d --dport 1723 -j DNAT
> --to-destination PVT.XXX.XXX.XXX
Ah, the meat of the problem... You're matching ONLY packets with BOTH
dport AND sport of 80... Drop the "--sport 80" part and you should be
all set to server http.
j
next prev parent reply other threads:[~2003-04-21 23:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-21 21:55 iptable woes James D. Parra
2003-04-21 23:25 ` Joel Newkirk [this message]
2003-04-21 23:28 ` Sascha Reissner
-- strict thread matches above, loose matches on Subject: below --
2003-04-22 18:05 James D. Parra
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=1050967556.24606.144.camel@alpha.newkirk.us \
--to=netfilter@newkirk.us \
--cc=JamesP@MusicReports.com \
--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