<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>NetworkingReviews.com &#187; IP Network Tutorials</title>
	<atom:link href="http://www.networkingreviews.com/category/ip-network-tutorials/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.networkingreviews.com</link>
	<description></description>
	<lastBuildDate>Sun, 08 Jan 2012 18:33:26 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Public and Private IP addresses explained. What is NAT.</title>
		<link>http://www.networkingreviews.com/2008/09/22/public-and-private-ip-addresses-explained-what-is-nat/</link>
		<comments>http://www.networkingreviews.com/2008/09/22/public-and-private-ip-addresses-explained-what-is-nat/#comments</comments>
		<pubDate>Mon, 22 Sep 2008 14:32:09 +0000</pubDate>
		<dc:creator>BlogAdmin</dc:creator>
				<category><![CDATA[IP Network Tutorials]]></category>
		<category><![CDATA[nat]]></category>
		<category><![CDATA[network address translation]]></category>
		<category><![CDATA[private ip address]]></category>
		<category><![CDATA[public ip address]]></category>

		<guid isPermaLink="false">http://www.networkingreviews.com/?p=248</guid>
		<description><![CDATA[Any networked device (computer, server, printer, router etc), needs an IP address to communicate either on the Internet or on its local area network (LAN). Especially for internet communication, this IP address has to be unique, in order to avoid address conflicts. The IP address that is used by a device to communicate on the [...]<div class="addthis_toolbox addthis_default_style " addthis:url='http://www.networkingreviews.com/2008/09/22/public-and-private-ip-addresses-explained-what-is-nat/' addthis:title='Public and Private IP addresses explained. What is NAT. '  ><a class="addthis_button_facebook_like" fb:like:layout="button_count"></a><a class="addthis_button_tweet"></a><a class="addthis_button_google_plusone" g:plusone:size="medium"></a><a class="addthis_counter addthis_pill_style"></a></div>]]></description>
			<content:encoded><![CDATA[<p>Any networked device (computer, server, printer, router etc), needs an IP address to communicate either on the Internet or on its local area network (LAN). Especially for internet communication, this IP address has to be unique, in order to avoid address conflicts. The IP address that is used by a device to communicate on the Internet is called “Public” address, and it is registered with the Internet Network Information Centre (InterNIC) which takes care of the uniqueness factor. We could have only “Public” IP addresses assigned to all network devices, but this is not possible since the current IP address range (32-bit addresses for IPv4) is not enough to cover all network nodes. Therefore, the Internet network community (IETF etc) has established three “Private” address ranges, which can be given to network devices that belong to a local private network which does not connect directly to the Internet cloud.</p>
<p>These “Private” address ranges are the following:</p>
<ul>
<li> From 10.0.0.0 to 10.255.255.255</li>
<li> From 172.16.0.0 to 172.31.255.255</li>
<li> From 192.168.0.0 to 192.168.255.255</li>
</ul>
<p>Now, the most common practice today for Network engineers is to assign private IP addresses to devices in their private Local networks, and use Network Address Translation (NAT) if a device needs to access the Internet. The purpose of NAT is to translate the source private IP address of the network device into a public IP address in order to communicate with another host on the Internet. Since NAT allows many-to-one IP translation, you can have many private IP addresses translated to a single public address, thus saving address space.</p>
<div class="addthis_toolbox addthis_default_style " addthis:url='http://www.networkingreviews.com/2008/09/22/public-and-private-ip-addresses-explained-what-is-nat/' addthis:title='Public and Private IP addresses explained. What is NAT. '  ><a class="addthis_button_facebook_like" fb:like:layout="button_count"></a><a class="addthis_button_tweet"></a><a class="addthis_button_google_plusone" g:plusone:size="medium"></a><a class="addthis_counter addthis_pill_style"></a></div>]]></content:encoded>
			<wfw:commentRss>http://www.networkingreviews.com/2008/09/22/public-and-private-ip-addresses-explained-what-is-nat/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Computer Networks Overview</title>
		<link>http://www.networkingreviews.com/2008/05/28/computer-networks-overview/</link>
		<comments>http://www.networkingreviews.com/2008/05/28/computer-networks-overview/#comments</comments>
		<pubDate>Wed, 28 May 2008 11:23:19 +0000</pubDate>
		<dc:creator>BlogAdmin</dc:creator>
				<category><![CDATA[IP Network Tutorials]]></category>
		<category><![CDATA[communication networks]]></category>
		<category><![CDATA[computer network]]></category>
		<category><![CDATA[computer networks]]></category>
		<category><![CDATA[telecom networks]]></category>

		<guid isPermaLink="false">http://www.networkingreviews.com/?p=80</guid>
		<description><![CDATA[The term networks (communication networks) generally refers to systems hardware, software and services / opportunities, aimed at transmission and routing data and to transfer information between electronic / channels (such as various types of computers, terminals, telephones) . The term includes the various technologies telecommunications networks computer networks (local (LANs), Metropolitan (MANs), wide area (WANs) [...]<div class="addthis_toolbox addthis_default_style " addthis:url='http://www.networkingreviews.com/2008/05/28/computer-networks-overview/' addthis:title='Computer Networks Overview '  ><a class="addthis_button_facebook_like" fb:like:layout="button_count"></a><a class="addthis_button_tweet"></a><a class="addthis_button_google_plusone" g:plusone:size="medium"></a><a class="addthis_counter addthis_pill_style"></a></div>]]></description>
			<content:encoded><![CDATA[<p>The term networks (communication networks) generally refers to systems hardware, software and services / opportunities, aimed at transmission and routing data and to transfer information between electronic / channels (such as various types of computers, terminals, telephones) .</p>
<p>The term includes the various technologies</p>
<ul>
<li>telecommunications networks</li>
<li>computer networks (local (LANs), Metropolitan (MANs), wide area (WANs) and Websites)</li>
<li>integrated services digital networks close (N-ISDN) and large B-ISDN) zone, and all wireless communication technologies.</li>
</ul>
<p>For the classification of networks can be used several characteristics:<span id="more-80"></span></p>
<p><strong><span style="text-decoration: underline;">The architecture and techniques used for transporting data, which are:</span></strong></p>
<ul>
<li>Switching circuit package, frame, cell</li>
<li>Broadcast networks.</li>
</ul>
<p><strong><span style="text-decoration: underline;">The geographical coverage offered </span></strong></p>
<ul>
<li>Data flow machines and multiprocessor systems</li>
<li>Local Computer Networks [Local Area Networks]</li>
<li>Metropolitan Area Networks</li>
<li>Regional Area Networks</li>
<li>Wide Area Networks</li>
<li>Interconnection of long haul networks or Global Area Networks</li>
</ul>
<p><strong><span style="text-decoration: underline;">The bandwidth offered (bandwidth) </span></strong></p>
<p><strong><span style="text-decoration: underline;">The type of applications supported </span></strong></p>
<p><strong><span style="text-decoration: underline;">The regulatory framework for the operation </span></strong></p>
<p><strong><span style="text-decoration: underline;">The used hardware and software, etc. </span></strong></p>
<p>Both the technology and the different standards, leading to a single communication system, which will consolidate all communications patterns, which will provide broad geographic coverage, and seamless and easy access to all sources of information. It is clear that a basic condition for achieving these objectives is the existence of a modern telecommunications infrastructure polydynamics. The infrastructure should provide the widest possible geographical coverage, to provide a basic standard set of advanced services with high added value and have the prospect of switching to high-speed networks (2 Mbps to 622.5 Mbps.)</p>
<p>Technoeconomical key factors of development of each communication technology, but also functional integration of individual infrastructure is a mature and widely accepted standard, which refer to protocols (ie, a set of rules and conditions which determine the communication) a specific architecture (Reference Model ).  The most famous architecture is that of seven levels, which is described as Reference Model Open Systems Interface (OSIRM-Open Systems Interconnect Reference Model).<br />
 Despite the fact that the OSI model has contributed greatly to the broad dissemination of the concepts of protocols in layers and that is an extremely useful tool for presentation and comparative study of various technologies, the same protocols OSI does not have the broad dissemination of other similar architectures (DoD example of architecture with plenty of protocols TCP / IP).</p>
<p>The technical description followed the model OSI, is that architecture in layers / levels (layered architecture). Each open system divided logically arranged in a set of subsystems and communications functions are shared in a sharply ordered all epipedon. Basic functions that are common at all levels are:</p>
<p><strong><span style="text-decoration: underline;">Encapsulation (Encapsulation) </span></strong></p>
<p><strong><span style="text-decoration: underline;">Segmentation (Segmentation) </span></strong></p>
<p><strong><span style="text-decoration: underline;">Installation Association (Connection Establishment) </span></strong></p>
<p><strong><span style="text-decoration: underline;">Flow Control (Flow Control) </span></strong></p>
<p><strong><span style="text-decoration: underline;">Error Control (Error Control) </span></strong></p>
<p><strong><span style="text-decoration: underline;">Polyplexia (Multiplexing) </span></strong></p>
<p><strong><span style="text-decoration: underline;">Transfer Means </span></strong></p>
<ul>
<li>Twisted Pair</li>
<li>Baseband Coaxial Cable</li>
<li>Broadband Coaxial Cable</li>
<li>Fiber Optics</li>
</ul>
<div class="addthis_toolbox addthis_default_style " addthis:url='http://www.networkingreviews.com/2008/05/28/computer-networks-overview/' addthis:title='Computer Networks Overview '  ><a class="addthis_button_facebook_like" fb:like:layout="button_count"></a><a class="addthis_button_tweet"></a><a class="addthis_button_google_plusone" g:plusone:size="medium"></a><a class="addthis_counter addthis_pill_style"></a></div>]]></content:encoded>
			<wfw:commentRss>http://www.networkingreviews.com/2008/05/28/computer-networks-overview/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What is Virtual Private Network (VPN)</title>
		<link>http://www.networkingreviews.com/2008/05/13/what-is-virtual-private-network-vpn/</link>
		<comments>http://www.networkingreviews.com/2008/05/13/what-is-virtual-private-network-vpn/#comments</comments>
		<pubDate>Tue, 13 May 2008 10:36:13 +0000</pubDate>
		<dc:creator>BlogAdmin</dc:creator>
				<category><![CDATA[IP Network Tutorials]]></category>
		<category><![CDATA[ipsec]]></category>
		<category><![CDATA[pptp]]></category>
		<category><![CDATA[tunneling]]></category>
		<category><![CDATA[virtual private network]]></category>
		<category><![CDATA[vpn]]></category>

		<guid isPermaLink="false">http://www.networkingreviews.com/?p=74</guid>
		<description><![CDATA[This online quiz is a series of essential questions about VPNs. Although many of the technical details of VPNs are hidden from the casual user, several aspects of the technology directly affect the &#8220;user experience,&#8221; and it is important to understand these. Students, networking professionals, corporate employees, and anyone else interested in the basic technology [...]<div class="addthis_toolbox addthis_default_style " addthis:url='http://www.networkingreviews.com/2008/05/13/what-is-virtual-private-network-vpn/' addthis:title='What is Virtual Private Network (VPN) '  ><a class="addthis_button_facebook_like" fb:like:layout="button_count"></a><a class="addthis_button_tweet"></a><a class="addthis_button_google_plusone" g:plusone:size="medium"></a><a class="addthis_counter addthis_pill_style"></a></div>]]></description>
			<content:encoded><![CDATA[<p>This online quiz is a series of essential questions about VPNs. Although many of the technical details of VPNs are hidden from the casual user, several aspects of the technology directly affect the &#8220;user experience,&#8221; and it is important to understand these.</p>
<p>Students, networking professionals, corporate employees, and anyone else interested in the basic technology of computer networks should find this a valuable study guide.<span id="more-74"></span></p>
<p><strong>1. VPN stands for</strong></p>
<p>a) Virtual Public Network<br />
b) Virtual Protocol Network<br />
c) Virtual Perimeter Network<br />
d) Virtual Private Network</p>
<p>Answer: <strong>d) Virtual Private Network</strong><br />
VPN stands for &#8220;Virtual Private Network&#8221; or &#8220;Virtual Private Networking.&#8221; A VPN is a private network in the sense that it carries controlled information, protected by various security mechanisms, between known parties. VPNs are only &#8220;virtually&#8221; private, however, because this data actually travels over shared public networks instead of fully dedicated private connections.<br />
 </p>
<p><strong>2. What is the main benefit of VPNs compared to dedicated networks utilizing frame relay, leased lines, and traditional dial-up? </strong></p>
<p>a) improved security<br />
b) reduced cost<br />
c) better network performance<br />
d) less downtime on average</p>
<p>Answer: <strong>b) Reduced Cost</strong><br />
The main benefit of a VPN is the potential for significant cost savings compared to traditional leased lines or dial up networking. These savings come with a certain amount of risk, however, particularly when using the public Internet as the delivery mechanism for VPN data. The performance of a VPN will be more unpredictable and generally slower than dedicated lines due to public Net traffic. Likewise, many more points of failure can affect a Net-based VPN than in a closed private system. Utilizing any public network for communications naturally raises new security concerns not present when using more controlled environments like point-to-point leased lines.</p>
<p><strong>3. VPNs save money by</strong><br />
a) reducing the need for long distance telephone calls<br />
b) reducing the need for modem pools and remote access servers<br />
c) reducing the need for leased lines<br />
d) all of the above</p>
<p>Answer: <strong>d) All of the above</strong><br />
VPNs may save money in several different ways. Companies that lease private lines typically pay a very high monthly fee, and a VPN can replace these lines with much less expensive, shorter connections to a local ISP. VPNs can also support remote access connectivity for travelers. Instead of configuring remote access servers and paying for the long-distance charges to reach them, an organization can rely on an ISP to support local access on both ends of the VPN connection.</p>
<p><strong>4. What is the relationship between a VPN and an extranet?</strong></p>
<p>a) VPNs are unrelated to extranets<br />
b) some extranets are VPNs and all VPNs are extranets<br />
c) some extranets are VPNs and some VPNs are extranets<br />
d) VPNs and extranets are two terms for the same type of network</p>
<p>Answer: <strong>b) some extranets are VPNs and all VPNs are extranets</strong><br />
Many VPNs support the same main feature of an extranet &#8212; controlled access by third parties to protected network resources. Some VPNs, however, exist only to provide remote access to employees within the organization; these are technically wide-area intranets. A few VPNs also implement local-area intranets that limit or meter access to one internal LAN from other internal LANs.</p>
<p><strong>5. In VPNs, the term &#8220;tunneling&#8221; refers to<br />
</strong>a) a marketing strategy that involves selling VPN products for very low prices in return for expensive service contracts<br />
b) an optional feature that increases network performance if it is turned on<br />
c) the encapsulation of packets inside packets of a different protocol to create and maintain the virtual circuit<br />
d) the method a system administrator uses to detect hackers on the network</p>
<p>Answer: <strong>c) the encapsulation of packets inside packets of a different protocol to create and maintain the virtual circuit</strong></p>
<p>VPN tunneling transforms packets from a VPN tunneling protocol format to a different format before being transmitted over the public network. This technique, called encapsulation, is used in several network technologies besides VPN. Once encapsulated, VPN protocol packets are responsible for creating and maintaining the private connection &#8212; including set-up and tear-down details. Tunneling is the essential feature behind any VPN implementation.</p>
<p><strong>6. Which of the following are VPN tunneling protocols?<br />
</strong>a) IPSEC<br />
b) PPTP<br />
c) L2TP<br />
d) All of the above</p>
<p>Answer: <strong>d) All of the above</strong><br />
PPTP, IPsec, and L2TP are three of today&#8217;s most popular VPN tunneling protocols. Each one of these is capable of supporting a secure VPN connection.</p>
<p><strong>7. PPTP stands for<br />
</strong>a) Place to Place Tunneling Protocol<br />
b) Point to Point Tunneling Protocol<br />
c) Pretty Pointless Traffic Producer<br />
d) Private Protocol Transfer Process</p>
<p>Answer: <strong>b) All of the above</strong></p>
<p>PPTP stands for Point to Point Tunneling Protocol. PPTP is a protocol specification developed by several companies. However, people generally associate PPTP with Microsoft because nearly all flavors of Windows include built-in support for this protocol.</p>
<p><strong>8. What is the basic difference between a VPN and a firewall?<br />
</strong>a) firewalls can be configured by an administrator but VPNs cannot be configured<br />
b) there is no fundamental difference exists between firewalls and VPNs<br />
c) firewalls are designed to block network traffic and VPNs are designed to deliver traffic<br />
d) firewalls are a less secure form of VPN</p>
<p>Answer: <strong>c) firewalls are designed to block network traffic and VPNs are designed to deliver traffic</strong></p>
<p>VPNs establish a guarded connection and transmit data across that link, whereas firewalls sit at strategic locations on the network and watch for certain types of traffic to block. An appropriately configured VPN can communicate through firewalls.</p>
<p><strong>9. What network port does PPTP use to establish communication?</strong></p>
<p>a) 25/udp<br />
b) 25/tcp<br />
c) 1723/udp<br />
d) 1723/tcp</p>
<p>Answer: <strong>d)1723/tcp</strong></p>
<p>PPTP uses TCP port 1723 to establish a connection. When opening holes in a firewall to support PPTP, one must be careful to not specify UDP port 1723 instead of TCP.<br />
Also, PPTP uses IP port 47, designed for &#8220;General Routing Encapsulation&#8221; or GRE packets. A common mistake in configuring firewalls for use with PPTP is to open port 1723 (allowing connections to be established) but fail to open port 47 (denying actual data from passing through the tunnel). Some operating systems include &#8220;PPTP ping&#8221; utiliies (pptpsrv and pptpclnt in Windows 2000) that verify both PPTP ports are opened.</p>
<p><strong>10. Which approach to VPNs is the best one?<br />
</strong>a) router-based<br />
b) software only<br />
c) VPN-specific gateway device<br />
d) firewall-based</p>
<p>Answer: c) VPN Specific gateway device</p>
<p> Each of these four alternatives is a viable approach to implementing a VPN, and vendors supply products in each of these areas. Some people may prefer the convenience of a &#8220;VPN in a box&#8221; as provided by special-purpose gateway devices. Those with routers and firewalls already present in their network may prefer to extend these for VPNs. Finally, those wanting to avoid hardware purchases can select a software-only VPN solution that meets their needs.</p>
<div class="addthis_toolbox addthis_default_style " addthis:url='http://www.networkingreviews.com/2008/05/13/what-is-virtual-private-network-vpn/' addthis:title='What is Virtual Private Network (VPN) '  ><a class="addthis_button_facebook_like" fb:like:layout="button_count"></a><a class="addthis_button_tweet"></a><a class="addthis_button_google_plusone" g:plusone:size="medium"></a><a class="addthis_counter addthis_pill_style"></a></div>]]></content:encoded>
			<wfw:commentRss>http://www.networkingreviews.com/2008/05/13/what-is-virtual-private-network-vpn/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The base of IP Networks &#8211; OSI Model</title>
		<link>http://www.networkingreviews.com/2008/02/29/the-base-of-ip-networks-osi-model/</link>
		<comments>http://www.networkingreviews.com/2008/02/29/the-base-of-ip-networks-osi-model/#comments</comments>
		<pubDate>Fri, 29 Feb 2008 11:15:40 +0000</pubDate>
		<dc:creator>BlogAdmin</dc:creator>
				<category><![CDATA[IP Network Tutorials]]></category>

		<guid isPermaLink="false">http://networkingreviews.com/blog/2008/02/29/the-base-of-ip-networks-osi-model/</guid>
		<description><![CDATA[Please Do Not Throw Sausage Pizza Away !!! You might be wondering what I am talking about, but take a closer look at the Red letters above&#8230;Yes you are right, these are the first letters of the 7 Layers of the OSI Model, the fundamental building block of TCP/IP Networks. The 7 Layers of the [...]<div class="addthis_toolbox addthis_default_style " addthis:url='http://www.networkingreviews.com/2008/02/29/the-base-of-ip-networks-osi-model/' addthis:title='The base of IP Networks &#8211; OSI Model '  ><a class="addthis_button_facebook_like" fb:like:layout="button_count"></a><a class="addthis_button_tweet"></a><a class="addthis_button_google_plusone" g:plusone:size="medium"></a><a class="addthis_counter addthis_pill_style"></a></div>]]></description>
			<content:encoded><![CDATA[<p><font size="+1"><font color="#ff0000"><strong>P</strong></font>lease <font color="#ff0000"><strong>D</strong></font>o <font color="#ff0000"><strong>N</strong></font>ot <font color="#ff0000"><strong>T</strong></font>hrow <font color="#ff0000"><strong>S</strong></font>ausage <font color="#ff0000"><strong>P</strong></font>izza <font color="#ff0000"><strong>A</strong></font>way !!!</font></p>
<p>You might be wondering what I am talking about, but take a closer look at the Red letters above&#8230;Yes you are right, these are the first letters of the 7 Layers of the OSI Model, the fundamental building block of TCP/IP Networks.</p>
<p>The 7 Layers of the OSI Model are shown below.<span id="more-7"></span></p>
<p align="center"><img src="/images/osi-model-7-layers.png" alt="osi model" /></p>
<ul type="disc">
<li><u><strong>Layer1:</strong></u><font color="#ff0000"><font size="+1">P</font></font>hysical Layer</li>
<li><strong><u>Layer2:</u></strong><font color="#ff0000" size="+1">D</font>ata Link Layer</li>
<li><strong><u>Layer3:</u></strong> <font color="#ff0000" size="+1">N</font>etwork Layer</li>
<li><strong><u>Layer4:</u></strong> <font color="#ff0000" size="+1">T</font>ransport Layer</li>
<li><strong><u>Layer5:</u></strong> <font color="#ff0000" size="+1">S</font>ession Layer</li>
<li><strong><u>Layer6:</u></strong> <font color="#ff0000" size="+1">P</font>resentation Layer</li>
<li><strong><u>Layer7:</u></strong> <font color="#ff0000" size="+1">A</font>pplication Layer</li>
</ul>
<p>The OSI reference model specifies standards for describing &#8220;Open Systems Interconnection&#8221;. The term &#8216;open&#8217; was chosen to emphasise the fact that by using these international standards, a system may be defined which is open to all other systems obeying the same standards throughout the world.</p>
<p>It consists of 7 Layers with each Layer being functionally independent of the others. Control is passed from one layer to the next, starting at the top and proceeding to the bottom layer, over the channel to the other station and back up the layers. The receiving layer at the destination host receives exactly the same object as sent by the matching layer at the source host. This is shown in the diagram below:</p>
<p align="center"><img src="/images/osi.gif" alt="osi model data flow" /></p>
<p>The layers are in two groups. The upper four layers are used whenever a message passes from or to a user. The lower three layers are used when any message passes through the host computer. Messages intended for this computer pass to the upper layers. Messages destined for some other host are not passed up to the upper layers but are forwarded to another host.</p>
<p>The sending process passes data to the application layer. The application layer attaches an application header and then passes the frame to the presentation layer.</p>
<p><!--adsense--></p>
<p>The presentation layer can transform data in various ways, if necessary, such as by translating it and adding a header. It gives the result to the session layer. The presentation layer is not aware of which portion (if any) of the data received from the application layer is the application header and which portion is actually user data, because that information is irrelevant to the presentation layer&#8217;s role.</p>
<p>The process of adding headers is repeated from layer to layer until the frame reaches the data link layer. There, in addition to a data-link header, a data-link trailer is added. The data-link trailer contains a checksum and padding if needed. This aids in frame synchronization. The frame is passed down to the physical layer, where it is transmitted to the receiving host. On the receiving host, the various headers and the data trailer are stripped off one by one as the frame ascends the layers and finally reaches the receiving process.</p>
<div class="addthis_toolbox addthis_default_style " addthis:url='http://www.networkingreviews.com/2008/02/29/the-base-of-ip-networks-osi-model/' addthis:title='The base of IP Networks &#8211; OSI Model '  ><a class="addthis_button_facebook_like" fb:like:layout="button_count"></a><a class="addthis_button_tweet"></a><a class="addthis_button_google_plusone" g:plusone:size="medium"></a><a class="addthis_counter addthis_pill_style"></a></div>]]></content:encoded>
			<wfw:commentRss>http://www.networkingreviews.com/2008/02/29/the-base-of-ip-networks-osi-model/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>How to access remotely your internal network</title>
		<link>http://www.networkingreviews.com/2008/02/28/how-to-access-remotely-your-internal-network/</link>
		<comments>http://www.networkingreviews.com/2008/02/28/how-to-access-remotely-your-internal-network/#comments</comments>
		<pubDate>Thu, 28 Feb 2008 15:23:19 +0000</pubDate>
		<dc:creator>BlogAdmin</dc:creator>
				<category><![CDATA[IP Network Tutorials]]></category>

		<guid isPermaLink="false">http://networkingreviews.com/blog/2008/02/28/how-to-access-remotely-your-internal-network/</guid>
		<description><![CDATA[Remotely Accessing your internal network and data is sometimes mandatory and can be used for a variety of reasons. Maybe you are outsourcing some of your business to an external partner, maybe you require external technical support, or you may have employees on the road or tele-workers that require access to internal data and resources [...]<div class="addthis_toolbox addthis_default_style " addthis:url='http://www.networkingreviews.com/2008/02/28/how-to-access-remotely-your-internal-network/' addthis:title='How to access remotely your internal network '  ><a class="addthis_button_facebook_like" fb:like:layout="button_count"></a><a class="addthis_button_tweet"></a><a class="addthis_button_google_plusone" g:plusone:size="medium"></a><a class="addthis_counter addthis_pill_style"></a></div>]]></description>
			<content:encoded><![CDATA[<p>Remotely Accessing your internal network and data is sometimes mandatory and can be used for a variety of reasons. Maybe you are outsourcing some of your business to an external partner, maybe you require external technical support, or you may have employees on the road or tele-workers that require access to internal data and resources in your company. In any case, you must take measures to protect your data and network, but still keep the operation of your remote access service as functional as possible.</p>
<p>In this article I describe the most popular methods and technologies available to use in order to enable your company users to access internal data from outside your company.<span id="more-5"></span></p>
<p><strong><u>1. Dial-up access</u></strong></p>
<p>This method was very popular in the past, but nowadays is not used so much since there are other faster and more secure technologies. Basically, a dial-in modem is installed on the serial port of your Remote Access Server (RAS), which serves as the entry point in your network. A remote user dials-in the company’s modem number, using for example the Microsoft Dial-up Networking (DUN), and is authenticated by the RAS server before entering the internal network. This method is vulnerable to ‘war dialers’ which are tools used to scan telephone networks and get access to dial-up modems for hacking into your network.<br />
  </p>
<p><strong><u>2. IPSEC VPN with Remote Access VPN Client</u></strong></p>
<p>This is probably the most secure and popular method used when individual users want to connect with their laptops or desktop computers from outside your corporate network. A VPN client has to be installed on the user’s computer, and there has to be an Internet connection available for the remote user. The VPN client creates a secure and encrypted IPSEC tunnel between the laptop of the user and the corporate office. This tunnel is terminated on a VPN IPSEC capable device located in the company office. Even if this VPN tunnel goes through the Internet, the IPSEC protocol encrypts all the data flowing inside the tunnel, thus providing strong security.</p>
<p><strong><u>3. IPSEC VPN with </u></strong><strong><u>LAN</u></strong><strong><u>-to-</u></strong><strong><u>LAN</u></strong><strong><u> Communication</u></strong></p>
<p>This method uses again the IPSEC protocol, but it is utilized for connecting a whole remote office LAN with the central corporate office, rather than individual users. The remote office has to be equipped with an IPSEC capable device and connection to the Internet. The IPSEC device (router, firewall etc) creates a VPN tunnel with the IPSEC device in the central office, thus creating a secure tunnel to connect the two data LANs. Even if the two LAN networks have private IP addresses (e.g 192.168.1.0 or 10.1.1.0 etc), they can still communicate through the Internet since the VPN tunnel encapsulates all data within public addresses which are routable in the Internet.</p>
<p><strong><u>4. SSL VPN</u></strong></p>
<p>SSL (Secure Sockets Layer) is the security protocol that is used extensively in web browsers. It employs the public and private key encryption system from RSA, and it provides secure and flexible communications through the internet. SSL VPN gains a lot of popularity since it already exists inside web browsers, and does not require an extra VPN client to be installed on the user’s computer. The central corporate office has to be equipped with an SSL VPN termination device, and the remote clients just need to use their web browser for connecting to their corporate office.   </p>
<p><!-- InstanceEndEditable --></p>
<div class="addthis_toolbox addthis_default_style " addthis:url='http://www.networkingreviews.com/2008/02/28/how-to-access-remotely-your-internal-network/' addthis:title='How to access remotely your internal network '  ><a class="addthis_button_facebook_like" fb:like:layout="button_count"></a><a class="addthis_button_tweet"></a><a class="addthis_button_google_plusone" g:plusone:size="medium"></a><a class="addthis_counter addthis_pill_style"></a></div>]]></content:encoded>
			<wfw:commentRss>http://www.networkingreviews.com/2008/02/28/how-to-access-remotely-your-internal-network/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Base of TCP/IP Networking</title>
		<link>http://www.networkingreviews.com/2008/02/28/the-base-of-tcpip-networking/</link>
		<comments>http://www.networkingreviews.com/2008/02/28/the-base-of-tcpip-networking/#comments</comments>
		<pubDate>Thu, 28 Feb 2008 15:04:16 +0000</pubDate>
		<dc:creator>BlogAdmin</dc:creator>
				<category><![CDATA[IP Network Tutorials]]></category>

		<guid isPermaLink="false">http://networkingreviews.com/blog/2008/02/28/the-base-of-tcpip-networking/</guid>
		<description><![CDATA[A few years ago there was a big hype about &#8220;being online&#8221;. Everyone had to be online and there wasn&#8217;t one day where you didn&#8217;t have to be afraid that you missed the coolest and newest technology. This was just the TCP/IP layer and it was already well known for over 20 years back then. [...]<div class="addthis_toolbox addthis_default_style " addthis:url='http://www.networkingreviews.com/2008/02/28/the-base-of-tcpip-networking/' addthis:title='The Base of TCP/IP Networking '  ><a class="addthis_button_facebook_like" fb:like:layout="button_count"></a><a class="addthis_button_tweet"></a><a class="addthis_button_google_plusone" g:plusone:size="medium"></a><a class="addthis_counter addthis_pill_style"></a></div>]]></description>
			<content:encoded><![CDATA[<p>A few years ago there was a big hype about &#8220;being online&#8221;. Everyone had to be online and there wasn&#8217;t one day where you didn&#8217;t have to be afraid that you missed the coolest and newest technology. This was just the TCP/IP layer and it was already well known for over 20 years back then.</p>
<p>So what is this TCP/IP thing? What good does it do for you and has this been the latest thing or will it even get better? This article is trying to touch some of the aspects of the TCP/IP layer, higher level protocols based on it and give a brief outlook on what is next.<span id="more-4"></span></p>
<p><strong>1. TCP what?</strong><br />
TCP/IP is an abbreviation for Transmission Control Protocol/Internet Protocol. It only has one task: it makes sure that all of your data is sent across the internet and is being delivered to the right computer.</p>
<p>TCP/IP is a bundle of communication rules. Without it, data could not be transported in a reliable manner and hardware independent from one computer to another. As such, it is the basis of the internet as we know it today.</p>
<p>However, it is important to understand that TCP/IP are just the parents in a family of networking protocols. There are other families of networking protocols and there are (if we keep the image of the family in mind) children and relatives belonging to the TCP/IP family.</p>
<p><strong>2. Layers </strong><br />
So, are you one of the fellows who first went online with Dial Up Networking on a Microsoft system? Have you ever clicked with your right mouse button on DUN to see further info and see how many packages you have transmitted over your dialup connection? Those packages were prepared and send out by mom and dad of the TCP/IP family. Surely, you probably never cared about this, unless you had problems with your dialup connection. But we are going to have a closer look at the microcosm of this newly discovered family.</p>
<p>Unfortunately, the TCP/IP family is somewhat limited and they sort of don&#8217;t get the bigger picture. This is a good thing though. They don&#8217;t pack up the 5MB MP3 song you are trading over Kazaa et al. at once. They slice your data into several hierarchical structured little packages. It doesn&#8217;t matter whether you send an email, use a filesharing tool, browser the web, use an instant messeger or even look at the pics you&#8217;re not supposed to look at &#8211; every chunk of data is sliced into pieces and transmitted over this standardized protocol.</p>
<p>Without this standard, every developer would need to create his own (proprietary) method to transmit data. However, developers (just like mathematicians) don&#8217;t like to do a lot of extra work and they like to reuse functionality. They usually don&#8217;t care how the data gets from your computer and the modem over a phone line or network cable through a whole line or network of computers to its final destination.</p>
<p>However, we do and that&#8217;s the reason of this article.</p>
<p>Think of the TCP/IP family as a set of different layers. The top layer is the actual application protocol which communicates with the application of your choice (your filesharing tool, mail software, browser, instant messenger, etc).</p>
<p>The top layer communicates with the TCP layer, which prepares and forwards the data to the IP layer. The IP layer is directly responsible for communicating with the networking card and its drivers. This low level layer is often referred to as the data-link layer. But when your local tech guru talks to you about your data link layer he usually just means your ethernet card, modem, or wlan card. The card is responsible for feeding the data into the network cable and retrieving incoming packages from it. Once it has retried a data package, it forwards it to the next higher layer (IP).</p>
<p>Depending on the amount of data you can send and retrieve (also known as upstream or downstream ratio) we might be talking about hundreds of thousands of packages for a normal session.</p>
<p>Imagine the chaos and confusion if the data could not be put back together properly!</p>
<p><strong>Network drivers</strong></p>
<p>That&#8217;s exactly what would happen without the network driver. The network driver adds data to each data package in a so called header. The header contains information such as the length of the data package.</p>
<p><strong>The IP layer</strong></p>
<p>The IP layer is responsible for making sure that all data is routed properly. It&#8217;s a point to point protocol and doesn&#8217;t have to worry about the network cards or other hardware related issues involved. Basically all it needs to know is the IP address of the final destination.</p>
<p><strong>IP addresses and DNS</strong></p>
<p>So what is an IP address? An IP address is a something like 66.98.189.217 &#8211; it is the numeric address of a host in a network. Instead of going to &#8216;www.ezoshosting.com&#8217; you could as well go to 66.98.189.217 and you&#8217;d see the same site. Give it a try, type it in your browser&#8217;s address bar and if the ezoshosting IP address has not changed, since I type out this article on my keyboard, you will see the same thing as when accessing &#8216;www.ezoshosting.com&#8217;</p>
<p>That&#8217;s neat, right? Let&#8217;s have a quick look at how this trick works: If you enter &#8216;www.ezoshosting.com&#8217; in your browser, TCP/IP tries to resolve that address. At first, it will look at your local hosts file. The local hosts file is a plain text file that allows you to overwrite public domain names with your own assigned IP address. This is only effective if someone on your computer types in the name of the domain. While this is relatively simple and effective, this is also possibly quite evil and dangerous. There is an increasing trend by worm and virus authors to overwrite addresses of well known companies with maliscuous IP addresses, so, it&#8217;s a good practice to regularly check your hosts file (in Windows XP you can locate it in /Windows\System32\Drivers\Etc) and see if no one added a local entry for websites you regularly login to and enter high sensitive data.</p>
<p>If TCP does not find an entry in your hosts file, it will query your name server (which is usually the nameserver of your ISP). Your ISPs nameserver usually caches the values of an assigned IP address for 24 to 72 hours. So, if you go to &#8216;www.ezoshosting.com&#8217; and &#8216;www.ezoshosting.com&#8217; moves one hour later to a new IP address, you will still see the old IP address for as long as your ISP has the old address cached. If your local ISPs name servers don&#8217;t know the address of a domain name, they will query the next higher nameservers (and this goes on and on until they reach the level of the so called root-servers). If in doubt, the root servers can happily point to a set of nameservers that really is supposed to know which IP address you have to go to in order to retrieve data from a domain. The root servers gather this data from the<br />
registrars.</p>
<p><strong>Package headers</strong></p>
<p>Let&#8217;s have a close look at the header again. We already know that it has the length added by the network driver. But what other goodies does the family add to the package as it sends it out across the net? The IP layer adds the IP address of the final destination host and the IP address of the sending host. As with every species, there are slackers among the group of data packages. For one reason or another they just never arrive at the destination. That&#8217;s the reason why the destination needs the address of the sender so that it can answer and say &#8220;hey you, yes you, send me the package XYZ again&#8221; if a package XYZ was lost along the way.</p>
<p>Now let&#8217;s get back to the family business. After the IP layer received a block of data, it passes it on to the next higher level: the TCP layer.</p>
<p><strong>TCP layer</strong></p>
<p>While the IP layer does the basic work, the job of the TCP layer could be compared to the job of a supervisor. The data blocks I referred to earlier in the article are also known as segments. The TCP layer&#8217;s job is to make sure that segments arrive in the right order and without modification at the proper destination. So what do they need to do to achieve that? Right, they&#8217;re adding data to the header. The TCP layer adds a checksum and a number which contains the order the data packages need to be put back in later on. Imagine what would happen if packages wouldn&#8217;t be sorted. Did you ever listen to a song backwards? You would probably experience something similar if packages would not be numbered.</p>
<p><strong>UDP layer</strong></p>
<p>However, there are situations where TCP headers adds too much overhead to a connection, for example, if you are listening to a live music or video stream. In those situations it doesn&#8217;t really matter that you receive all packages all the time and in the right order. In those situations, you&#8217;re better off by using a more lightweight protocol such as the User Datagram Protocol (UDP).</p>
<p>UDP controls the data transfer at a very minimal level only. It does not guarantee that all segments arrive at the destination or that all of them arrive in the proper order.</p>
<p><strong>TCP and medieval cities</strong></p>
<p>Once TCP has verified that a data segment is correct, it removes the header and passes the data on to the actual application.</p>
<p>The actual applications are sitting behind a port and waiting on the input as delivered by TCP. Each application has at least one unique port. The route from the port to the actual application is called the application protocol. The concepts of ports and firewalls (which we can&#8217;t cover here) might be easy to visualize if you think of a medieval city. Back in the medieval ages, they had walls around the cities and gates to let people in and out. In some cities they had special gates for merchants, soldiers, etc. The walls are the firewall of our computer, the gates are the ports, and the different purposes of each gate can be compared to the different jobs an application needs to do.</p>
<p>A computer, just like the medieval city, can have different ports open at the same time &#8211; which guarantees that you can chat with friends while you are using a filesharing software.</p>
<p>There are several popular protocols: the Hypertext Transfer Protocol (HTTP), SMTP (Simple Mail Transfer Protocol), and FTP (File Transfer Protocol) are probably the most popular ones. The HTTP protocol standardizes how data needs to be formed so that your browser (no matter which one you use) is able to recognize the data it receives.</p>
<p>If you&#8217;re curious to see what the real text data your browser receives looks like and you know how to open a telnet session, we should have a closer look:</p>
<p>As I mentioned above, the different applications are sitting behind different unique ports. For a webserver behind a HTTP connection this is usually port 80, for a mailserver behind a SMTP connection this is usually port 25, for a FTP server behind a FTP connection this is usually port 21.</p>
<p><u>A sample HTTP connection</u></p>
<p>To connect to the webserver residing at &#8216;www.ezoshosting.com&#8217; through telnet, simply enter this command:</p>
<p><strong><em>telnet www.ezoshosting.com 80</em></strong></p>
<p><span lang="EN">The screen output will be something like this:</span></p>
<p><strong><code><span style="font-size: 10pt" lang="EN">Trying 66.98.189.217...</span></code><span style="font-size: 11pt; font-family: 'Courier New'" lang="EN"><br />
<code>Connected to www.ezoshosting.com.</code><br />
<code>Escape character is '^]'.</code></span></strong><span lang="EN"></span></p>
<p><span lang="EN">Now type the escape character and an actual webpage will be shown in its sourcecode to your telnet session. </span></p>
<p><u><span lang="EN">A sample SMTP connection</span></u><span lang="EN"> </span></p>
<p><span lang="EN">To connect to the mailserver residing at mail.ezoshosting.com through telnet, simply enter this command: </span></p>
<p><strong><em><code><span style="font-size: 10pt" lang="EN">telnet mail.ezoshosting.com 25</span></code></em></strong><span lang="EN"> </span></p>
<p><span lang="EN">The screen output will be something like this: </span></p>
<p><strong><code><span style="font-size: 10pt" lang="EN">Trying 66.98.189.217...</span></code><span style="font-size: 11pt; font-family: 'Courier New'" lang="EN"><br />
<code>Connected to mail.ezoshosting.com.</code><br />
<code>Escape character is '^]'.</code><br />
<code>220-houston.ezoshosting.com ESMTP Exim 4.24 #1 Fri, 30 Jan 2004 09:09:24 -0600</code><br />
<code>220-We do not authorize the use of this system to transport unsolicited,</code><br />
<code>220 and/or bulk e-mail.</code></span></strong><span lang="EN"> </span></p>
<p><span lang="EN">It will just sit there and do nothing. If you feel like it, you can communicate some more with the server: </span></p>
<p><strong><code><span style="font-size: 10pt" lang="EN">HELO tester.atsomedomain.com</span></code><span style="font-size: 11pt; font-family: 'Courier New'" lang="EN"><br />
<code>250-houston.ezoshosting.com Hello tester.atsomedomain.com[ipaddresshere]</code><br />
<code>250-SIZE 52428800</code><br />
<code>250-PIPELINING</code><br />
<code>250-AUTH PLAIN LOGIN</code><br />
<code>250-STARTTLS</code><br />
<code>250 HELP</code></span><span lang="EN"> </span></strong></p>
<p><span lang="EN">As you see, it recognized you and greeted you back.<br />
If you want to talk more with the chatty server, just type: </span></p>
<p><strong><code><span style="font-size: 10pt" lang="EN">HELP</span></code><span style="font-size: 11pt; font-family: 'Courier New'" lang="EN"><br />
<code>The output will be:</code><br />
<code>214-Commands supported:</code><br />
<code>214 AUTH STARTTLS HELO EHLO MAIL RCPT DATA NOOP QUIT RSET HELP</code></span><span lang="EN"> </span></strong></p>
<p><u><span lang="EN">A sample FTP connection</span></u><span lang="EN"> </span></p>
<p><span lang="EN">To connect to the ftp server residing at ftp.ezoshosting.com through telnet, simply enter this command: </span></p>
<p><strong><em><code><span style="font-size: 10pt" lang="EN">telnet www.ezoshosting.com 21</span></code><span lang="EN"> </span></em></strong></p>
<p><span lang="EN">The screen output will be something like this: </span></p>
<p><strong><code><span style="font-size: 10pt" lang="EN">Trying 66.98.189.217...</span></code><span style="font-size: 11pt; font-family: 'Courier New'" lang="EN"><br />
<code>Connected to ftp.ezoshosting.com.</code><br />
<code>Escape character is '^]'.</code><br />
<code>220 ProFTPD 1.2.9 Server (ftp.ezoshosting.com) [66.98.189.217]</code></span><span lang="EN"> </span></strong></p>
<p><span lang="EN">To see a list of available commands / words: </span></p>
<p><code><span style="font-size: 10pt" lang="EN">HELP</span></code><span lang="EN"> </span></p>
<p><code><span style="font-size: 10pt" lang="EN">214-The following commands are recognized (* =&gt;'s unimplemented).</span></code><span style="font-size: 10pt; font-family: 'Courier New'" lang="EN"><br />
<code> USER    PASS    ACCT*   CWD     XCWD    CDUP    XCUP    SMNT*</code><br />
<code> QUIT    REIN*   PORT    PASV    EPRT    EPSV    TYPE    STRU</code><br />
<code> MODE    RETR    STOR    STOU    APPE    ALLO*   REST    RNFR</code><br />
<code> RNTO    ABOR    DELE    MDTM    RMD     XRMD    MKD     XMKD</code><br />
<code> PWD     XPWD    SIZE    LIST    NLST    SITE    SYST    STAT</code><br />
<code> HELP    NOOP    FEAT    OPTS    ADAT*   AUTH*   CCC*    CONF*</code><br />
<code> ENC*    MIC*    PBSZ*   PROT*</code><br />
<code>214 Direct comments to root@www.ezoshosting.com.</code></span><span lang="EN"> </span></p>
<p><strong><span lang="EN">The next generation</span></strong><span lang="EN"> </span></p>
<p><span lang="EN">Unfortunately, the current and still relatively easy way of handling IP addresses is doomed to die, as the number of IP addresses is limited to only about 4 billion addresses. This may sound like a lot, but it really isn&#8217;t. Have a look at how many pages are spidered by Google. As I write this article, google spidered 3,307,998,701 pages and that&#8217;s still only a small percentage of all estimated webpages. Experts believe that in 2005 we will run out of Ipv4 addresses. This is not a new development though and people are prepared. </span></p>
<p><span lang="EN">In the early 90s work on IPv6 has started. IPv6 will greatly enhance the number of available IP addresses and many people believe it will lead to each electronic device having it&#8217;s own IP address and we still won&#8217;t run out of IP addresses. </span></p>
<div class="addthis_toolbox addthis_default_style " addthis:url='http://www.networkingreviews.com/2008/02/28/the-base-of-tcpip-networking/' addthis:title='The Base of TCP/IP Networking '  ><a class="addthis_button_facebook_like" fb:like:layout="button_count"></a><a class="addthis_button_tweet"></a><a class="addthis_button_google_plusone" g:plusone:size="medium"></a><a class="addthis_counter addthis_pill_style"></a></div>]]></content:encoded>
			<wfw:commentRss>http://www.networkingreviews.com/2008/02/28/the-base-of-tcpip-networking/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

