-
Notifications
You must be signed in to change notification settings - Fork 22
/
RELNOTES
51 lines (43 loc) · 2.09 KB
/
RELNOTES
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
RELNOTES of KAME kit
KAME Project
$Date: 1999/12/12 00:53:34 $
For list of changes from past KAME kit, please refer to CHANGELOG.
KNOWN BUGS/TWISTS
=================
All the following problems will be fixed in near-future SNAP releases,
and the next STABLE release,
- "faithd" sometimes fail to relay rsh/rlogin connection properly. Some part
of data connection seems to be lost. rlogin session may fail to propagate
screen size information to the peer.
- Some of the userland tool may not work properly, if you configure more than
500 interfaces. (libinet6 is fixed for this, but there are some places
where max # of interfaces is hardcoded)
- Notebooks/laptops problem: multicast hardware filter on ethernet card will
not be properly initialized after suspend/resume session, and this makes
trouble with IPv6 commuincation (which heavily uses multicast).
This is not a KAME problem (*BSD problem), but please be warned.
Workaround: perform "ifconfig down", then "ifconfig up" after resume.
- racoon daemon may not work correctly due to code synchronization problem
between userland and the kernel. Because of STABLE cut-off date we do not
supply fixes for this. If you would like to use racoon, please use more
recent SNAP kit instead.
- Intel EtherExpress Pro (fxp driver) has some problem with the
initialization sequence KAME is using (a set of ioctl calls). The driver
will become unusable if consequtive calls to fxp_init() are made, or
consequtive multicast configurations are made.
This problem occurs only with specific revision of the card.
It is not KAME problem, it is problem in fxp driver.
PLATFORM DIFFERENCES
====================
As we support various platforms, there are several differences between
those platforms. Here is a brief list of important differences:
- ALTQ
ALTQ 2.0 is merged into: KAME/FreeBSD228, KAME/FreeBSD33,
KAME/NetBSD141
No ALTQ support in: KAME/BSDI31, KAME/OpenBSD26
- IPsec
No KAME IPsec support in: KAME/OpenBSD26
(you can enjoy OpenBSD IPsec for IPv4)
- TCP
see IMPLEMENTATION for details.
<end of RELNOTES>