bpqparms(8) [debian man page]

BPQPARMS(8)						   Linux System Managers Manual 					       BPQPARMS(8)

NAME

       bpqparms - Configure BPQ ethernet devices.

SYNOPSIS

       bpqparms device [-a ethaddr] [-d ethaddr] [-vV]

DESCRIPTION

       Bpqparms  allows  the  setting  of  the	BPQ  Ethernet  options for a particular device. Each BPQ Ethernet device appears as a device named
       bpq0...bpqN which overlays the original Ethernet device, usually eth0...ethN. This device is an AX.25 device driver and allows AX.25 frames
       to be transmitted over an Ethernet to another machine using the same protocol. The default for the device is to send and receive BPQ Ether-
       net packets to the broadcast address. This program replaces the previous "axparms -dev" option.

OPTIONS

       -a ethaddr     Allows the setting of which ethernet address will be accepted by the BPQ Ethernet device.

       -d ethaddr     If specified on its own, will set the destination ethernet address will be used for transmitting and for	receiving  of  BPQ
		      ethernet packets. An address of "broadcast" sets it to the ethernet broadcast address.

       -v	      Displays the version number.

       -V	      The original version messages.

SEE ALSO

       ax25(4), axports(5), ifconfig(8).

AUTHOR

       Joerg Reuter DL1BKE <jreuter@poboxes.com>

Linux								 4 September 1996						       BPQPARMS(8)

ETHERIP(4)						   BSD Kernel Interfaces Manual 						ETHERIP(4)

NAME

     etherip -- EtherIP tunneling device

SYNOPSIS

     pseudo-device etherip

DESCRIPTION

     The etherip interface is a tunneling pseudo device for Ethernet frames.  It can tunnel Ethernet traffic over IPv4 and IPv6 using the EtherIP
     protocol specified in RFC 3378.

     The only difference between an etherip interface and a real Ethernet interface is that there is an IP tunnel instead of a wire.  Therefore,
     to use etherip the administrator must first create the interface and then configure protocol and addresses used for the outer header.  This
     can be done by using ifconfig(8) create and tunnel subcommands, or SIOCIFCREATE and SIOCSLIFPHYADDR ioctls.

   Packet format
     Ethernet frames are prepended with a EtherIP header as described by RFC 3378.  The resulting EtherIP packets will be encapsulated in an outer
     packet, which may be either an IPv4 or IPv6 packet, with IP protocol number 97.

   Ethernet address
     When a etherip device is created, it is assigned an Ethernet address of the form f2:0b:a5:xx:xx:xx.  This address can later be changed
     through a sysctl node.

     The sysctl node is net.link.etherip.<iface>.  Any string of six colon-separated hexadecimal numbers will be accepted.  Reading that node will
     provide a string representation of the current Ethernet address.

   Security
     The EtherIP header of incoming packets is not checked for validity.  This is because there seems to be some confusion about how such a header
     has to look like.	For outgoing packets, the header is set up the same way as done in OpenBSD, FreeBSD, and Linux to be compatible with those
     systems.

   Converting from previous implementation
     A tunnel configured for the previous (undocumented) implementation will work with just renaming the device from gif to etherip.

SEE ALSO

     bridge(4), gif(4), inet(4), inet6(4), tap(4), ifconfig(8)

HISTORY

     The etherip device first appeared in NetBSD 4.0, it is based on tap(4), gif(4), and the former gif-based EtherIP implementation ported from
     OpenBSD.

BUGS

     Probably many.  There is lots of code duplication between etherip, tap(4), gif(4), and probably other tunnelling drivers which should be
     cleaned up.

BSD
								 November 23, 2006							       BSD