atmarp(8) [debian man page]

ATMARP(8)						       Maintenance Commands							 ATMARP(8)

NAME

       atmarp - administer classical IP over ATM connections

SYNOPSIS

       atmarp -a
       atmarp -c [[atm]number]
       atmarp -q ip_addr [qos qos] [sndbuf bytes]
       atmarp -s ip_addr [itf.]vpi.vci [qos qos] [sndbuf bytes] [temp] [pub] [null]
       atmarp -s ip_addr atm_addr [qos qos] [sndbuf bytes] [temp] [pub] [arpsrv]
       atmarp -d ip_addr [arpsrv]
       atmarp -V

DESCRIPTION

       atmarp is used to maintain the ATMARP table of the ATMARP demon.  The table can be listed, new PVC and SVC entries can be added, and exist-
       ing entries can be deleted. In addition to that, atmarp is also used to create new IP over ATM interfaces.

       Note that the kernel has its own ATMARP table containing only entries for destinations to which a connection exists. The table  of  atmarpd
       can also contain currently unused entries.

OPTIONS

       -a     list the current ATMARP table.

       -c     create  the specified IP interface. If the interface number is omitted, the operating system assigns the next free number and atmarp
	      prints the resulting interface name (e.g. `atm0') on standard output.

       -q     sets the QOS and the send buffer size to use as the default for all VCs generated for that IP network (ip_addr must be  the  address
	      of the network).

       -s     set up a PVC or create an SVC entry. The following options are recognized:

	      qos qos
		     uses the specified quality of service (see qos(7) for the syntax). UBR at link speed is used by default.

	      sndbuf bytes
		     tries to set the send buffer to the specified number of bytes. A system default value is used if sndbuf is not specified.

	      temp   does not mark the entry as permanent, i.e. it will time out and then be removed.

	      pub    publishes	the  entry  (only  relevant  for  ATMARP  server).  ATMARP requests for entries not marked for publishing yield an
		     ATMARP_NAK response.

	      null   uses NULL encapsulation instead of LLC/SNAP encapsulation on the PVC. This option is not  available  for  SVCs,  because  the
		     LLC/SNAP header is required to identify ATMARP packets. null also implies that the entry is permanent.

	      arpsrv identifies the entry pointing to the ATMARP server. Note that the node acting as the ATMARP server must have no ATMARP server
		     entry in its ATMARP table.

       -d     delete the specified ARP entry.  In order to prevent accidental deletion of the ATMARP server entry, the arpsrv flag must be  speci-
	      fied when deleting it.

       -V     print the version number of atmarp on standard output and exit.

FILES

       /var/run/atmarpd.table	ATMARP table
AUTHOR

       Werner Almesberger, EPFL ICA <Werner.Almesberger@epfl.ch>
SEE ALSO

       atmarpd(8), clip(8), qos(7)

Linux								  April 26, 2000							 ATMARP(8)

Check Out this Related Man Page

br2684ctl(8)						      System Manager's Manual						      br2684ctl(8)

NAME

       br2684ctl - RFC1483/2684 Bridge Daemon

SYNOPSIS

       br2684ctl [ -b ] [[ -c n ] [ -e 0|1 ] [ -p 0|1 ] [ -s sndbuf ] [ -a [itf].vpi.vci ]] ...

PARAMETERS

       -a [itf].vpi.vci
		      ATM PVC number, VPI and VCI.  (Required)

       -b	      Puts the process in the background.

       -c n	      br2684 interface number such as 0, 1, ... (Required)

       -e 0|1	      Encapsulation method:  0=LLC, 1=VC mux (the default is 0 or LLC)

       -p 0|1	      Payload method:  0=Routed, 1=Bridged (the default is 1 or Bridged)

       -s sndbuf      Send buffer size. Default is 8192.

DESCRIPTION

       br2684ctl  handles RFC1483/2684 bridged PDUs.  This is most often used in ADSL scenarios where usually the subscribers' ethernet traffic is
       encapsulated in ATM AAL5 (by bridging ADSL modems) according to RFC2684.  The subscriber-side ADSL modem can be external with  an  ethernet
       connector or an internal ADSL card in a PC.  RFC1483 has been obsoleted by RFC2684.

       For  example  it is possible to set up your Linux box to handle several ATM PVC's with bridged-1483 (sometimes referred as SNAP) encapsula-
       tion.  The Linux network stack might provide DHCP, IP masquerading, IP firewall services or bridge the Ethernet frames  just  like  it  had
       several ethernet interfaces.  In fact it can have several (logical) ethernet interfaces, where ATM is just used as a carrier.

USAGE

       br2684ctl creates a new network interface named nas[n] which is bound to an specific ATM PVC. It requires two mandatory arguments:  -c, the
       interface number, and -a, the ATM PVC. It should be noted that the order of the command arguments matter; -c should be followed by -a.  You
       can create as many interfaces as necessary in one go, just make a long command line ;)

       For  example,  following  command will create a nas0 interface which uses the ATM PVC with VPI=0 and VCI=401. You need to configure the PVC
       connection 0.401 on the ATM switch manually.

       % br2684ctl -c 0 -a 0.401

       The command will only create a new interface nas0.  Next step is to assign an IP address and netmask to the interface nas0 using the ifcon-
       fig command. Using ifconfig, you can also assign a Ethernet MAC address to the interface nas0, if necessary.

       % ifconfig nas0 192.168.2.1 netmask 255.255.255.0

       Messages are logged to the LOCAL2 syslog facility.

FILES

       /var/run/br2684ctl-<iface>.pid

NOTES

       This man page is based on a tutorial by by Joonbum Byun <jbyun@megaxess.com>

SEE ALSO

       qos(7)

								    7 Jul 2003							      br2684ctl(8)

Linux and UNIX Man Pages

atmarp(8) [debian man page]

Check Out this Related Man Page