From: Harald Welte <laforge@gnumonks.org>
To: Georg Chini <georg.chini@triaton-webhosting.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Sparc 32/64 - freeswan - iptables
Date: Mon, 4 Nov 2002 09:50:40 +0100 [thread overview]
Message-ID: <20021104095040.F8635@sunbeam.de.gnumonks.org> (raw)
In-Reply-To: <3DC5AE86.7010404@triaton-webhosting.com>; from georg.chini@triaton-webhosting.com on Mon, Nov 04, 2002 at 12:17:26AM +0100
[-- Attachment #1: Type: text/plain, Size: 1311 bytes --]
On Mon, Nov 04, 2002 at 12:17:26AM +0100, Georg Chini wrote:
> Hi,
>
> when I try to use freeswan on my sparcs, I have the following problems:
The question seems off-topic on the generic kernel mailinglist then.
freeswan is developed outside the kernel and not part of the kernel, it
has it's own mailinglists (see http://www.freeswan.org).
Netfilter/iptables _is_ part of the kernel but also has it's own
development-oriented mailinglist (netfilter-devel@lists.netfilter.org)
From my (netfilter) point of view: netfilter and iptables work on both
sparc32 and sparc64. There's a single known bug in the sparc64 iptables
implementation, but it's only about the per-rule packet and byte counters.
> Can anyone help me to solve one of my problems?
As long as there's nobody pointing me more directly to a particular issue,
no. Sorry. I don't have the time to test freeswan on a sparc system.
> Thanks in advance
> Georg Chini
--
Live long and prosper
- Harald Welte / laforge@gnumonks.org http://www.gnumonks.org/
============================================================================
"If this were a dictatorship, it'd be a heck of a lot easier, just so long
as I'm the dictator." -- George W. Bush Dec 18, 2000
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
prev parent reply other threads:[~2002-11-04 8:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-03 23:17 Georg Chini
2002-11-04 8:50 ` Harald Welte [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=20021104095040.F8635@sunbeam.de.gnumonks.org \
--to=laforge@gnumonks.org \
--cc=georg.chini@triaton-webhosting.com \
--cc=linux-kernel@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 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®