All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darryl Miles <darryl-mailinglists@netbauds.net>
To: netfilter-devel@vger.kernel.org
Subject: Can NFQUEUE accept/continue when there is no userspace listener registered ?
Date: Thu, 04 Nov 2010 03:52:40 +0000	[thread overview]
Message-ID: <4CD22E08.2060300@netbauds.net> (raw)


Hi,

Is there any mechanism which would allow additional options to NFQUEUE 
target to instruct the kernel what to do:

  --action-no-listener NF_ACCEPT|NF_DROP|CONTINUE  (with NF_DROP being 
the default)
  --action-backlog-overflow NF_ACCEPT|NF_DROP|CONTINUE   (with NF_DROP 
being the default)

Where CONTINUE would in effect ignore the existence of the "-j NFQUEUE" 
rule in the chain and continue to the next rule.  I guess this is 
possible if the packet never made it to user-space.


Would there be any objections to providing a patch to kernel and 
userspace tooling to provide this configurable behavior ?   Is it 
obviously useful to others ?


I am writing a non-critical userspace tool to fire Wake-on-LAN magic 
packets, if incoming TCP SYN "-p tcp --syn" is matched (and presumably 
forwarded).  The SYN packet is always allowed to pass but the userspace 
tools then goes into monitoring mode in the period after each SYN 
packet, it looks for either a valid IPv4 or IPv6 neighbour entry 
(/sbin/ip neigh) and/or Echo Reply.  As well as periodically monitoring 
the last known MAC address for each destination IP/IP6 to auto-learn.

This is not a critical application, I am looking for a minimal CPU 
overhead on the router and a best-effort service.  It should never be 
the cause of a failure (to connect i.e. pass SYN packets) should it 
crash / not be running.


Your comments appreciated,

Darryl


             reply	other threads:[~2010-11-04  4:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-04  3:52 Darryl Miles [this message]
2010-11-04  4:37 ` Can NFQUEUE accept/continue when there is no userspace listener registered ? Patrick McHardy
2010-11-05  0:08   ` Pablo Neira Ayuso
2010-11-05  9:29     ` Patrick McHardy
2010-11-05  9:33       ` Pablo Neira Ayuso

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=4CD22E08.2060300@netbauds.net \
    --to=darryl-mailinglists@netbauds.net \
    --cc=netfilter-devel@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.