vni(4d) 맨 페이지 - 윈디하나의 솔라나라

개요

섹션
맨 페이지 이름
검색(S)

vni(4d)

Device Drivers & /dev files                                            vni(4D)



NAME
       vni - STREAMS virtual network interface driver

DESCRIPTION
       The  vni pseudo device is a multi-threaded, loadable, clonable, STREAMS
       pseudo-device supporting the connectionless Data Link  Provider  Inter‐
       face dlpi(4P) Style 2.


       The  vni  device  is  a  software-only  interface  and does not send or
       receive data. The device provides a DLPI upper interface  that  identi‐
       fies  itself  to IP with a private media type. It can be configured via
       ipadm(8) and can have IP addresses assigned to it, making aliases  pos‐
       sible.


       The  vni  pseudo device is particularly useful in hosting an IP address
       when used in conjunction with the 'usesrc' ipadm option  (see  ipadm(8)
       for  examples). The logical instances of the device can also be used to
       host addresses as an alternative to  hosting  them  over  the  loopback
       interface.


       Multicast  is not supported on this device. More specifically, the fol‐
       lowing options return an error when used with an address  specified  on
       vni:  IP_MULTICAST_IF, IP_ADD_MEMBERSHIP, IP_DROP_MEMBERSHIP, IPV6_MUL‐
       TICAST_IF, IPV6_JOIN_GROUP, and IPV6_LEAVE_GROUP. In  addition,  broad‐
       cast is not supported.


       Because  there  is no physical hardware configured below it, no traffic
       can be received through nor transmitted on  a  virtual  interface.  All
       packet  transmission and reception is accomplished with existing physi‐
       cal interfaces and tunnels. Because applications that deal with  packet
       transmission and reception (such as packet filters) cannot filter traf‐
       fic on virtual interfaces, you cannot set up a packet filter on a  vir‐
       tual interface. Instead, you should configure the policy rules to apply
       to the physical interfaces and tunnels, and if necessary, use the  vir‐
       tual  IP  addresses themselves as part of the rule configuration. Also,
       note that the virtual interface cannot be part of  an  IP  multipathing
       (IPMP) group.

FILES
       /dev/vni    64-bit ELF kernel driver


SEE ALSO
       ip(4P), ip6(4P), in.mpathd(8), ipadm(8)



Oracle Solaris 11.4               14 Jun 2012                          vni(4D)
맨 페이지 내용의 저작권은 맨 페이지 작성자에게 있습니다.
RSS ATOM XHTML 5 CSS3