From: Patrick McHardy <kaber@trash.net>
To: Ondrej Slanina <oslanina@kerio.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: Fw: Netfilter for Windows
Date: Thu, 15 Apr 2010 12:35:40 +0200 [thread overview]
Message-ID: <4BC6EBFC.3020204@trash.net> (raw)
In-Reply-To: <E1065721E84E443C803CD31BFE864396@kerio.local>
Ondrej Slanina wrote:
> I just created a basic 'port' of Linux netfilter core modules on MS
> Windows. Now, it's implemented as a single kernel module (IM driver) and
> userspace library which has the same API as libnetfilter_queue. Network
> filtering is now performed only on pre_input and post_output sides.
> Kernel module now includes packet queueing, processing, not as on Linux,
> where this tasks is processed by separate modules. It will be
> distributed under GPL. I have some questions:
Cool. Finally those poor souls can use a proper firewall :)
> 1, Can I use 'netfilter' and 'libnetfilter_queue' names for this? For
> example kernel module named netfilter.sys, userspace library named
> libnetfilter_queue.lib, project name netfilter, netfilter for windows or
> something like it?
I think using the same names is fine.
> 2, Should I put some notice about origin into source code files ?
> Something like: "Based on Linux netfilter/libnetfilter_queue" ?
Just keeping the original copyright and GPL headers is fine.
> My implementation is now very primitive, but I want to extend it in the future.
Please keep us posted. I guess we could also host the source on
one of the netfilter servers in case you're interested.
next prev parent reply other threads:[~2010-04-15 10:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-15 9:02 Fw: Netfilter for Windows Ondrej Slanina
2010-04-15 10:35 ` Patrick McHardy [this message]
2010-04-15 12:21 ` Bruno Moreira Guedes
2010-04-15 12:51 ` Ondrej Slanina
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=4BC6EBFC.3020204@trash.net \
--to=kaber@trash.net \
--cc=netfilter-devel@vger.kernel.org \
--cc=oslanina@kerio.com \
/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.