118d2b1d4f
(Sorry for a big commit, I can't separate this into several pieces...)
Pls check sys/netinet6/TODO and sys/netinet6/IMPLEMENTATION for details.
- sys/kern: do not assume single mbuf, accept chained mbuf on passing
data from userland to kernel (or other way round).
- "midway" ATM card: ATM PVC pseudo device support, like those done in ALTQ
package (ftp://ftp.csl.sony.co.jp/pub/kjc/).
- sys/netinet/tcp*: IPv4/v6 dual stack tcp support.
- sys/netinet/{ip6,icmp6}.h, sys/net/pfkeyv2.h: IETF document assumes those
file to be there so we patch it up.
- sys/netinet: IPsec additions are here and there.
- sys/netinet6/*: most of IPv6 code sits here.
- sys/netkey: IPsec key management code
- dev/pci/pcidevs: regen
In my understanding no code here is subject to export control so it
should be safe.
|
||
|---|---|---|
| .. | ||
| xebec | ||
| Makefile | ||
| README | ||
| argo_debug.h | ||
| clnl.h | ||
| clnp.h | ||
| clnp_debug.c | ||
| clnp_er.c | ||
| clnp_frag.c | ||
| clnp_input.c | ||
| clnp_options.c | ||
| clnp_output.c | ||
| clnp_raw.c | ||
| clnp_stat.h | ||
| clnp_subr.c | ||
| clnp_timer.c | ||
| cltp_usrreq.c | ||
| cltp_var.h | ||
| cons.h | ||
| cons_pcb.h | ||
| eonvar.h | ||
| esis.c | ||
| esis.h | ||
| idrp_usrreq.c | ||
| idrp_var.h | ||
| if_cons.c | ||
| if_eon.c | ||
| iso.c | ||
| iso.h | ||
| iso_chksum.c | ||
| iso_errno.h | ||
| iso_pcb.c | ||
| iso_pcb.h | ||
| iso_proto.c | ||
| iso_snpac.c | ||
| iso_snpac.h | ||
| iso_var.h | ||
| tp.trans | ||
| tp_astring.c | ||
| tp_clnp.h | ||
| tp_cons.c | ||
| tp_driver.c | ||
| tp_emit.c | ||
| tp_events.h | ||
| tp_inet.c | ||
| tp_input.c | ||
| tp_ip.h | ||
| tp_iso.c | ||
| tp_meas.c | ||
| tp_meas.h | ||
| tp_output.c | ||
| tp_param.h | ||
| tp_pcb.c | ||
| tp_pcb.h | ||
| tp_seq.h | ||
| tp_stat.h | ||
| tp_states.h | ||
| tp_states.init | ||
| tp_subr.c | ||
| tp_subr2.c | ||
| tp_timer.c | ||
| tp_timer.h | ||
| tp_tpdu.h | ||
| tp_trace.c | ||
| tp_trace.h | ||
| tp_user.h | ||
| tp_usrreq.c | ||
| tp_var.h | ||
README
In case you were wondering why this code is still present: The ISO (or OSI) stack is still in use by many router vendors (e.g., using IS-IS the OSI equivelent of OSPF, to carry IP routes). Chris. chopps@netbsd.org