Permalink
Browse files

update the sections on ALTQ.

  • Loading branch information...
1 parent bda4983 commit e48be364ae83240673ce5bc2c1b8ac104e3466a7 kjc committed May 7, 2003
Showing with 16 additions and 19 deletions.
  1. +11 −10 IMPLEMENTATION
  2. +2 −2 USAGE
  3. +3 −7 openbsd/INSTALL
View
@@ -2,7 +2,7 @@
KAME Project
http://www.kame.net/
- $KAME: IMPLEMENTATION,v 1.332 2003/04/01 03:44:32 itojun Exp $
+ $KAME: IMPLEMENTATION,v 1.333 2003/05/07 11:27:31 kjc Exp $
NOTE: The document tries to describe behaviors/implementation choices
@@ -2119,21 +2119,22 @@ interoperate.
5. ALTQ
-KAME kit includes ALTQ 2.1 code, which supports FreeBSD2, FreeBSD3,
-NetBSD and OpenBSD. For BSD/OS, ALTQ does not work.
-ALTQ in KAME supports (or tries to support) IPv6.
+KAME kit includes ALTQ, which supports FreeBSD3, FreeBSD4, FreeBSD5
+NetBSD. OpenBSD has ALTQ merged into pf and its ALTQ code is not
+compatible with other platforms so that KAME's ALTQ is not used for
+OpenBSD. For BSD/OS, ALTQ does not work.
+ALTQ in KAME supports IPv6.
(actually, ALTQ is developed on KAME repository since ALTQ 2.1 - Jan 2000)
-ALTQ occupies single character device number. For FreeBSD, it is officially
-allocated. For OpenBSD and NetBSD, we use the number which is not
-currently allocated (will eventually get an official number).
-The character device is enabled for i386 architecture only. To enable and
-compile ALTQ-ready kernel for other archititectures, take the following steps:
+ALTQ occupies single character device number.
+The ALTQ character device is enabled for i386 architecture only. To enable
+and compile ALTQ-ready kernel for other archititectures, take the following
+steps:
- assume that your architecture is FOOBAA.
- modify sys/arch/FOOBAA/FOOBAA/conf.c (or somewhere that defines cdevsw),
to include a line for ALTQ. look at sys/arch/i386/i386/conf.c for
example. The major number must be same as i386 case.
-- copy kernel configuration file (like ALTQ.v6 or GENERIC.v6) from i386,
+- copy kernel configuration file (like GENERIC.KAME) from i386,
and modify accordingly.
- build a kernel.
- before building userland, change netbsd/{lib,usr.sbin,usr.bin}/Makefile
View
4 USAGE
@@ -1,6 +1,6 @@
USAGE
KAME Project
- $KAME: USAGE,v 1.34 2002/01/31 09:44:02 k-sugyou Exp $
+ $KAME: USAGE,v 1.35 2003/05/07 11:27:31 kjc Exp $
This is a introduction of how to use the commands provided in the KAME
kit. For more information, please refer to each man page to be
@@ -527,7 +527,7 @@ How to install and use ALTQ:
other platforms:
add "options ALTQ" to your kernel config file.
- add optional queueing disciplines to use.
+ add optional queueing disciplines (e.g., ALTQ_CBQ) to use.
- make altq devices
you need to create altq devices before using altq:
View
@@ -1,6 +1,6 @@
Installation procedure - OpenBSD
KAME project
-$Id: INSTALL,v 1.9 2000/11/30 18:48:23 itojun Exp $
+$Id: INSTALL,v 1.10 2003/05/07 11:27:32 kjc Exp $
You'll need to follow the steps below. They can be separated into two major
@@ -88,18 +88,14 @@ E-1. Most of configuration files are shipped with normal OS distribution,
/usr/local/v6/etc. You may want to copy /usr/local/v6/etc/foo.sample into
/usr/local/v6/etc/foo, and edit as necessary.
-E-2. If you wish to use ALTQ, you may need to invoke /dev/MAKEDEV.altq.
- # cd /dev
- # sh MAKEDEV.altq all
-
-E-3. Commands modified by KAME project are placed in /usr/local/v6/{bin,sbin}.
+E-2. Commands modified by KAME project are placed in /usr/local/v6/{bin,sbin}.
For daily use, you will need to add both of (or either of) them
into your command search path (consult manpage for your favorite
shell). Make sure to make them used before /usr/bin or /usr/sbin,
otherwise you end up using OS-supplied (hence not IPv6 nor IPsec capable)
commands.
-E-4. There are batch of documents installed into /usr/local/v6/man
+E-3. There are batch of documents installed into /usr/local/v6/man
and /usr/local/v6/share/doc. Please read them as necessary.
If you wish to develop your own programs, we suggest you to read through
supplied documents, RFCs, and other documents to learn how.

0 comments on commit e48be36

Please sign in to comment.