All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mart Frauenlob <mart.frauenlob@chello.at>
To: netfilter@vger.kernel.org
Subject: Re: multiport needs `-p tcp', `-p udp' - Why?
Date: Sun, 28 Feb 2010 15:41:39 +0100	[thread overview]
Message-ID: <4B8A80A3.80806@chello.at> (raw)
In-Reply-To: <4B8A76D8.5030800@gatworks.com>

On 28.02.2010 14:59, netfilter-owner@vger.kernel.org wrote:
> 
> 
> On 02/28/2010 01:54 AM, Mart Frauenlob wrote:
>>> >  I dont want to test over (( and over ) and over ) again when I
>>> know that
>>> >  the packet is already KNOWN to be from eth1 and of protocol UDP.
>> now if we add -p icmp -j PRE_UDP,  what should iptables do now?
>>
>> use 'ferm' if you are too lazy to write iptables rules:
>> http://ferm.foo-projects.org/
>>
>>> >
> Do what *I* say it should be doing. Do the jump. None of the tests in
> PRE_UDP chain would/should match, and the packet should fall out by the
> default policy of the chain. An iptable optimizer would recognize that
> the chain only tests for UDP, and would change the -p icmp -j PRE_UDP to
> -p icmp -j $(default policy) without going through any of the chain.

which of the 2 jumps is to give precedence?
how to judge? read your mind?

> 
> BTW: its not lazy to write efficient code.

ok, don't be lazy write the netfilter chain/jump optimizer :)
Because such a thing does not exist, netfilter will not do what you want.



  reply	other threads:[~2010-02-28 14:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-27 15:03 multiport needs `-p tcp', `-p udp' - Why? U. George
2010-02-27 15:06 ` ratheesh k
2010-02-27 16:17   ` U. George
2010-02-27 16:46     ` ratheesh k
2010-02-27 17:28       ` U. George
2010-02-27 17:18     ` Dennis J.
2010-02-28  6:54     ` Mart Frauenlob
2010-02-28 10:53       ` ratheesh k
2010-02-28 13:59       ` U. George
2010-02-28 14:41         ` Mart Frauenlob [this message]
2010-02-28 15:17           ` U. George
     [not found] <4b8984a7.0ab6660a.24bd.1f7f@mx.google.com>
2010-02-27 21:14 ` U. George
2010-02-28  4:46   ` ratheesh k
2010-02-28  6:38     ` Mart Frauenlob

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=4B8A80A3.80806@chello.at \
    --to=mart.frauenlob@chello.at \
    --cc=netfilter@vger.kernel.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.