Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Yoann Juet <yoann.juet@univ-nantes.fr>
To: netfilter@vger.kernel.org
Subject: NFQUEUE target + queue-bypass option, expected behavior
Date: Thu, 13 Feb 2014 17:20:29 +0100	[thread overview]
Message-ID: <52FCF0CD.9030202@univ-nantes.fr> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1700 bytes --]

Hi all,

I have two questions about NFQUEUE target and queue-bypass option. To 
begin with, what is the expected behavior with iptables v1.4.14 ?

(*) extract from the manual page of iptables v1.4.14:
        --queue-bypass
	[...] When this option is used, the NFQUEUE rule is silently
	bypassed instead. The packet will move on to the next rule.

(*) extract from the manual page of iptables-extensions v1.4.20+:
        --queue-bypass
	[...] When this option is used, the NFQUEUE rule behaves like
	ACCEPT instead, and the packet will move on to the next table.

On a standard debian/stable machine (wheezy, iptables v1.4.14), all 
packets are accepted if no userspace program is listening on an NFQUEUE. 
Next iptables rules are never matched. A man-page mistake ?

Assuming that this is the expected behavior (ACCEPT), a second question 
arises. I'd like to merge on a single machine firewall 
(netfilter/iptables) and IPS (suricata) services. In case of suricata 
failure, the firewall should run into a degraded state where packets 
move on to the next rule (i.e. to L3/L4 firewall rules). Is it 
technically possible with iptables v1.4.14 or higher versions ? In my 
point of view, omitting queue-bypass option could be too disruptive for 
a L7 firewall whereas inserting it is far too permissive.

---
Just to refine my setup, the following rule is added at the first 
position of the table FORWARD:

iptables -I FORWARD  -m mark ! --mark 1/1 -j NFQUEUE --queue-num 0 
[--queue-bypass]

All next rules are L3/L4 traditional firewall rules.

Regards,
-- 
Université de Nantes - Direction des Systèmes d'Information
IM jabber: yoann.juet@univ-nantes.fr

[-- Attachment #1.2: yoann_juet.vcf --]
[-- Type: text/x-vcard, Size: 360 bytes --]

begin:vcard
fn:Yoann Juet
n:Juet;Yoann
org;quoted-printable:Direction des Syst=C3=A8mes d'Information
adr;quoted-printable:BP 92208;;2 Rue de la Houssini=C3=A8re;Nantes Cedex 3;;44322;France
email;internet:yoann.juet@univ-nantes.fr
tel;work:02.53.48.49.26
tel;fax:02.53.48.49.09
tel;cell:06.73.15.42.19
x-mozilla-html:FALSE
version:2.1
end:vcard


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3256 bytes --]

             reply	other threads:[~2014-02-13 16:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-13 16:20 Yoann Juet [this message]
2014-02-13 20:20 ` NFQUEUE target + queue-bypass option, expected behavior Eric Leblond
2014-02-14 12:44   ` Yoann Juet

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=52FCF0CD.9030202@univ-nantes.fr \
    --to=yoann.juet@univ-nantes.fr \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox