From: Harald Welte <laforge@netfilter.org>
To: Sven Schuster <schuster.sven@gmx.de>
Cc: Alessandro Suardi <alessandro.suardi@gmail.com>,
netdev@oss.sgi.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
netfilter-devel@lists.netfilter.org
Subject: Re: oops in 2.6.13-rc6-git12 in tcp/netfilter routines
Date: Fri, 26 Aug 2005 10:35:27 +0200 [thread overview]
Message-ID: <20050826083527.GD4226@rama.de.gnumonks.org> (raw)
In-Reply-To: <20050825210200.GA10374@zion.homelinux.com>
[-- Attachment #1: Type: text/plain, Size: 1057 bytes --]
On Thu, Aug 25, 2005 at 11:02:01PM +0200, Sven Schuster wrote:
>
> Hi Harald,
>
> On Thu, Aug 25, 2005 at 06:55:50PM +0200, Harald Welte told us:
> > Is it true that PeerGuardian is a proprietary application? I'm not
> > going to debug this problem using a proprietary ip_queue program, sorry.
>
> sorry to jump in here, but I took a quick look at PeerGuardian,
> according to
> http://methlabs.org/wiki/license_information
> it's open source. The source code is available at
> http://methlabs.org/projects/peerguardian-linuxosx/
ok, thanks. Sorry for the confusion, but the 'official' website is just
a blog that didn't really reveal all that much information.
--
- Harald Welte <laforge@netfilter.org> http://netfilter.org/
============================================================================
"Fragmentation is like classful addressing -- an interesting early
architectural error that shows how much experimentation was going
on while IP was being designed." -- Paul Vixie
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-08-26 8:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-25 13:39 Alessandro Suardi
2005-08-25 16:55 ` Harald Welte
2005-08-25 17:26 ` Alessandro Suardi
2005-08-25 21:02 ` Sven Schuster
2005-08-26 8:35 ` Harald Welte [this message]
2005-08-26 17:52 ` Patrick McHardy
2005-08-26 20:40 ` Alessandro Suardi
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=20050826083527.GD4226@rama.de.gnumonks.org \
--to=laforge@netfilter.org \
--cc=alessandro.suardi@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=netfilter-devel@lists.netfilter.org \
--cc=schuster.sven@gmx.de \
/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
all inboxes | Powered by JetHome®