forked from Linjay/SCPS_Project
/
README.GATEWAY.LINUX.TAP
90 lines (57 loc) · 2.63 KB
/
README.GATEWAY.LINUX.TAP
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
README FILE FOR SCPS GATEWAY REFERENCE IMPLEMENTATION - NATIVE LINUX
support.
This particular port uses a combination of the tap interface and
bridging functionality.
The following steps are required before configuring the SCPS gateway to
work under linux.
===================================================================
Section 1 Obtaining and installing supporting software. Note the depending on
your version of linux, they may already be present on your system.
Need to install the tun/tap modules from http://vtun.sourceforge.net/tun
Need to install brctl from http://bridge.sourceforge.net
May need to install latest kernel from ftp://ftp.kernel.org - I am
using 2.4.10 with no problem.
Also Verify the following kernel configure/compiling options are enabled
UNDER NETWORKING OPTIONS
802.1d Ethernet Bridging
UNDER NETWORKING DEVICE
Universal TUN/TAP device dirver support.
===================================================================
Section 2 Building the SCPS Gateway
The next step is to configure the makefiles for the SCPS Gateway.
You must configure the makefiles for the SCPS application and the main
SCPS source directory. There are scripts to assist you in doing this.
cd ../apps
Enter the command
./configure
A message indicating that a make file is being created should be printed.
Now, cd to the "source" directory:
cd ../source
Enter the command
./configure --gateway=yes --tap=yes
expect to see a message indicating that the makefile is being created.
Finally, change to the top-level (SCPS) directory:
cd ..
And build the configuration by entering the following command:
make clean
make
===================================================================
Section 3 Modifing the rfile
The rfile required adding two additional directives to support
the tap interface. These directives are AIF_TAP_NAME and
BIF_TAP_NAME need to be set their corresponding tap interfaces.
For example
AIF_TAP_NAME tap0
BIF_TAP_NAME tap1
There are two additional directives that may be useful;
C_OTHER_PROTO_QLEN and C_OTHER_PROTO_XRATE_DROP. To implement
the briding functionality the gateway now processes all IP packets.
There is a queue for each protocol id for each direction. The
directive C_OTHER_PROTO_QLEN allows you to set this queue length.
Note that the default is 5. C_OTHER_PROTO_XRATE_DROP allows you
to set the drop dehavior when the gateway tried to emit the non
TCP packets and no rate exists. If C_OTHER_PROTO_XRATE_DROP is
set to 0 (the default) the packet will be dropped. If this
directive is set to 1, this packet will stay in the queue until
rate is available.
Well that's about it...