-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathINSTRUCTIONS
93 lines (76 loc) · 3.79 KB
/
INSTRUCTIONS
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
91
92
93
This document describes the environment for the Mininet sr assignment. You will
login to a virtual topology like this one:
Application Server 1
+====================+
| |
| 192.168.2.2 |
| |
+====================+
/
/
/
eth3: /
10.0.1.1 / eth1: 192.168.2.1
+============(eth1)==+
| |
Internet =============(eth3) Your Router |
| |
+============(eth2)==+
\ eth2: 172.64.3.1
\
\
\
+====================+
| |
| 172.64.3.10 |
| |
+====================+
Application Server 2
To connect to a topology, first compile the stub code.
Then, you can invoke sr as follows:
$ ./sr
By default, ./sr will connect to the mininet controller on localhost.
If you would like to run "sr" remotely, invoke sr as follows:
$ ./sr -s <controller_ip>
Your output upon connecting should look like this:
Using VNS sr stub code revised 2009-10-14 (rev 0.20)
Loading filters
---------------------------------------------
no filters specified. accepting all connections.
---------------------------------------------
Client ubuntu connecting to Server localhost:8888
Requesting topology 0
successfully authenticated as ubuntu
Connected to new instantiation of topology 0
Loading routing table
---------------------------------------------
Destination Gateway Mask Iface
192.168.2.2 192.168.2.2 255.255.255.255 eth1
172.64.3.10 172.64.3.10 255.255.255.255 eth2
10.0.1.100 10.0.1.100 255.255.255.255 eth3
---------------------------------------------
Router interfaces:
eth3 HWaddrc2:e3:78:bf:71:f9
inet addr 10.0.1.1
eth2 HWaddr26:e4:1f:26:49:ab
inet addr 172.64.3.1
eth1 HWaddr56:01:ec:fb:34:09
inet addr 192.168.2.1
<-- Ready to process packets -->
IMPORTANT: The system has more users than IP addresses, so you are not assigned
a particular set of static IP addresses. This means each time you connect you
MAY receive a different set of IP addresses. However, the system remembers the
last IP block assigned to you and will always re-assign it to you unless someone
else is currently using it (in which case you will get a new set of IP
addresses). Your routing table (stored in rtable.vrhost) will be automatically
updated by the stub code.
Please verify that you can see packets arriving to your topology when you try
and ping one of your router interfaces. To do this, connect to your topology as
described above and try and ping eth0 (e.g., 171.67.238.32 in this example).
$ ping 171.64.3.10
You should see output from sr that looks like:
*** -> Received packet of length 42
*** -> Received packet of length 42
*** -> Received packet of length 42
If so, everything is working! If not, please post your question on piazza.
Good Luck!