55 | | |
| 55 | [inki@Client1 ~]$ wget -m -p http://pc484.emulab.net |
| 56 | --2012-07-06 04:33:49-- http://pc484.emulab.net/ |
| 57 | Resolving pc484.emulab.net... 155.98.38.84 |
| 58 | Connecting to pc484.emulab.net|155.98.38.84|:80... connected. |
| 59 | HTTP request sent, awaiting response... 200 OK |
| 60 | Length: 548 [text/html] |
| 61 | Saving to: “pc484.emulab.net/index.html” |
| 62 | |
| 63 | 100%[======================================>] 548 --.-K/s in 0s |
| 64 | |
| 65 | 2012-07-06 04:33:49 (118 MB/s) - “pc484.emulab.net/index.html” saved [548/548] |
| 66 | |
| 67 | Loading robots.txt; please ignore errors. |
| 68 | --2012-07-06 04:33:49-- http://pc484.emulab.net/robots.txt |
| 69 | Connecting to pc484.emulab.net|155.98.38.84|:80... connected. |
| 70 | HTTP request sent, awaiting response... 404 Not Found |
| 71 | 2012-07-06 04:33:49 ERROR 404: Not Found. |
| 72 | |
| 73 | --2012-07-06 04:33:49-- http://pc484.emulab.net/top.html |
| 74 | Connecting to pc484.emulab.net|155.98.38.84|:80... connected. |
| 75 | HTTP request sent, awaiting response... 200 OK |
| 76 | Length: 917 [text/html] |
| 77 | Saving to: “pc484.emulab.net/top.html” |
| 78 | |
| 79 | 100%[======================================>] 917 --.-K/s in 0s |
| 80 | |
| 81 | 2012-07-06 04:33:49 (172 MB/s) - “pc484.emulab.net/top.html” saved [917/917] |
| 82 | |
| 83 | --2012-07-06 04:33:49-- http://pc484.emulab.net/home.html |
| 84 | Connecting to pc484.emulab.net|155.98.38.84|:80... connected. |
| 85 | HTTP request sent, awaiting response... 200 OK |
| 86 | Length: 822 [text/html] |
| 87 | Saving to: “pc484.emulab.net/home.html” |
| 88 | |
| 89 | 100%[======================================>] 822 --.-K/s in 0s |
| 90 | |
| 91 | 2012-07-06 04:33:49 (215 MB/s) - “pc484.emulab.net/home.html” saved [822/822] |
| 92 | |
| 93 | --2012-07-06 04:33:49-- http://pc484.emulab.net/links.html |
| 94 | Connecting to pc484.emulab.net|155.98.38.84|:80... connected. |
| 95 | HTTP request sent, awaiting response... 200 OK |
| 96 | Length: 958 [text/html] |
| 97 | Saving to: “pc484.emulab.net/links.html” |
| 98 | |
| 99 | 100%[======================================>] 958 --.-K/s in 0s |
| 100 | |
| 101 | 2012-07-06 04:33:49 (267 MB/s) - “pc484.emulab.net/links.html” saved [958/958] |
| 102 | |
| 103 | --2012-07-06 04:33:49-- http://pc484.emulab.net/media/GENILogo.png |
| 104 | Connecting to pc484.emulab.net|155.98.38.84|:80... connected. |
| 105 | HTTP request sent, awaiting response... 200 OK |
| 106 | Length: 22678 (22K) [image/png] |
| 107 | Saving to: “pc484.emulab.net/media/GENILogo.png” |
| 108 | |
| 109 | 100%[======================================>] 22,678 --.-K/s in 0.001s |
| 110 | |
| 111 | 2012-07-06 04:33:49 (42.8 MB/s) - “pc484.emulab.net/media/GENILogo.png” saved [22678/22678] |
| 112 | |
| 113 | --2012-07-06 04:33:49-- http://pc484.emulab.net/media/topgeni.png |
| 114 | Connecting to pc484.emulab.net|155.98.38.84|:80... connected. |
| 115 | HTTP request sent, awaiting response... 200 OK |
| 116 | Length: 116224 (114K) [image/png] |
| 117 | Saving to: “pc484.emulab.net/media/topgeni.png” |
| 118 | |
| 119 | 100%[======================================>] 116,224 --.-K/s in 0.002s |
| 120 | |
| 121 | 2012-07-06 04:33:49 (66.7 MB/s) - “pc484.emulab.net/media/topgeni.png” saved [116224/116224] |
| 122 | |
| 123 | --2012-07-06 04:33:49-- http://pc484.emulab.net/media/hello.png |
| 124 | Connecting to pc484.emulab.net|155.98.38.84|:80... connected. |
| 125 | HTTP request sent, awaiting response... 200 OK |
| 126 | Length: 11497 (11K) [image/png] |
| 127 | Saving to: “pc484.emulab.net/media/hello.png” |
| 128 | |
| 129 | 100%[======================================>] 11,497 --.-K/s in 0s |
| 130 | |
| 131 | 2012-07-06 04:33:49 (45.8 MB/s) - “pc484.emulab.net/media/hello.png” saved [11497/11497] |
| 132 | |
| 133 | --2012-07-06 04:33:49-- http://pc484.emulab.net/media/experimenter.png |
| 134 | Connecting to pc484.emulab.net|155.98.38.84|:80... connected. |
| 135 | HTTP request sent, awaiting response... 200 OK |
| 136 | Length: 14020 (14K) [image/png] |
| 137 | Saving to: “pc484.emulab.net/media/experimenter.png” |
| 138 | |
| 139 | 100%[======================================>] 14,020 --.-K/s in 0s |
| 140 | |
| 141 | 2012-07-06 04:33:49 (47.5 MB/s) - “pc484.emulab.net/media/experimenter.png” saved [14020/14020] |
| 142 | |
| 143 | --2012-07-06 04:33:49-- http://pc484.emulab.net/media/keyboard.png |
| 144 | Connecting to pc484.emulab.net|155.98.38.84|:80... connected. |
| 145 | HTTP request sent, awaiting response... 200 OK |
| 146 | Length: 9533 (9.3K) [image/png] |
| 147 | Saving to: “pc484.emulab.net/media/keyboard.png” |
| 148 | |
| 149 | 100%[======================================>] 9,533 --.-K/s in 0s |
| 150 | |
| 151 | 2012-07-06 04:33:49 (73.4 MB/s) - “pc484.emulab.net/media/keyboard.png” saved [9533/9533] |
| 152 | |
| 153 | FINISHED --2012-07-06 04:33:49-- |
| 154 | Downloaded: 9 files, 173K in 0.003s (59.7 MB/s) |
| 155 | [inki@Client1 ~]$ |
58 | | * On pc1, start a UDT file transfer server, using this command: |
59 | | {{{ |
60 | | % pc1:~% /local/udt4/app/sendfile |
61 | | server is ready at port: 9000 |
62 | | }}} |
63 | | |
64 | | * On pc2, start a UDT file transfer client, using this command: |
65 | | {{{ |
66 | | pc2:~% /local/udt4/app/recvfile pc1 9000 /local/datafiles/sm.10M /dev/null |
67 | | }}} |
68 | | You should see output like the following in your pc1 window, showing the results of the file transfer. Note the transfer rate. |
69 | | {{{ |
70 | | new connection: 192.168.2.2:55839 |
71 | | speed = 7.14472Mbits/sec |
72 | | }}} |
73 | | |
74 | | * There are three data files available for transfer tests: '''/local/datafiles/sm.10M''' is 10MB, '''/local/datafiles/med.100M''' is 100MB, and '''/local/datafiles/lg.1G''' is 1000MB. Leave your transfer server running on pc1, and try transferring each of these files in turn by typing the appropriate commands on pc2. Keep track of the transfer rates in each case. |
75 | | |
76 | | * You can leave your UDT server running or stop it with ctrl-C. |
77 | | |
78 | | === File Transfer Using FTP === |
79 | | |
80 | | Follow these steps to perform a file transfer using FTP. |
81 | | |
82 | | * For a TCP-based (FTP) transfer, there's already a FTP server running on pc1. Log into pc2, and start an ftp client: |
83 | | |
84 | | (You type ''ftp pc1'', the user name ''anonymous'', and any password you want, although your e-mail address is traditional.) |
85 | | |
86 | | {{{ |
87 | | pc2:~% ftp pc1 |
88 | | Connected to PC1-lan1. |
89 | | 220 (vsFTPd 2.3.2) |
90 | | Name (pc1:mberman): anonymous |
91 | | 331 Please specify the password. |
92 | | Password: |
93 | | 230 Login successful. |
94 | | Remote system type is UNIX. |
95 | | Using binary mode to transfer files. |
96 | | ftp> |
97 | | }}} |
98 | | |
99 | | * Still on pc2, request a file transfer. Note the reported file size, transfer time, and transfer rate. |
100 | | |
101 | | {{{ |
102 | | ftp> get med.100M /dev/null |
103 | | local: /dev/null remote: med.100M |
104 | | 200 PORT command successful. Consider using PASV. |
105 | | 150 Opening BINARY mode data connection for med.100M (104857600 bytes). |
106 | | 226 Transfer complete. |
107 | | 104857600 bytes received in 8.91 secs (11491.9 kB/s) |
108 | | }}} |
109 | | |
110 | | * You can perform additional transfers with additional get commands. When you're done, exit the ftp client with the quit command. |
| 158 | * Use the dataplane interface. Up to this point we have used the public interface of the webserver. As you are testing your environment, you should use the dataplane connections between the clients and the server. These are the private connections that are represented with a lines between the machines in Flack. To do that you first need to figure out the IP address of the server on each of these links. In the above example, the line that connects the Server with Client1 has a box that is called `lan0`. Press on the (i) button of that box and see the IP server that is assigned on the server. Use this IP to run the wget command : |
| 159 | {{{ |
| 160 | [inki@Client1 ~]$ wget -m -p http://10.10.1.1 |
| 161 | }}} |