Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

vv(4) [bsd man page]

VV(4)							     Kernel Interfaces Manual							     VV(4)

NAME

       vv - Proteon proNET 10 Megabit ring

SYNOPSIS

       /sys/conf/SYSTEM:
	    NVV  vv_controllers # V2LNI (Pronet)

DESCRIPTION

       The vv interface provides access to a 10 Mb/s Proteon proNET ring network.

       The network address of the interface must be specified with an an SIOCSIFADDR ioctl before data can be transmitted or received.	It is only
       permissible to change the network address while the interface is marked "down".

       The host's hardware address is discovered by putting the interface in digital loopback mode (not joining the ring) and sending a  broadcast
       packet from which the hardware address is extracted.

       Transmit timeouts are detected through use of a watchdog routine.  Lost input interrupts are checked for when packets are sent out.

       If  the	installation  is  running  CTL	boards	which  use  the  old broadcast address of 0 instead of the new address of 0xff, the define
       OLD_BROADCAST should be specified in the driver.

       The driver can use ``trailer'' encapsulation to minimize copying data on input and output.  This may be disabled, on a per-interface basis,
       by setting the IFF_NOTRAILERS flag with an SIOCSIFFLAGS ioctl.

DIAGNOSTICS

       vv%d: host %d.  The software announces the host address discovered during autoconfiguration.

       vv%d: can't initialize. The software was unable to discover the address of this interface, so it deemed "dead" will not be enabled.

       vv%d: error vvocsr=%b.  The hardware indicated an error on the previous transmission.

       vv%d: output timeout.  The token timer has fired and the token will be recreated.

       vv%d: error vvicsr=%b.  The hardware indicated an error in reading a packet off the ring.

       en%d:  can't  handle  af%d.   The  interface  was handed a message with addresses formatted in an unsuitable address family; the packet was
       dropped.

       vv%d: vs_olen=%d.  The ring output routine has been handed a message with a preposterous length.   This	results  in  an  immediate  panic:
       vs_olen.

SEE ALSO

       intro(4N), inet(4F)

BUGS

       The  encapsulation  of  trailer	packets  in the 4.2BSD version of this driver was incorrect (the packet type was in VAX byte order).  As a
       result, the trailer encapsulation in this version is not compatible with the 4.2BSD VAX version.

3rd Berkeley Distribution					  August 20, 1987							     VV(4)

Check Out this Related Man Page

LO(4)                                                      BSD Kernel Interfaces Manual                                                      LO(4)

NAME

     lo -- software loopback network interface

SYNOPSIS

     device loop

DESCRIPTION

     The loop interface is a software loopback mechanism which may be used for performance analysis, software testing, and/or local communication.
     As with other network interfaces, the loopback interface must have network addresses assigned for each address family with which it is to be
     used.  These addresses may be set or changed with the SIOCSIFADDR ioctl(2).  The loopback interface should be the last interface configured,
     as protocols may use the order of configuration as an indication of priority.  The loopback should never be configured first unless no hard-
     ware interfaces exist.

     If the transmit checksum offload capability flag is enabled on a loopback interface, checksums will not be generated by IP, UDP, or TCP for
     packets sent on the interface.

     If the receive checksum offload capability flag is enabled on a loopback interface, checksums will not be validated by IP, UDP, or TCP for
     packets received on the interface.

     By default, both receive and transmit checksum flags will be enabled, in order to avoid the overhead of checksumming for local communication
     where data corruption is unlikely.  If transmit checksum generation is disabled, then validation should also be disabled in order to avoid
     packets being dropped due to invalid checksums.

DIAGNOSTICS

     lo%d: can't handle af%d.  The interface was handed a message with addresses formatted in an unsuitable address family; the packet was
     dropped.

SEE ALSO

     inet(4), intro(4)

HISTORY

     The lo device appeared in 4.2BSD.  The current checksum generation and validation avoidance policy appeared in FreeBSD 8.0.

BSD                                                               March 15, 2009                                                               BSD
Man Page