Linux Netfilter discussions
 help / color / mirror / Atom feed
From: SBlaze <dagent.geo@yahoo.com>
To: Cedric Blancher <blancher@cartel-securite.fr>
Cc: netfilter@lists.netfilter.org
Subject: Re: state matching vrs prerouting.... ???
Date: Fri, 21 Mar 2003 12:37:06 -0800 (PST)	[thread overview]
Message-ID: <20030321203706.30847.qmail@web40208.mail.yahoo.com> (raw)
In-Reply-To: <1048259686.6912.10.camel@elendil.intranet.cartel-securite.net>

--- Cedric Blancher <blancher@cartel-securite.fr> wrote:
> Le ven 21/03/2003 à 15:53, SBlaze a écrit :
> > # iptables -A INPUT -p udp -i eth0 -m state --state NEW,INVALID -j DROP
> > # iptables -A INPUT -p udp -i eth0 -m state --state ESTABLISHED,RELATED -j
> > ACCEPT
> > 
> > # CounterStrike NAT Line
> > #
> > iptables -t nat -A PREROUTING -p udp --dport 27015 -i eth0 -j DNAT
> > --to-destination 192.168.1.25:27015
> > 
> > Ok the UDP filters physically come before my CounterStrike line. In reading
> > Oskar's tutorial I as under the impression that the nat tables rules took
> > precedence before the filter tables....
> 
> They have. Moreover, there's no filter chain at NF_IP_PRE_ROUTING hook.
> 
> > However the UDP rules drop the incoming CS requests before they are
> > prerouted... What gives? 
> 
> Once your packet has been handled by NAT stuff, it has to be authorized
> by filter stuff. In your ruleset, two things are quite strange to me.
> 
> First, your filtering rules are in INPUT chain. As far as I understand
> your point, you are trying to nat CS stuff to an internal host. So
> packets will get routed, and so have to be filtered in FORWARD chain.
> 
> Second, you drop packets with state NEW. If you do so, no one will be
> able to connect.
> 
> 
> -- 
> Cédric Blancher  <blancher@cartel-securite.fr>
> IT systems and networks security expert  - Cartel Sécurité
> Phone : +33 (0)1 44 06 97 87 - Fax: +33 (0)1 44 06 97 99
> PGP KeyID:157E98EE  FingerPrint:FA62226DA9E72FA8AECAA240008B480E157E98EE
> 
 That is somewhat correct. What I read in Oskar's tutorial led me to believe
that i could preroute the CS requests so that they would in a sence bypass or
not pass through the UDP input filters. I am somewhat confused as to why they
do?





=====
"No touchy NO TOUCHY! Emperor Kuzko -=Emperor's New Groove=-"

__________________________________________________
Do you Yahoo!?
Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!
http://platinum.yahoo.com


  reply	other threads:[~2003-03-21 20:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-21 14:53 state matching vrs prerouting.... ??? SBlaze
2003-03-21 15:14 ` Cedric Blancher
2003-03-21 20:37   ` SBlaze [this message]
2003-03-24  8:43     ` Cedric Blancher

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=20030321203706.30847.qmail@web40208.mail.yahoo.com \
    --to=dagent.geo@yahoo.com \
    --cc=blancher@cartel-securite.fr \
    --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