Lines Matching refs:ipd
16 * ipd: Internet packet disturber
18 * The purpose of ipd is to simulate congested and lossy networks when they
25 * 1. ipd's operations and restrictions
27 * ipd currently has facilities to cause IP traffic to be:
35 * Enabling ipd on a given zone causes pfhooks to be installed for that zone's
36 * netstack. Because of the nature of ipd, it currently only supports exclusive
38 * administrative access. ipd can be enabled for the global zone, but doing so
43 * ipd consists of a few components. There is a per netstack data structure that
46 * accessed for control of ipd via ioctls. The following diagram touches on the
47 * data structures that are used throughout ipd.
58 * | /dev/ipd | | pfhooks packet callback | == ipd_hook()
72 * ipd has two different entry points, one is administrative, the other is the
74 * ipdadm(1M). It communicates to the kernel component via ioctls to /dev/ipd.
80 * While the locking inside of ipd should be straightforward, unfortunately, the
82 * currently three different sets of locks in ipd.
179 #include <sys/ipd.h>
236 * ipd internal variables
380 ins->ipdn_v4in->h_name = "ipd IPv4 in";
395 ins->ipdn_v4out->h_name = "ipd IPv4 out";
410 ins->ipdn_v6in->h_name = "ipd IPv6 in";
425 ins->ipdn_v6out->h_name = "ipd IPv6 out";
907 ins->ipdn_kstat = net_kstat_create(id, "ipd", ins->ipdn_zoneid,
908 "ipd", "net", KSTAT_TYPE_NAMED,
1044 if (ddi_create_minor_node(dip, "ipd", S_IFCHR, instance,
1065 ipd_neti->nin_name = "ipd";