Testing a Network Connection - Revision history

Paulm: Testing a Network Connection on the Command Line moved to Testing a Network Connection

2011-02-25T00:09:33Z

Testing a Network Connection on the Command Line moved to Testing a Network Connection

Paulm: /* Introduction */

2011-02-01T21:00:47Z

Introduction

Paulm at 20:58, 1 February 2011

2011-02-01T20:58:03Z

Paulm at 19:59, 24 December 2010

2010-12-24T19:59:26Z

Paulm at 19:58, 24 December 2010

2010-12-24T19:58:43Z

Paulm: New page: For a general conceptual overview of how networks work the wikipedia page on the [http://en.wikipedia.org/wiki/TCP/IP_model| TCP/IP model] and the[http://en.wikipedia.org/wiki/OSI_model|OS...

2010-12-15T21:02:34Z

New page: For a general conceptual overview of how networks work the wikipedia page on the [http://en.wikipedia.org/wiki/TCP/IP_model| TCP/IP model] and the[http://en.wikipedia.org/wiki/OSI_model|OS...

New page

For a general conceptual overview of how networks work the wikipedia page on the [http://en.wikipedia.org/wiki/TCP/IP_model| TCP/IP model] and the[http://en.wikipedia.org/wiki/OSI_model|OSI model] are a good places to start. You don't need to know all the gory details but it is useful

@@ Line 2: / Line 2: @@
 For a general conceptual overview of how networks work the wikipedia page on the [http://en.wikipedia.org/wiki/TCP/IP_model| TCP/IP model] and the [http://en.wikipedia.org/wiki/OSI_model| OSI model] are a good places to start. You don't need to know all the gory details but it is useful to have some understanding of the layered model of network connections. The basic idea is that networks are represented as a series of distinct layers each resting one on top of the other. At the bottom of the pile is the physical layer in the OSI model. In the tcp/ip model this is the link layer which combines the physical layer with  the logical network e.g. Ethernet. On top of this in the TCP/IP model you have:
-Internet layer -- this includes IP in TCP/IP as well as ICMP etc. IP is responsible for addressing and routing packets over the Internet -- hence IP address. It is not designed to be reliable, it will allow packets for example, just to get them there (Reliability is provided by the next layer). Ping works on this level.
+* Internet layer -- this includes IP in TCP/IP as well as ICMP etc. IP is responsible for addressing and routing packets over the Internet -- hence IP address. It is not designed to be reliable, it will allow packets for example, just to get them there (Reliability is provided by the next layer). Ping works on this level.
-Transport Layer -- TCP, UDP etc. This provides end to end communication for applications. TCP provides transport for the data and provides reliability by allowing for resending and re-ordering of packets.
+The reason for knowing this is that it gives us a model to work from so we can test consistently (by starting at the lowest level and working our way up or vice versa, I strongly encourage you to do the former, this is how this article will be structured).

@@ Line 1: / Line 1: @@
 For a general conceptual overview of how networks work the wikipedia page on the [http://en.wikipedia.org/wiki/TCP/IP_model| TCP/IP model] and the [http://en.wikipedia.org/wiki/OSI_model| OSI model] are a good places to start. You don't need to know all the gory details but it is useful to have some understanding of the layered model of network connections. The basic idea is that networks are represented as a series of distinct layers each resting one on top of the other. At the bottom of the pile is the physical layer in the OSI model. In the tcp/ip model this is the link layer which combines the physical layer with  the logical network e.g. Ethernet. On top of this in the TCP/IP model you have:
@@ Line 8: / Line 9: @@
 The Application Layer -- this is top layer it covers all the common Internet protocols: DNS, HTTP, SMTP, IMAP, POP3, SSH, BitTorrent etc (it doesn't include the programs that use these themselves).
-The advantage to knowing all this is we can test consistently starting at the lowest level and working out way up.
+The advantage to knowing all this is we can test consistently by starting at the lowest level and working our way up (or vice versa).

← Older revision		Revision as of 19:59, 24 December 2010
Line 8:		Line 8:
	The Application Layer -- this is top layer it covers all the common Internet protocols: DNS, HTTP, SMTP, IMAP, POP3, SSH, BitTorrent etc (it doesn't include the programs that use these themselves).		The Application Layer -- this is top layer it covers all the common Internet protocols: DNS, HTTP, SMTP, IMAP, POP3, SSH, BitTorrent etc (it doesn't include the programs that use these themselves).

−	The advantage to knowing all this is we can test consistently starting at ~~lthe~~ lowest level and working up.	+	The advantage to knowing all this is we can test consistently starting at the lowest level and working out way up.

← Older revision		Revision as of 19:58, 24 December 2010
Line 1:		Line 1:
−	For a general conceptual overview of how networks work the wikipedia page on the [http://en.wikipedia.org/wiki/TCP/IP_model\| TCP/IP model] and the[http://en.wikipedia.org/wiki/OSI_model\|OSI model] are a good places to start. You don't need to know all the gory details but it is useful	+	For a general conceptual overview of how networks work the wikipedia page on the [http://en.wikipedia.org/wiki/TCP/IP_model\| TCP/IP model] and the [http://en.wikipedia.org/wiki/OSI_model\| OSI model] are a good places to start. You don't need to know all the gory details but it is useful to have some understanding of the layered model of network connections. The basic idea is that networks are represented as a series of distinct layers each resting one on top of the other. At the bottom of the pile is the physical layer in the OSI model. In the tcp/ip model this is the link layer which combines the physical layer with the logical network e.g. Ethernet. On top of this in the TCP/IP model you have:
		+
		+	Internet layer -- this includes IP in TCP/IP as well as ICMP etc. IP is responsible for addressing and routing packets over the Internet -- hence IP address. It is not designed to be reliable, it will allow packets for example, just to get them there (Reliability is provided by the next layer). Ping works on this level.
		+
		+	Transport Layer -- TCP, UDP etc. This provides end to end communication for applications. TCP provides transport for the data and provides reliability by allowing for resending and re-ordering of packets.
		+
		+
		+	The Application Layer -- this is top layer it covers all the common Internet protocols: DNS, HTTP, SMTP, IMAP, POP3, SSH, BitTorrent etc (it doesn't include the programs that use these themselves).
		+
		+	The advantage to knowing all this is we can test consistently starting at lthe lowest level and working up.

← Older revision	Revision as of 00:09, 25 February 2011
(No difference)