1zeppelin(8)                  Maintenance Commands                  zeppelin(8)
2
3
4

NAME

6       zeppelin - ATM LAN Emulation client demon (LED) Zeppelin
7

SYNOPSIS

9       zeppelin      [-b ]     [-c LECS_address | -s LES_address]     [-e esi]
10       [-n VLAN_name] [-m mesg_mask] [-l listen_address | selector] [-i inter‐
11       face_number]                             [-I physical_interface_number]
12       [-t 1516|1580|4544|9234|18190]   [-1 ]   [-2 ]    [-p ]    [-F logfile]
13       [-f Fore_specific_name]
14

DESCRIPTION

16       A  LAN Emulation Client is an entity in an ATM endstation that performs
17       data forwarding, address resolution and  other  control  functions.  It
18       uses  the  LUNI  interface  when communicating with other components in
19       emulated LANs. It provides upper protocol layers a MAC  like  interface
20       similar to IEEE 802.3/Ethernet or IEEE 802.5/Token Ring LAN.
21
22       LAN  Emulation client code is divided into two parts: user space appli‐
23       cation LAN Emulation Demon called (LED)  zeppelin(8),  and  the  kernel
24       component. Zeppelin is responsible for control operations needed in LAN
25       Emulation clienthood. It forms the necessary VCCs and receives all  the
26       LE  control frames and acts accordingly. It also controls the operation
27       of the LEC kernel component.
28
29       Linux LEC supports only Ethernet type of emulated LAN.
30
31       SIGHUP causes restart of the LEC. All resources are released  and  zep‐
32       pelin is started.
33

OPTIONS

35       -b     Run  in  background  (i.e. in a forked child process) after ini‐
36              tializing kernel interface.
37
38       -c LECS_address
39              ATM address of lecs(8) (Lan Emulation Configuration Server),  if
40              not set, Well-Known server address is used.
41
42       -s LES_address
43              ATM  address  of  les(8)  (Lan Emulation Server), can be used in
44              bypassing configuration phase in joining emulated Lan  i.e  lecs
45              address is not used.
46
47       -e esi Mac  address  to  use  when  communicating in Emulated LAN. E.g.
48              00:20:22:23:04:05 .
49
50       -n VLAN_name
51              Name of the virtual LAN to which joining is requested.  This  is
52              used in LE_CONFIGURE_REQUEST to LECS or LE_JOIN_RESPONSE to LES,
53              if configuration phase is bypassed.
54
55       -m mesg_mask
56              Sometimes one wants to know more what is happening in LE  daemon
57              e.g.  when  nothing works. This is a hexadecimal long value set‐
58              ting global message mask. 0 = No messages, ffff = All messages.
59
60       -l listen_address | selector
61              Local ATM address that zeppelin uses as local binding  point  in
62              signalling.  Use this if you are running more than one client or
63              a set of LE servers. The local ATM address can be  specified  by
64              either giving the full ATM address or the desired selector byte.
65
66       -i interface_number
67              Linux  LEC  supports  up  to 40+8 network interfaces. The inter‐
68              face_number tells zeppelin to which of these to attach. Ethernet
69              type  network interfaces are numbered from "lec0" to "lec39" and
70              Token Ring interfaces are from "lec40" to "lec47". These parame‐
71              ters  are  tweakable  during the kernel compile, see <linux/atm‐
72              lec.h>.
73
74       -I physical_interface_number
75              The physical interface this LANE client should bind to. If  your
76              host  has multiple ATM network cards, you can use this option to
77              choose which card this zeppelin will use.
78
79       -t MTU The MTU of ELAN to join. You need to also use ifconfig(8) to set
80              the MTU of the LANE interface.
81
82       -1     Run as LANEv1 client. This is the default.
83
84       -2     Run as LANEv2 client. This is required by MPOA.
85
86       -p     Enable  proxy.  When started with this option, it is possible to
87              bridge packets between ATM and Ethernet. That is,  you  can  use
88              LANE  interfaces  with  normal  bridging. See the Bridging mini-
89              Howto for more info.
90
91       -F logfile
92              Instead of writing debug messages to stderr, write the  messages
93              to the file logfile. Use syslog as the file name to use the sys‐
94              log(3) facility.
95
96       -f Fore specific name
97              The LANE servers on Fore ATM switches can display a special name
98              if  a  client can supply one. This name shows with command ´conf
99              lane les show advanced´.
100

TOKEN RING CONSIDERATIONS

102       A number of lec interfaces is reserved for Token Ring  ELANs  when  the
103       kernel is compiled with Token Ring (CONFIG_TR) support. See the discus‐
104       sion about interface_number command line option above. The Linux  Token
105       Ring  LANE  client  does not support bridging between legacy Token Ring
106       and ATM parts of the ELAN, so using the -p option is  not  recommended.
107       Token Ring support has received less testing than its Ethernet counter‐
108       part.
109

FILES

111       /var/run/lec[interface
112              The file containing the process id of zeppelin.
113

BUGS

115       John Bonham died 1980 and Led Zeppelin broke.
116
117       Please report any other bugs to Heikki Vatiainen <hessu@cs.tut.fi>
118

AUTHORS

120       Marko  Kiiskila,  TUT  <carnil@cs.tut.fi>  and  Heikki  Vatiainen,  TUT
121       <hessu@cs.tut.fi>
122

SEE ALSO

124       lecs(8), mpcd(8), atmsigd(8), les(8), qos(7)
125
126
127
128Linux                            Nov 29, 1999                      zeppelin(8)
Impressum