From: Jasbir Khehra <jasbir.k@gmail.com>
To: Mike <1100100@gmail.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: NAT PREROUTING vs. filter FORWARD
Date: Fri, 20 Oct 2006 11:02:14 +0530 [thread overview]
Message-ID: <45385F5E.5070408@gmail.com> (raw)
In-Reply-To: <8ca422820610191125k16f58f03t3ce33bd4e1d22c28@mail.gmail.com>
Mike wrote:
> I'm having difficulty with clients connecting to a game I'm hosting
> over the internet.
> So I'm wondering if my PREROUTING rule is conflicting with my FORWARD
> rule.
>
>
> Then I should not have to worry about these FORWARD rules interfering
> with the prerouted data getting to the server at 192.168.170.6 ---
>
> $IPTABLES -t filter -A FORWARD -i ppp0 -o eth1 -m state --state
> ESTABLISHED,RELATED -j ACCEPT
> $IPTABLES -t filter -A FORWARD -i ppp0 -o eth2 -m state --state
> ESTABLISHED,RELATED -j ACCEPT
>
> Am I right or wrong?
> If wrong, is the only way then to change the FORWARD rule to -j ACCEPT
> and leave out the ESTABLISHED,RELATED requirement?
You just missing out on the rule to accept NEW state connections on your
game ports
$IPTABLES -t filter -A FORWARD -i ppp0 -m state --state NEW -p tcp -m
multiport --dports 34297,34397,34447 -j ACCEPT
Same rule for udp connections.
>
> Thanks for your time and assistance.
>
> Mike
HTH,
Jasbir
next prev parent reply other threads:[~2006-10-20 5:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-19 18:25 NAT PREROUTING vs. filter FORWARD Mike
2006-10-19 18:27 ` Mike
2006-10-20 5:32 ` Jasbir Khehra [this message]
2006-10-20 13:36 ` Mike
2006-10-20 15:14 ` Martijn Lievaart
[not found] ` <4429765974127559812@unknownmsgid>
2006-10-20 17:04 ` Mike
2006-10-21 6:46 ` Martijn Lievaart
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=45385F5E.5070408@gmail.com \
--to=jasbir.k@gmail.com \
--cc=1100100@gmail.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 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.