Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "John A. Sullivan III" <john.sullivan@nexusmgmt.com>
To: Manestro Oliveira <manestro123@hotmail.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: bypassing a prerouting rule
Date: Thu, 24 Jun 2004 03:18:18 -0400	[thread overview]
Message-ID: <1088060134.24608.35.camel@localhost> (raw)
In-Reply-To: <BAY22-F8GvaIyuw4n4a0009ebc4@hotmail.com>

On Wed, 2004-06-23 at 09:24, Manestro Oliveira wrote:
> Hi,
>       I am a begginer to Linux and I have a PREROUTING rule that makes port 
> redirection on incoming packages. But there is a server that don`t accept 
> that, and works only without that rule. How can I bypass the rule for that 
> server specifically?
> 
>      If iptables works by matching rules and leaving the other ones without 
> checking them, then I should insert a rule before that and the problem is 
> solved. Is this correct?
> 
>      Sorry if the question might be stupid, but I am taking the chance for 
> being stupid now (and maybe not forever). >)
<snip>
Yes, you can place an ACCEPT rule before the REDIRECT rule and that will
halt processing in the PREROUTING chain for that match.  Thanks for
asking :-) - John
-- 
John A. Sullivan III
Chief Technology Officer
Nexus Management
+1 207-985-7880
john.sullivan@nexusmgmt.com
---
If you are interested in helping to develop a GPL enterprise class
VPN/Firewall/Security device management console, please visit
http://iscs.sourceforge.net 



  parent reply	other threads:[~2004-06-24  7:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-23 13:24 bypassing a prerouting rule Manestro Oliveira
2004-06-24  5:07 ` Feizhou
2004-06-24  7:18 ` John A. Sullivan III [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-06-25 17:27 Manestro Oliveira

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=1088060134.24608.35.camel@localhost \
    --to=john.sullivan@nexusmgmt.com \
    --cc=manestro123@hotmail.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