NetBSD

History

itojun 6b56aad85e more careful about AF on ctlinput. (saw panic in the past with kame/netbsd141)		2000-02-26 16:10:31 +00:00
..
xebec	…
Makefile	…
README	…
argo_debug.h	…
clnl.h	…
clnp.h	…
clnp_debug.c	…
clnp_er.c	…
clnp_frag.c	…
clnp_input.c	allow delivery of routing protocol pdus to `raw' sockets even when the	2000-01-08 20:39:45 +00:00
clnp_options.c	…
clnp_output.c	…
clnp_raw.c	…
clnp_stat.h	…
clnp_subr.c	…
clnp_timer.c	…
cltp_usrreq.c	PRU_PURGEADDR -> PRU_PURGEIF, per a discussion w/ itojun. In the IPv4	2000-02-02 23:28:08 +00:00
cltp_var.h	…
cons.h	…
cons_pcb.h	…
eonvar.h	…
esis.c	more careful about AF on ctlinput. (saw panic in the past with kame/netbsd141)	2000-02-26 16:10:31 +00:00
esis.h	…
idrp_usrreq.c	…
idrp_var.h	…
if_cons.c	…
if_eon.c	make sure we do not pass bogus socket pointer to IPv4 IPsec.	1999-12-24 05:01:33 +00:00
iso.c	PRU_PURGEADDR -> PRU_PURGEIF, per a discussion w/ itojun. In the IPv4	2000-02-02 23:28:08 +00:00
iso.h	…
iso_chksum.c	CL* discarding.	1999-12-04 12:11:13 +00:00
iso_errno.h	…
iso_pcb.c	…
iso_pcb.h	…
iso_proto.c	add PR_LISTEN to protocols which support listen(2)	1999-07-01 05:53:04 +00:00
iso_snpac.c	add multicast address like everyone else, using if_ioctl	1999-06-30 03:32:40 +00:00
iso_snpac.h	…
iso_var.h	PRU_PURGEADDR -> PRU_PURGEIF, per a discussion w/ itojun. In the IPv4	2000-02-02 23:28:08 +00:00
tp.trans	…
tp_astring.c	…
tp_clnp.h	…
tp_cons.c	more careful about AF on ctlinput. (saw panic in the past with kame/netbsd141)	2000-02-26 16:10:31 +00:00
tp_driver.c	…
tp_emit.c	clear m_pkthdr for M_PKTHDR mbuf, so that we do not get panic with	2000-02-25 03:41:54 +00:00
tp_events.h	…
tp_inet.c	make sure we do not pass bogus socket pointer to IPv4 IPsec.	1999-12-24 05:01:33 +00:00
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