Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

tired of too many questions

  • Loading branch information...
commit 97be3181778c0b9a9822f6c81cabe172af09980a 1 parent 948a1b2
itojun authored
Showing with 65 additions and 20 deletions.
  1. +65 −0 kame/kame/racoon/doc/FAQ
  2. +0 −20 kame/kame/racoon/doc/README.build
View
65 kame/kame/racoon/doc/FAQ
@@ -0,0 +1,65 @@
+racoon FAQ
+KAME team
+$KAME: FAQ,v 1.1 2000/09/13 05:46:14 itojun Exp $
+
+
+Q: With what other IKE/IPsec implementation racoon is known to be interoperable?
+
+A:
+ see "IMPLEMENTATION" document supplied with KAME kit, or:
+ http://www.kame.net/dev/cvsweb.cgi/kame/IMPLMENTATION
+
+Q: How can I make racoon interoperate with <IKE/IPsec implementation>?
+
+A:
+ Basic rule: configure both end exactly the same.
+ (TBD)
+
+Q: How to build racoon on my platform?
+
+A: (NetBSD 1.5/current, FreeBSD 4.1/current)
+ To build racoon on these platforms, there are couple of ways:
+ - on NetBSD/FreeBSD integrated platforms, use pkgsrc/ports.
+ It is the easiest and recommended way.
+ - If you need to use configure.in and Makefile.in under
+ kame/kame/racoon, use the following operation:
+ % (cd ../../../bsdi4/lib; make)
+ % env LIBS=-L../../../bsdi4/lib/libpfkey CFLAGS=-I../../sys \
+ ./configure --with-libpfkey
+ % make
+ If you do not do the above, you may see missing symbols with pfkey_xx
+ functions, and/or mismatch in ipsec.h. PKGSRC/PORTS IS DEFINITELY
+ THE RECOMMENDED WAY.
+
+A: (KAME-patched platforms)
+ - on KAME-patched platforms, use <opsys>/usr.sbin/racoon, not
+ configure.in and Makefile.in.
+ - If you need to use configure.in and Makefile.in under
+ kame/kame/racoon, use the following options to configure.in:
+ % env LIBS=-L../../../bsdi4/lib/libpfkey ./configure \
+ --with-libpfkey
+ % make
+
+Q: How can I get help?
+
+A:
+ Always identify your operating system platforms, the versions you are
+ using (like "KAME SNAP, 2000/Sep/4"), and information to repeat the
+ problem. It is *mandatory* for you to submit the following at least:
+ - version identification
+ - trace from racoon, taken by "racoon -d 0xffffffff"
+ (maximum debug level)
+ - configuration file you are using
+ - probabaly, tcpdump trace
+ http://orange.kame.net/dev/send-pr.html has the guideline.
+
+ If you do not identify your version, we will not help you.
+
+ If your question is not confidential, send your questions to:
+ - as KAME problem report from http://orange.kame.net/dev/send-pr.html
+ - snap-users@kame.net
+ users mailing list, subscription guildeline: seewww.kame.net.
+ - NOT TO THE INDIVIDUAL DEVELOPERS.
+
+ If your question is confidential, send your questions to:
+ - core@kame.net
View
20 kame/kame/racoon/doc/README.build
@@ -1,20 +0,0 @@
-How to use configure.in with KAME/non-kame platforms
-$KAME: README.build,v 1.1 2000/09/13 05:35:08 itojun Exp $
-
-
-On the following platforms (and maybe others), libipsec.a does not provide
-pfkey_xx functions.
- NetBSD 1.5/current, FreeBSD 4.1/current
- kame/bsdi4, kame/netbsd, kame/freebsd2
-This is because pfkey_xx API is subject to change, and current function signature does not provide enough
-boundary checks.
-
-To build racoon on these platforms, there are couple of ways:
-- on NetBSD/FreeBSD integrated platforms, use pkgsrc/ports. It is the easiest
- and recommended way.
-- on KAME-patched platforms, use <opsys>/usr.sbin/racoon, not configure.in and
- Makefile.in.
-- If you need to use configure.in and Makefile.in under kame/kame/racoon,
- use the following options to configure.in:
- % env LIBS=-L../../../bsdi4/lib/libpfkey ./configure --with-libpfkey
- % make
Please sign in to comment.
Something went wrong with that request. Please try again.