svcadm(8)을 검색하려면 섹션에서 8 을 선택하고, 맨 페이지 이름에 svcadm을 입력하고 검색을 누른다.
ng_iface(4)
An node is both a netgraph node and a system networking inter‐
face. When an node is created, a new interface appears which is
accessible via node interfaces are named etc. When a node is
shutdown, the corresponding interface is removed and the inter‐
face name becomes available for reuse by future nodes; new nodes
always take the first unused interface. The node itself is as‐
signed the same name as its interface, unless the name already
exists, in which case the node remains unnamed. An node has a
single hook corresponding to each supported protocol. Packets
transmitted via the interface flow out the corresponding proto‐
col-specific hook. Similarly, packets received on a hook appear
on the interface as packets received into the corresponding pro‐
tocol stack. The currently supported protocols are IP, IPv6,
ATM, NATM, and NS. An node can be configured as a point-to-point
interface or a broadcast interface. The configuration can only
be changed when the interface is down. The default mode is
point-to-point. nodes support the Berkeley Packet Filter (BPF).
This node type supports the following hooks: Transmission and re‐
ception of IP packets. Transmission and reception of IPv6 pack‐
ets. Transmission and reception of ATM packets. Transmission
and reception of NATM packets. Transmission and reception of NS
packets. This node type supports the generic control messages,
plus the following: Returns the name of the associated interface
as a string. Normally this is the same as the name of the node.
Returns the global index of the associated interface as a 32 bit
integer. Set the interface to point-to-point mode. The inter‐
face must not currently be up. Set the interface to broadcast
mode. The interface must not currently be up. This node shuts
down upon receipt of a control message. The associated interface
is removed and becomes available for use by future nodes. Unlike
most other node types, an node does go away when all hooks have
been disconnected; rather, and explicit control message is re‐
quired. The interface supports ALTQ bandwidth management fea‐
ture. However, is a special case, since it is not a physical in‐
terface with limited bandwidth. One should not turn ALTQ on if
the latter corresponds to some tunneled connection, e.g. PPPoE or
PPTP. In this case, ALTQ should be configured on the interface
that is used to transmit the encapsulated packets. In case when
your graph ends up with some kind of serial line, either synchro‐
nous or modem, the is the right place to turn ALTQ on. The node
type was implemented in