Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Eric Leblond <eric@inl.fr>
To: halfdog@gmx.at
Cc: netfilter@lists.netfilter.org
Subject: Re: User space firewall
Date: Wed, 24 May 2006 19:11:28 +0200	[thread overview]
Message-ID: <1148490688.13582.20.camel@localhost.localdomain> (raw)
In-Reply-To: <44749333.5080805@gmx.at>

[-- Attachment #1: Type: text/plain, Size: 1177 bytes --]

Le mercredi 24 mai 2006 à 19:09 +0200, halfdog@gmx.at a écrit :
> Hi all,
> 
> I want to write a (simple) user space firewall. All packets not acceptable for 
> the iptables go to as netlink message (ulog) to the user space. All established 
> connections are kept. The user is then to decide, if he accepts the connection.

have you heard about libnetfilter_queue (or ip_queue). This is done for
that. Do NOT use ulog to do this!

See http://www.netfilter.org/ for information about libnetfilter_queue.

For code example, you can have a look at NuFW : http://www.nufw.org/

BR,

> 
> Use case: Lets assume a Tcp-Syn hits the iptables, gets rejected, captured by my 
> software. What should I do to make the connection stable?
> 
> * Just push the Syn into the stack again, will this make the connection 
> established? If yes, where to put it so that I do not have to care about Nat and 
> so on, so it should go rather the same way an accepted packet would have gone.
> 
> * Modify the conntrack tables first and then push the syn back?
> 
> * Do I have to go an more complicated way?
> 
> Thanks for your input,
> 
> halfdog
> 
> 
> 
> 


[-- Attachment #2: Ceci est une partie de message numériquement signée --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2006-05-24 17:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-24 17:09 User space firewall halfdog
2006-05-24 17:11 ` Eric Leblond [this message]

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=1148490688.13582.20.camel@localhost.localdomain \
    --to=eric@inl.fr \
    --cc=halfdog@gmx.at \
    --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