VND(7D) Devices VND(7D)


vnd - virtual layer two network driver





The vnd driver provides support for a layer two datapath in an analogous
way that IP(7P) provides a support for an IP-based layer three datapath.
Both devices operate exclusively on datalinks. A datalink that has been
plumbed up with IP via ifconfig(1M) or ipadm(1M) cannot be used with vnd
or vice-versa.

The vnd driver supports and takes advantage of the the following illumos

Supports dld/dls feature negotation of GLDv3 features, such as
direct calls, flow control, checksum offloading, and more.

All IP and IPv6 based traffic is sent through ipfilter(5),
allowing packet filtering.

Better control over vectored reads and writes in a frame-centric
manner through framed I/O. See libvnd(3LIB) for more information
on these interfaces.

The vnd driver exposes two different kinds of device nodes. The first is
a self-cloning control node which can be used to create vnd devices on
top of datalinks. Those devices can optionally be bound into the file
system namespace under /dev/vnd. Control operations on the control node
or named devices are private to the implementation. Instead, libvnd(3LIB)
provides a stable interfaces for using, creating, and manipulating vnd


vnd self-cloning control node

Character device that corresponds to the vnd device of
the given name (%link). A given device will appear for
each actively linked device in the current zone.

These are character devices that correspond to the vnd
device of the given name (%link). They are organized
based on the zone that they appear in. Thus if a zone
named foo has a vnd device named bar, then the global
zone will have the file /dev/vnd/zone/foo/bar. Note,
these only occur in the global zone.


See attributes(5) for descriptions of the following attributes:

|Interface Stability | Evolving |


dladm(1M), ipflter(5), libvnd(3LIB), vndadm(1M), vndstat(1)

February 11, 2014 VND(7D)