1 / 17

Wisconsin Broadcaster’s Association - Transferring Files Using the Internet

Wisconsin Broadcaster’s Association - Transferring Files Using the Internet. July 14, 1999. Agenda. How does the Internet connect computers? What file transfer options are available? How long should file transfers take?. The Internet. Trace Route - West Coast.

calais
Download Presentation

Wisconsin Broadcaster’s Association - Transferring Files Using the Internet

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. WisconsinBroadcaster’sAssociation -Transferring FilesUsing the Internet July 14, 1999

  2. Agenda • How does the Internet connect computers? • What file transfer options are available? • How long should file transfers take?

  3. The Internet

  4. Trace Route - West Coast • glacier> traceroute www.cisco.com • traceroute to cio-sys.cisco.com (192.31.7.130), 30 hops max, 40 byte packets • 1 hood.binc.net (208.155.53.129) 1.171 ms 0.668 ms 0.502 ms • 2 borderx1-hssi4-0.KansasCity.cw.net (204.70.197.109) 39.826 ms 65.262 ms 29.2 ms • 3 core2-fddi-0.KansasCity.cw.net (204.70.197.49) 29.33 ms 29.084 ms 30.175 ms • 4 core5.WillowSprings.cw.net (204.70.4.97) 39.301 ms 38.627 ms 78.089 ms • 5 206.157.77.202 (206.157.77.202) 39.48 ms 53.901 ms 47.036 ms • 6 p2-0.chicago1-nbr1.bbnplanet.net (4.0.5.90) 65.324 ms 58.153 ms 64.021 ms • 7 p2-1.paloalto-nbr1.bbnplanet.net (4.0.3.166) 92.66 ms 87.199 ms 89.18 ms • 8 p1-0.paloalto-nbr2.bbnplanet.net (4.0.5.66) 98.269 ms 94.211 ms 96.705 ms • 9 p0-0-0.paloalto-cr18.bbnplanet.net (4.0.3.86) 93.012 ms 97.153 ms 97.247 ms • 10 h1-0.cisco.bbnplanet.net (4.1.142.238) 100.333 ms 95.248 ms 168.087 ms • 11 sty.cisco.com (192.31.7.39) 97.447 ms 138.212 ms 99.984 ms

  5. Trace Route - Local • glacier> traceroute www.fullfeed.com • traceroute to www.fullfeed.com (199.184.184.2), 30 hops max, 40 byte packets • 1 hood.binc.net (208.155.53.129) 0.923 ms 0.528 ms 0.489 ms • 2 borderx1-hssi4-0.KansasCity.cw.net (204.70.197.109) 73.395 ms 89.037 ms 122.573 ms • 3 core2-fddi-0.KansasCity.cw.net (204.70.197.49) 124.976 ms 35.189 ms 29.416 ms • 4 core9.Chicago.cw.net (204.70.9.105) 38.094 ms 86.538 ms 40.209 ms • 5 204.70.10.94 (204.70.10.94) 41.252 ms 38.312 ms 50.9 ms • 6 ord1-core3-fa4-1-0.atlas.digex.net (165.117.55.11) 38.578 ms 39.22 ms 38.875 ms • 7 dca1-core6-s1-1-0.atlas.digex.net (165.117.56.153) 60.079 ms 62.165 ms 65.447 ms • 8 dca1-core10-pos1-3.atlas.digex.net (165.117.59.197) 119.339 ms 66.016 ms 82.721 ms • 9 ric2-core1-s4-0-0.atlas.digex.net (165.117.50.70) 159.386 ms 69.805 ms 64.346 ms • 10 rdu2-core2-h1-0-0.atlas.digex.net (165.117.53.22) 140.809 ms 124.645 ms 138.938 ms • 11 rdu2-core1-fa10-0-0.atlas.digex.net (165.117.61.49) 164.267 ms 135.732 ms 135.187 ms • 12 * 209.48.179.126 (209.48.179.126) 194.346 ms 226.159 ms • 13 www.fullfeed.com (199.184.184.2) 213.423 ms 188.941 ms 201.149 ms

  6. Network Performance • 180,000 miles/s - It’s not just a good idea, it’s the law • 20 ms for a R/T from Madison to California • That doesn’t include other overhead

  7. Internet Connection • Physical proximity is not as important as “Internet” proximity • Each router or “hop” adds latency • Lot’s of places for things to go wrong - most out of your control • The bandwidth is shared

  8. File Transfer Options • E-Mail Attachments • FTP - File Transfer Protocol • TFTP - Trivial File Transfer • NFS - Network File System

  9. E-Mail Transfer

  10. E-Mail Transfer • Disks on mail servers can fill • Mail servers can go down • Connections can be slow/down • Mail is readily intercepted • Mail stops in many places • Simple and readily available

  11. FTP Transfer

  12. FTP Transfer • Disks can fill • Usually requires a dedicated FTP server • Less places for things to go wrong • More “production” orientated

  13. TFTP Transfer • Trivial File Transfer Protocol • Like FTP except lacking some features • Usually used for engineering purposes • Client and Server commonly available

  14. NFS Transfer • Network File System • Generally a Data Center application • Relatively slow • Requires specialized knowledge

  15. How Long - Ideal Conditions Assume 1 MB file (About a floppy) 28.8 kbs Modem 4.62 minutes 56 kbs Mode 2.38 minutes 126 kbs ISDN 1.05 minutes 800 kbs xDSL 10.2 seconds T1 5.18 seconds DS3 0.17 seconds

  16. Reality • Speed of disk access • Speed of network access • Congestion of network - dropped packets • Number of hops • Distance traveled

  17. Summary Today, nothing is guaranteed High-speed access is key Availability is important

More Related