Data tapes sent by courier are one example of a high bandwidth and high latency method of transporting data.
A LAN has low bandwidth and low latency.
High bandwidth is desired when there is a large amount of data to transport when the time to deliver the data is not a concern.
Interactive or real-time operations would be best with low latency as quick deliver and/or response is required.
When the commercials are comparing DSL/cable to either each other or to dial-up, they are referring to bandwidth. When the commercials are comparing two dial-up companies, they are referring to compression.
Connection-oriented communication sets up a channel, eg a SYN handshake with TCP, sends the data for the communication and tears down the channel. An example would be a telephone call. Connectionless communication just sends the data with full addressing information and no communication channel is established. An example would be sending letters through the mail system.
Data Link Layer
Network Layer
Same:Different:
- Both have a stack of protocols
- The functionality of the layers are similar
- The layers are divided into application oriented (end-to-end) and transport oriented (chained) protocols with the application protocols above the transport ones.
- There is a different number of layers in each.
- OSI makes a clear distinction between service, interface and protocol whereas TCP/IP does not.
- OSI protocols are better hidden, more like a black box
- OSI had the model first and then the protocols. The opposite was true with TCP/IP.
- OSI gave no consideration to internetworking
- OSI offers only connection-oriented communication to users. TCP/IP offers both connection-oriented and connectionless.
Wireless networks also transmit one frame at a time, but determining when one can send is more difficult. Ethernet is a broadcast bus so the sender can just listen to see if there is any traffic before sending. Due to range issues with wireless, a sender cannot be sure that there are not other transmissions just because it cannot "hear" other transmissions. Wireless senders use either a central base station or use methods discussed in Chapter 4 to avoid collisions.
First get S/N from 20db.20dB = 10 log10(S/N) S/N = 100Now plug values into Shannon's Lawmax rate = 3000 log2(1 + 100) = 3000 log2(101) = 3000 * 6.66 = 19974.63 bits/secIf you didn't convert dB, you would get 13176.95 bits/sec
1540000 = 50000 log2(S/N + 1) 30.8 = log2 (S/N + 1) S/N + 1 = 1869493099 S/N = 1869493098Convert to dB10 log10 (1869493098) 92.7 dB
Option (a) looks up the IP address for a given domain name and returns the IP address in the answer section. It also returns the listed nameservers for the domain in the authority section and information about the nameservers in the additional section. The answer section may contain multiple lines if the domain name is an alias for another domain name (CNAME type).Option (b) returns the start of authority information for the domain name. In particular, the authority section will give details about the DNS record for that domain name. The answer section will list any alias names, but will not look up the IP address. If the domain name has no aliases, the answer section will be omitted.
Option (a) will find the start of authority record. It specifies the address in the proper notation for dig as you cannot use the IP address directly by default. Option (b) is close, but is missing the -x option to dig that is required to use just the IP address or portions of the IP address. If you added -x before the IP address, the output would be identical to option (a). Option (c) is wrong because ping only checks round trip times, not start of authority.
This indicates that there is some issue with looking up the domain name ftp.foo.com. First, do a dig on the domain name to see if an IP address is listed in the answer section. If there is no IP address for that domain name, you should at least get a dig response with an authority section for the root domain (foo.com if it existed or com if foo.com does not exist). If dig does not have this information, then your nameservers may be down. Check by pinging your nameservers to see if they are up. If dig does list an authority section for foo.com, then check that foo.com's nameservers are up. You can get the nameservers for foo.com by either using dig foo.com (checks the DNS records) or whois foo.com (checks the registrar records). You can then ping the nameservers to see if they are up. If nameservers are down, retry later on. If all nameservers are up, then this is likely an invalid or no longer used domain name.
In this case, we have successfully looked up ftp.foo.com and gotten an IP address, so the DNS is working properly. Now we are timing out connecting to the IP address. The most common causes of this are routing issues or some sort of interference connecting to the FTP port such as no FTP service running on the machine, firewalls blocking connection to the FTP port or too much traffic to the server. You can check for routing issues by using ping to see if the server is up and traceroute to check the route from you to the server. If the machine appears to be up, then one of the other causes is at play.