FOSS Network Infrastructure and Security/Network Concepts and Architectures: Difference between revisions
wikademia>Stine loft |
wikademia>Eme m moved Alpha:FOSS Network Infrastructure and Security/Network Concepts and Architectures to FOSS Network Infrastructure and Security/Network Concepts and Architectures |
||
| (12 intermediate revisions by 4 users not shown) | |||
| Line 24: | Line 24: | ||
A hub or a switch is used as the central exchange point in a Star topology. All computers are connected to the hub in a star-like configuration of wires going in all directions from the hub. A '''Star topology''' is easier to maintain and to expand. | A hub or a switch is used as the central exchange point in a Star topology. All computers are connected to the hub in a star-like configuration of wires going in all directions from the hub. A '''Star topology''' is easier to maintain and to expand. | ||
{| style="border:solid 1px;" | |||
|[[Image:StarTopologyNetwork.jpg|600px]] | |||
|} | |||
== LAN Architecture == | == LAN Architecture == | ||
| Line 50: | Line 55: | ||
| Application Layer | | Application Layer | ||
|- | |- | ||
| | | rowspan=2 | | ||
| Transmission Control Protocol / User Datagram protocol | |||
| Transmission | | Transport Layer | ||
| | |||
|- | |- | ||
| | | Internet Protocol | ||
| Network Layer | | Network Layer | ||
|- | |- | ||
| Hardware Layer | | rowspan=2 | Hardware Layer | ||
| Network Interface Card Drivers | |||
| Interface | | Software/Hardware Layer | ||
| | |||
|- | |- | ||
| Card Layer | | Network Interface Card Layer | ||
| | | Electronic Layer | ||
|} | |} | ||
=== NIC Driver === | |||
An NIC driver provides a layer between the hardware and the software in any network. All network card manufacturers provide NIC drivers, which sometimes also come with the operating system. | |||
=== Network Protocols === | |||
Network protocols provide a way for diverse computer hardware to communicate with each other in a standard way. These protocols follow set rules unique to themselves. Common network protocols are IP (commonly referred to as the Transmission Control Protocol/Internet Protocol or TCP/IP) and NetBEUI (NetBIOS Extended User Interface). Other protocols had been developed and used in the past, but IP has replaced most of these. NetBEUI is developed by Microsoft and is native to the Windows environment. IP is the Internet Protocol and is the most popular protocol today. | |||
=== TCP/IP === | |||
TCP/IP are the basic protocols of the Internet. There are other protocols in TCP/IP like User Datagram Protocol (UDP). IP is the network layer and provides the basis for the network through the IP addresses. The IP address of each computer must be unique. TCP and UDP are the transport layers and are responsible for transport of network data packets. | |||
IP addresses follow the format nnn.nnn.nnn.nnn (where nnn is less than 255). A network mask separates | |||
the network address and the host address. | |||
For internal network use, the IP range defined in Request For Comments (RFC) <ref>RFC stands for Request for Comments, which is the series of documentation for Internet Standards. RFC 1918 means RFC number 1918, which defines private use IP addresses. RFCs can be downloaded from http://www.faqs.org/rfcs/. We will refer to many RFCs for further reference throughout the e-primer.</ref> 19184<ref>RFC 1918. ftp://ftp.rfc-editor.org/in-notes/rfc1918.txt</ref> should be used. These are 192.168.0.0 to 192.168.255.255, 172.16.0.0 to 172.31.255.255 and 10.0.0.0 to 10.255.255.255 | |||
== Components of a Network == | |||
=== Network Operating System === | |||
A Network Operating System (NOS) is a network capable operating system that handles network resources | |||
and provides services like file and printer sharing. It is also capable of being an application server. | |||
=== Users and Groups === | |||
Any NOS provides some form of security to its resources and services, the simplest being the user name & password pair. All users on the network are given a unique user name and they are also given a secret password. Only after verifying that a proper user name and password have been supplied does the NOS provide access to the designated network services. | |||
A group is a collection of users in any network. A group is created to give similar rights to a group of users. Groups make administration and management easier. | |||
=== Rights === | |||
Not all resources in a network may be available to everyone. It is necessary to shield some parts of the network from unauthorized use. So, all NOS provide rights to its users and groups. Users and groups are given only the required rights, while the more powerful rights are limited to the administrators. | |||
=== Super User or Administrator === | |||
In most NOS, there is a super user or administrator who has absolute rights in the network system. In the UNIX and GNU/Linux environments, ‘root’ is the super user. An administrator is the supreme user in a Windows network. In NetWare networks, supervisors are super, meaning such users are capable of doing anything that the NOS permits. These accounts should be used with care. | |||
== Monitoring Network Performance == | |||
When users start complaining that the network is too slow, we know that there are problems in the | |||
network. Network performance must be monitored to find where the fault lies. It may lie in the network hardware or software. | |||
Inferior grade cables and loose cable connections cause 80 percent of network problems and performance issues. High quality and prescribed cables and connectors should always be used. Another cause of problems may be the server hardware. Servers require more Random Access Memory (RAM). Some | |||
network performance problems call for the replacement of an older switch. | |||
Unnecessary services running on the server should be stopped to get the maximum performance from | |||
the server. Every NOS provides some utility to monitor network performance, as well as server | |||
performance. | |||
== Troubleshooting the Network == | |||
The first step is to check the cables. After that, check the power connections to the network switch or resources on the network. If the problem is not solved, check the different services running on the server. | |||
== Role of FOSS in Networking == | |||
The Internet is the biggest example of the successful implementation of free and open source tools and software. It is the largest network in the world and its basis is the IP protocol. While it is true that the Internet has helped in the growth of FOSS in general, FOSS has also made the Internet a much more reliable network. Detailed information about the Internet Engineering Task Force (IETF), the protocol standards body of the Internet, and its implications as a FOSS reference implementation can be found in RFC 1718. | |||
== Limitations to the Use of FOSS == | |||
Yes, there are limitations. Most FOSS is produced in conformance to open standards and processes. There are proprietary software and processes that may not have a FOSS equivalent. Sometimes, it may also be necessary to use proprietary software to access certain types of hardware. Another limitation may be the rapid pace of development of FOSS. To an average user, this may be confusing but for service providers this is definitely an advantage. | |||
== Footnotes == | |||
<references /> | |||
[[Category:FOSS Network Infrastructure and Security]] | [[Category:FOSS Network Infrastructure and Security]] | ||
{{alphabetical|F}} | |||