Debian Codegraph @

src/lane/USAGE

raw
1 /*
2 * Marko Kiiskila [email protected]
3 *
4 * Tampere University of Technology - Telecommunications Laboratory
5 *
6 */
7
8 LANE Service Package
9 ====================
10 Lan Emulation Configuration Server, Lan Emulation Server and
11 Broadcast and Unknown Server. Description
12 of LAN-E can be found from ATM Forum's specification "LAN Emulation
13 Over ATM - Version 1.0".
14 ftp://ftp.atmforum.com/pub/specs/af-lane-0021.000.ps.Z
15
16 Usage:
17 ======
18 Compile the package. This produces three executables lecs, les and bus.
19 LES and BUS noth use same configuration file '.lanevars'. Fill in the
20 required fields in that file and start the servers.
21 Configuration file for LECS is .lecs_conf
22
23 Configuration file (.lanevars):
24 ===============================
25 Has following variables for controlling VLAN and server operation:
26
27 S1=Address of the LES. This address is used in ATM signalling.
28 S2=Type of the emulated LAN. Valid values are "802.3" and "802.5".
29 S3=Maximum frame size. Valid values are 1516, 4544, 9234 and 18190
30 S4=Join Timeout. Time in seconds which LES waits for LE_JOIN_REQUEST
31 before tearing down a connection.
32 S5=Maximum frame Age. Currently not used.
33 S6=Address of the BUS. This address is used in ATM signalling.
34 ELANNAME= Name of the emulated LAN
35
36 Most important variables are S1 and S6. When one is running LE service
37 and LE client in same machine, care must be taken in choosing different
38 ATM addresses for these entities. This is needed because SAPs for these
39 entities must be different, and ATM address is the only way for this.
40 Currently these variables must be given in format shown in example
41 configuration file included in package, i.e.:
42
43 S6=:47:00:23:00:00:00:03:03:00:01:00:02:01:00:20:ea:00:0a:e9:02 #viulu
44
45 Configuration file (.lecs_conf):
46 ================================
47 Includes definitions for LECS's ATM address and ELAN definitions for
48 which LECS knows about. Look for example configuration file
49 .lecs_conf for description of variables and syntax of these.
50
51 Example scenario:
52 =================
53
54 -------- -------- --------
55 | | | | | |
56 | Box1 |-------------|Switch|-------------| Box2 |
57 | | | | | |
58 -------- -------- --------
59
60 Box1 has ATM addresses A1, A2 and A3. Box2 has ATM address B1 and B2.
61 A1 = LEC address in Box1
62 A2 = LES address
63 A3 = BUS address
64 B1 = LECS address
65 B2 = LEC address in Box2
66
67 Start ATM signalling in both boxes. Switch is configures with IISP
68 routes, because ilmid can only register one ATM address.
69
70 Another way is to modify signalling daemon's code.
71 -----8<------
72 if (walk->state == ls_same && atm_equal(&walk->addr,
73 &msg->svc,0,0)) break;
74
75 to
76
77 if (walk->state == ls_same && atm_equal(&walk->addr,
78 &msg->svc,(ATM_ESA_LEN-1)*8,AXE_WILDCARD)) break;
79
80 (atm/sigd/kernel.c, near line 156)
81 -----8<------
82
83 After this it is possible to run ilmid if A1, A2 and A3 differ only in
84 selector byte of their ATM addresses. In this case IISP routes are
85 not needed.
86
87 .lanevars contains:
88 [conn]
89 S1=A2
90 S6=A3
91
92
93 .lecs_conf contains:
94 #LECS address
95 B1
96
97 #ELAN definition
98 []
99 DEFAULT
100
101
102 Start lecs, les and bus.
103
104 Run LEC in Box1:
105 zeppelin -c B1 -l A1
106
107 Run LEC in Box2:
108 zeppelin -c B1 -l B2
109