All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Christensen <pch@coolsystems.dk>
To: Allen Francom <aef@prismnet.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: Statefull SOCKS filter
Date: Fri, 10 Mar 2006 13:02:11 +0100	[thread overview]
Message-ID: <44116AC3.1050506@coolsystems.dk> (raw)
In-Reply-To: <20060309104524.B75323@tempest.prismnet.com>

Hmm, I think I'll just do the connection state maintenance manually... 
Hopefully I will be able to do it reasonable fast.

--
Best regards

Peter Christensen

Developer
------------------
Cool Systems ApS

Tel: +45 2888 1600
  @ : pch@coolsystems.dk
www: www.coolsystems.dk


Allen Francom wrote:
> 
> 
> Once upon a time I interacted with a project called "Hogwash".
> 
> This was all layer 2 and seemed to be off to a great start.
> 
> Sounds more like what you need, "transparent".
> 
> The maintainer resigned, however the code ran, based on
> Snort and associated libraries.
> 
> With a lot of help from others, I made a binding
> for these rules into IPTables via the QUEUE target... but
> that wasn't all that clean.  Maybe skip the IPTables
> entirely, and "do like hogwash did".
> 
> 2 cents...
> 
> On Thu, 9 Mar 2006, Peter Christensen wrote:
>> I'm currently in the development of a transparent firewall bridge, 
>> whose sole purpose is to filter our everything but LAN traffic and 
>> traffic for a list of privileged servers on the Internet. Since it is 
>> meant to work on an bunch of different network configurations 
>> out-of-box, it must be able to detect and filter proxy traffic as well.

      reply	other threads:[~2006-03-10 12:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-09 12:16 Statefull SOCKS filter Peter Christensen
2006-03-09 13:08 ` Alexey Toptygin
2006-03-09 13:45   ` Peter Christensen
2006-03-09 16:49 ` Allen Francom
2006-03-10 12:02   ` Peter Christensen [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=44116AC3.1050506@coolsystems.dk \
    --to=pch@coolsystems.dk \
    --cc=aef@prismnet.com \
    --cc=netfilter-devel@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 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.