All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eliezer Croitoru <eliezer@ngtech.co.il>
To: netfilter@vger.kernel.org
Subject: Re: conntrack GRE behaves differently in 3.17 / 3.18
Date: Thu, 22 Jan 2015 17:40:20 +0200	[thread overview]
Message-ID: <54C119E4.1050208@ngtech.co.il> (raw)
In-Reply-To: <54C0CC79.3010001@chello.at>

Hey,

The way iptables rules are working is "first match" so in the case of an 
ACCEPT rule it will only be ACCEPTED if it matches the rule else it will 
try the next rule.
Always there was a need to add two rules to match an ESTABLISHED,RELATED.
1 - For the NEW state
2 - For the ESTABLISHED,RELATED

As long these rules are there with an ACCEPT target it will always be fine.

The main consideration is what will be faster to match from the two?
 From what I have seen until now FW rules usually have an 
ESTABLISHED,RELATED rule first and then the other NEW rules.

If it's right to "hijack" the thread for this particular case:
Which is better to be first?

Eliezer

On 22/01/2015 12:10, Mart Frauenlob wrote:
> Hello,
>
> the way I understand the change is:
> you need to add an according iptables rule for the first state NEW
> packet, which will then load the according conntrack helper
> automatically. So further packets are classified as ESTABLISHED or RELATED.
> There is no mechanism of unloading a module once it has been loaded afaik.



  reply	other threads:[~2015-01-22 15:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-19 13:04 conntrack GRE behaves differently in 3.17 / 3.18 Jan Niggemann
2015-01-21  2:01 ` Eliezer Croitoru
2015-01-21 13:19   ` Jan Niggemann
2015-01-21 14:33     ` Mart Frauenlob
2015-01-21 19:03       ` Jan Niggemann
2015-01-21 23:21         ` Pascal Hambourg
2015-01-22  7:55           ` Jan Niggemann
2015-01-22 10:10             ` Mart Frauenlob
2015-01-22 15:40               ` Eliezer Croitoru [this message]
2015-01-22 18:51                 ` Neal Murphy
2015-01-22 20:33               ` Pascal Hambourg
2015-01-22 21:51                 ` Jan Niggemann
2015-01-22 22:28                   ` Neal Murphy
2015-01-23 23:20                 ` Mart Frauenlob
2015-01-24  7:44                   ` Jan Niggemann
2015-01-24 15:28                     ` Mart Frauenlob
2015-01-24 20:07                       ` Pascal Hambourg
     [not found] <1430142363.3948.12.camel@alum.wpi.edu>
2015-04-27 13:47 ` Lubomir Rintel

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=54C119E4.1050208@ngtech.co.il \
    --to=eliezer@ngtech.co.il \
    --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.