English:Computer Network Fundamentals
Computer Network Fundamentals
Introduction
Computer networks are part of almost every modern workplace. Offices, workshops, factories, warehouses, schools, hospitals, shops, and service companies depend on networks to connect computers, mobile devices, printers, servers, machines, sensors, and cloud services. As an apprentice, trainee, or vocational student, you need more than definitions: you need to understand what happens when a device is connected, how data reaches its destination, how common faults can be located, and how a network can be operated safely and professionally.
A computer network is a group of devices that exchange data through communication links and agreed rules called protocols. Networks can be small, such as two computers connected by one cable, or extremely large, such as the Internet. In professional practice, you will often work with a LAN, a WLAN, switches, routers, structured cabling, IP addresses, network services, and security controls.
The connector above is typical of copper Ethernet patch cabling. When you connect a workstation to a switch, the physical connection is only the first step. The device also needs appropriate link settings, an IP configuration, a path to other networks, and usually services such as DNS.
This aiMOOC combines technical explanations with workplace-oriented examples, troubleshooting methods, practical tasks, and interactive exercises. You should use a safe training network, simulation environment, or equipment that you are authorized to configure. Do not change production network settings without permission and a documented change procedure.
Learning Goals
After completing this aiMOOC, you should be able to explain the purpose of a computer network, distinguish common network types and topologies, identify important networking devices and media, relate the OSI and TCP/IP models to real traffic, interpret basic IPv4 addressing and subnetting, explain switching and routing, describe common network services, apply basic network security practices, and troubleshoot typical connectivity problems in a structured way.
You should also be able to document a small network, communicate technical findings clearly, select appropriate diagnostic tools, and justify your troubleshooting decisions in a vocational context.
What a Network Does
A network enables devices to share information and resources. Typical workplace uses include file access, printing, database access, web applications, voice and video communication, industrial control, inventory systems, remote support, backups, and Internet access. Networks make cooperation efficient, but they also create dependencies: if a switch, cable, address configuration, authentication service, or Internet connection fails, many users may be affected.
A useful way to think about networking is to follow a message from one application to another. An application creates data. Networking software adds information that helps transport and route the data. A network interface sends signals over copper, fiber, or radio. Intermediate devices forward the traffic. At the destination, the information is processed in the reverse direction until it reaches the receiving application.
Clients, Servers, and Peers
A client requests a service. A server provides a service. A workstation opening a company website is acting as a client, while the web server is providing the requested content. A device can act as both a client and a server in different situations.
In a client-server network, services are commonly centralized. Centralization can simplify management, backup, authentication, and security. In a peer-to-peer arrangement, devices may exchange resources directly without a permanently dedicated server. Peer-to-peer communication can be useful for small or specialized applications, but centralized management is often preferred in business environments.
Network Scope
A PAN covers a very small personal area, for example a phone connected to a headset. A LAN usually connects devices within a room, building, workshop, or site. A WLAN provides local connectivity using radio rather than only fixed cables. A MAN spans a larger urban area, while a WAN links networks across larger geographic distances. The Internet is a global system of interconnected networks.
In vocational practice, the exact label is less important than understanding the operational boundaries: who owns the infrastructure, which devices share a local broadcast domain, where routing occurs, what bandwidth is available, and which security rules apply.
Network Topologies
A network topology describes how devices and links are arranged physically or logically. Common topologies include star, bus, ring, tree, and mesh. Modern Ethernet LANs commonly use a physical star or extended-star arrangement, with end devices connected to switches.
In a star topology, each endpoint has a separate connection to a central device such as a switch. A single damaged endpoint cable usually affects only one device, but the failure of the central switch can affect all devices connected to it. In a mesh topology, multiple paths can improve resilience but require more links and more complex control. A topology diagram is therefore useful when evaluating fault tolerance, cost, cable routes, and troubleshooting options.
When reading a network diagram, distinguish between a physical topology and a logical topology. The physical topology shows equipment and links. The logical topology shows how traffic is grouped and flows. For example, VLANs can create several logical networks on the same physical switches.
Transmission Media and Physical Connections
The physical layer carries signals. Depending on the environment, a network may use twisted-pair copper cable, optical fiber, radio, or a combination of these media. Media selection depends on distance, required data rate, electromagnetic conditions, installation standards, cost, mobility, and security requirements.
Twisted-Pair Ethernet
Copper Ethernet commonly uses balanced twisted-pair cabling. Twisting helps reduce electromagnetic interference and crosstalk. Patch cables connect devices such as computers, switches, access points, and patch panels. Permanent building cabling is normally installed and tested as part of a structured cabling system.
The plug commonly used with twisted-pair Ethernet is often called an RJ45 connector in everyday networking language, although the exact standardized connector terminology is more specific. In workplace practice, what matters is that you recognize the eight-position modular connector, preserve correct pair arrangement, use appropriate cable categories and components, and verify the link with suitable testing equipment.
A network link can fail even if a cable looks undamaged. Broken conductors, poorly terminated plugs, excessive bending, damaged sockets, incorrect patching, or electromagnetic problems can create intermittent or complete failure. Visual inspection is useful, but a cable tester and switch-port status information provide stronger evidence.
Fiber-Optic Cabling
Optical fiber carries light rather than electrical signals. Fiber is useful for longer distances, high bandwidth, and environments where electrical interference is a concern. Common network installations use multimode or single-mode fiber depending on the required reach and optical system.
Fiber connectors and transceivers must match the installed system. Contamination on connector end faces can significantly affect optical performance. Never look into the end of an active fiber. Follow the workplace's laser-safety, cleaning, handling, and testing procedures.
Wireless Transmission
Wireless LANs use radio communication, commonly based on standards from the IEEE 802.11 family. Wireless connectivity adds mobility, but performance depends on signal strength, interference, channel use, client capabilities, access-point placement, obstacles, and security configuration.
A device marketed as a "wireless router" often combines several functions in one enclosure, such as routing, switching, wireless access, DHCP service, NAT, and firewall functions. In professional networks, these functions may be provided by separate devices or centrally managed systems.
Network Devices
Network devices perform different forwarding and service functions. Understanding those functions helps you choose the right troubleshooting point.
Network Interface
A network interface controller, or NIC, connects a host to a network medium. An Ethernet NIC has a link-layer address called a MAC address. A host may have several interfaces, for example one wired Ethernet interface, one Wi-Fi interface, and virtual interfaces created by software.
When troubleshooting, verify that the intended interface is enabled, has a physical or wireless link, and has the expected configuration. A valid IP address on the wrong interface does not necessarily provide connectivity through the required path.
Hub
An Ethernet hub repeats incoming signals to its other ports. Hubs were used in older shared Ethernet networks, but switches have largely replaced them. A hub does not learn destination MAC addresses in the way an Ethernet switch does.
Switch
A switch connects devices within a LAN and forwards Ethernet frames. A switch learns source MAC addresses and associates them with switch ports. It can then forward a unicast frame toward the port where the destination MAC address was learned. If the destination is not known, the switch may flood the frame within the relevant VLAN.
Managed switches can provide features such as VLANs, trunk links, link aggregation, monitoring, security controls, and remote administration.
Router
A router forwards IP packets between different IP networks. Routers use routing tables to choose paths. The router that a host uses to reach destinations outside its local subnet is commonly called the default gateway.
A router does not simply "make the Internet work." It makes forwarding decisions between networks. Internet access may additionally require an ISP connection, public addressing, NAT, firewall policy, DNS, and other services.
Wireless Access Point
A wireless access point connects wireless clients to a network. In business networks, access points may be managed centrally. Placement, channel planning, transmit power, authentication, and security settings influence service quality and reliability.
Firewall
A firewall applies security policy to network traffic. Depending on its design, it may filter traffic by addresses, protocols, ports, connection state, application characteristics, identity, or other attributes. A firewall is not a replacement for secure configuration, updates, access control, monitoring, and user awareness; it is one control in a layered security strategy.
Layered Network Models
Layered models divide complex communication into manageable functions. They help technicians describe problems precisely. Instead of saying "the network is broken," you can ask whether the fault is physical, local Ethernet, IP routing, transport, name resolution, or application-specific.
OSI Model
The OSI model is a conceptual seven-layer model: Physical, Data Link, Network, Transport, Session, Presentation, and Application. The model is useful for learning and troubleshooting even though real protocol implementations do not always match its boundaries perfectly.
At the Physical layer, you consider signals, connectors, cable, radio, and link state. At the Data Link layer, you consider frames, MAC addresses, switching, and VLANs. At the Network layer, you consider IP addresses and routing. At the Transport layer, you consider protocols such as TCP and UDP. Higher layers support application communication and data representation.
TCP/IP Model
The TCP/IP model describes the protocol architecture used by the Internet. A common four-layer view contains Link, Internet, Transport, and Application layers.
Do not treat the OSI and TCP/IP models as competing descriptions where only one can be correct. For training, the OSI model provides fine-grained terminology, while TCP/IP describes the protocol suite that actually underlies Internet communication.
Encapsulation
As application data moves down a protocol stack, protocol information is added. This process is called encapsulation. At the transport layer, data may be carried in a TCP segment or UDP datagram. At the Internet layer, it is carried in an IP packet. On Ethernet, the IP packet is carried inside an Ethernet frame.
At the receiver, the process is reversed. Understanding encapsulation helps you interpret packet captures because one captured frame can contain Ethernet information, IP information, transport-layer information, and application data.
Ethernet, MAC Addresses, and Switching
Ethernet is a family of technologies widely used in wired LANs. Ethernet frames contain source and destination MAC addresses. A MAC address identifies an interface at the data-link level within the relevant LAN context.
A switch learns by observing the source MAC address of frames arriving on its ports. It records which MAC addresses are reachable through which ports. When a frame arrives, the switch examines the destination MAC address and forwards the frame according to its forwarding table and VLAN configuration.
Broadcast frames are delivered to all relevant ports within the same broadcast domain. Routers normally separate broadcast domains. VLANs can divide one physical switching infrastructure into multiple logical Layer 2 networks.
Unicast, Broadcast, and Multicast
Unicast communication targets one destination. Broadcast communication targets all hosts in a local broadcast domain. Multicast communication targets a subscribed group of receivers. These traffic patterns have different effects on switching, routing, efficiency, and security.
A technician should not assume that "broadcast" means the packet travels across the entire Internet. Layer 2 broadcasts are normally confined to the local broadcast domain and are not forwarded by routers as ordinary routed traffic.
Internet Protocol and Addressing
The Internet Protocol provides logical addressing and packet delivery across interconnected networks. Two versions are widely relevant: IPv4 and IPv6.
IPv4 Basics
An IPv4 address is 32 bits long and is usually written as four decimal octets, for example 192.168.10.25. An IPv4 interface configuration normally includes an IP address and subnet mask or prefix length. A host may also be configured with a default gateway and DNS server addresses.
Private IPv4 ranges commonly used inside organizations include 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16. These addresses are not globally routed as ordinary public Internet addresses. Organizations commonly use private addressing together with routing and, where required, network address translation.
The IPv4 packet header contains information used to deliver the packet, including source and destination addresses and a field identifying the upper-layer protocol.
Subnet Masks and Prefix Lengths
A subnet divides an IP address range into a network part and a host part. In CIDR notation, a prefix such as /24 means that the first 24 bits represent the network prefix.
For example, the host 192.168.20.37/24 belongs to the network 192.168.20.0/24. The usual broadcast address for that subnet is 192.168.20.255, and the commonly usable host range is 192.168.20.1 through 192.168.20.254.
Subnetting is important because it organizes address space, defines local network boundaries, reduces unnecessary broadcast scope, supports security design, and helps route traffic efficiently.
When calculating subnets, work systematically. Identify the prefix length, determine which bits belong to the network, find the network address, identify the broadcast address for IPv4 when applicable, and determine the usable host range according to the design. In real workplace networks, always check the documented addressing plan instead of inventing an address that merely "looks suitable."
IPv6 Basics
An IPv6 address is 128 bits long and is usually written in hexadecimal groups separated by colons. IPv6 provides a much larger address space than IPv4. IPv6 also changes several protocol behaviors, so it should not be treated as simply "IPv4 with longer addresses."
A vocational technician should recognize IPv6 addressing, link-local addresses, prefix notation, default routes, and the fact that modern systems often operate with both IPv4 and IPv6. Troubleshooting must therefore consider which protocol version an application is actually using.
ARP, Gateways, and Routing
A host first decides whether a destination IP address is local or remote according to its own IP address and prefix. If the destination is local, the host needs a data-link address for that destination. In traditional IPv4 Ethernet networks, the Address Resolution Protocol, or ARP, maps an IPv4 address to a MAC address.
If the destination is outside the local subnet, the host normally sends the frame toward its default gateway. The destination IP address in the IP packet remains the remote destination, while the destination MAC address of the local Ethernet frame is normally the MAC address of the next-hop router interface.
This distinction is essential: switches forward frames within a Layer 2 network, while routers forward packets between IP networks.
Routing Tables
Hosts and routers use routing tables. A routing-table entry describes a destination prefix and how to reach it, for example through a directly connected interface or a next-hop router. A default route is used when no more specific route matches.
When several routes exist, routers use routing rules and metrics to select an appropriate path. Enterprise routing can become complex, but the fundamental question remains: "Which next hop or interface should receive this packet for this destination network?"
Network Address Translation
NAT changes address information as traffic passes through a translating device. In many IPv4 Internet-access designs, NAT enables many private internal hosts to communicate through one or a smaller number of public addresses.
Do not confuse NAT with routing or firewalling. A device may perform all three functions, but they are conceptually different. Routing chooses where packets go, NAT modifies address information, and firewalling applies security policy.
Core Network Services
A network can have working cables, switches, and routes while users still report that "the Internet is down." Often the missing piece is a service such as DHCP or DNS.
DHCP
The Dynamic Host Configuration Protocol, or DHCP, can automatically provide network configuration to clients. Typical information includes an IP address, subnet mask or prefix information, default gateway, DNS server addresses, and a lease duration.
If DHCP fails, a client may have no usable address or may assign itself a link-local fallback address, depending on the operating system and protocol. A technician should check whether the client received the expected lease, whether the correct DHCP scope is active, whether the client and server can communicate, and whether relay configuration is required across routed boundaries.
DNS
The Domain Name System, or DNS, maps names to information such as IP addresses. Users usually prefer names such as "intranet.example" instead of memorizing addresses.
A common troubleshooting distinction is this: if you can reach a service by IP address but not by hostname, basic IP connectivity may be working while name resolution is failing. This is not a universal rule, but it is a useful diagnostic clue.
Time, Authentication, and Directory Services
Business networks often depend on other infrastructure services. Accurate time synchronization supports logging, authentication, certificates, and event correlation. Directory and identity services centralize accounts, groups, permissions, and authentication. If these services fail, applications can appear unreachable even when basic network connectivity is available.
Therefore, successful troubleshooting requires you to distinguish network transport from the application and identity services that depend on it.
Transport and Application Protocols
At the transport layer, two important protocols are TCP and UDP.
TCP is connection-oriented and provides reliable, ordered delivery through mechanisms such as acknowledgements, sequence numbers, retransmission, and flow control. UDP has lower protocol overhead and does not provide TCP's connection-oriented reliability mechanisms. Applications choose transport behavior according to their requirements.
A port number helps identify an application endpoint on a host. Common examples include TCP port 443 for HTTPS and UDP or TCP port 53 for many DNS operations. Port numbers are not physical switch ports; the same word "port" is used for different concepts.
Application-layer protocols include HTTP and HTTPS for web communication, DNS for name resolution, SMTP for sending email, SSH for secure remote administration, and many specialized protocols used in industrial, building, and business systems.
Virtual LANs
A VLAN creates a logical Layer 2 broadcast domain on switching infrastructure. VLANs can separate departments, device types, security zones, voice systems, management traffic, or other groups without requiring a separate physical switch for every group.
An access port normally carries traffic for one VLAN toward an endpoint. A trunk can carry traffic for multiple VLANs between network devices, commonly using IEEE 802.1Q tagging.
Devices in different VLANs need Layer 3 routing to communicate. The existence of VLANs does not automatically provide security; access-control policy, routing, firewall rules, authentication, and correct switch configuration still matter.
A common vocational troubleshooting problem is a device connected to the correct physical switch but assigned to the wrong VLAN. Link lights can be on, yet DHCP, gateway access, and application connectivity may fail because the logical network is wrong.
Wireless LAN Fundamentals
A wireless LAN uses access points and client radios. Service quality depends on both coverage and capacity. A strong signal does not guarantee high throughput if the radio channel is congested, interfered with, or shared by many active clients.
Wireless networks are identified by an SSID. Authentication and encryption protect access and traffic. In professional environments, use current security methods approved by the organization. Avoid obsolete or weak security settings merely because old devices support them.
When troubleshooting Wi-Fi, check whether the client can see the intended SSID, whether authentication succeeds, whether it receives the expected IP settings, whether signal quality is adequate, and whether the problem also occurs on wired connections. This helps determine whether the fault is radio-related, local network-related, or upstream.
Basic Network Security
Network security protects confidentiality, integrity, and availability. A secure network design uses several controls rather than relying on a single device.
Important practices include unique administrative credentials, least-privilege access, secure management protocols, current firmware and software, network segmentation, controlled firewall rules, protected wireless authentication, logging, backups of configurations, and physical protection of network equipment.
Do not connect unknown devices to a workplace network without authorization. Do not capture other users' traffic unless you have explicit permission and a legitimate training or operational purpose. Diagnostic tools are powerful and must be used ethically and according to policy.
Segmentation and Least Privilege
Segmentation limits which devices share the same network and which systems can communicate. VLANs, routers, firewalls, and access-control rules can support segmentation. A production machine, guest device, office workstation, and network-management interface may require different trust levels.
Least privilege means giving users, devices, and services only the access they need. This principle reduces the impact of mistakes, compromised accounts, and malicious activity.
Secure Management
Use encrypted management protocols such as HTTPS and SSH where appropriate. Restrict management access to trusted networks or administrators. Disable unused services, document changes, and protect backups of device configurations.
A configuration change can solve one problem while creating another. Professional practice therefore includes change planning, testing, rollback preparation, and clear documentation.
Network Troubleshooting
Good troubleshooting is a method, not a collection of random commands. Begin with the user's symptoms and define the scope. Ask what works, what does not work, when the problem started, what changed, and whether one device or many devices are affected.
A useful sequence is:
- Define the problem: Record symptoms, affected users, devices, locations, and time.
- Check the physical and wireless connection: Verify power, link state, cable, port, signal, and interface status.
- Check local configuration: Verify IP address, prefix, gateway, DNS settings, VLAN, and interface selection.
- Test progressively: Test the local stack, local gateway, nearby resources, remote IP connectivity, name resolution, and the application.
- Compare with a working reference: Compare configuration, switch port, VLAN, address assignment, and policy.
- Change one thing at a time: Record the result so that evidence is not lost.
- Verify and document: Confirm that the original service works and document the cause and solution.
Common Diagnostic Commands
On many systems, tools such as ipconfig, ip, ifconfig, ping, traceroute or tracert, nslookup, dig, arp, and routing-table commands can provide useful evidence. Exact syntax depends on the operating system.
ping can test IP reachability and round-trip response when ICMP traffic is permitted. A failed ping does not always prove that the destination is offline because firewalls or hosts may block ICMP.
traceroute or tracert can reveal intermediate routing hops, although devices may not always respond. nslookup and dig can help test DNS resolution. Interface commands show addresses and link state. Routing-table commands show which paths the host plans to use.
Use commands as tests tied to a hypothesis. Do not run a long list of commands without knowing what each result would tell you.
Packet Capture
A packet analyzer such as Wireshark can show actual network traffic. Packet capture is especially useful when you need evidence about ARP, DNS, TCP connection attempts, retransmissions, protocol errors, or application exchanges.
The screenshot illustrates a packet analyzer decoding protocol layers. Notice how one captured frame can be expanded into Ethernet, IP, transport, and application information. This connects the abstract layer models to real traffic.
Packet captures can contain sensitive information. Capture only on systems and networks where you are authorized to do so, limit the capture scope, protect the files, and follow organizational policy.
Workplace Documentation
Technical skill includes documentation. A clear network record helps colleagues maintain and troubleshoot systems safely.
A small network documentation set can include a topology diagram, device names, locations, interface labels, IP addresses, VLAN IDs, uplink connections, service dependencies, cable identifiers, wireless SSIDs, configuration backup locations, and change history.
Use consistent naming. Label both ends of important cables. Record why a configuration exists, not only what value was entered. During troubleshooting, document evidence, tests, results, changes, and final verification.
Example Workplace Scenario
Imagine a trainee reports: "My workstation has network link lights, but I cannot open the company intranet."
A structured investigation could proceed as follows. First, confirm whether other users are affected. Second, check the workstation's IP address, subnet prefix, default gateway, and DNS configuration. Third, test the local gateway. Fourth, test the intranet server by IP address if permitted. Fifth, test the intranet hostname. Sixth, compare the switch-port VLAN and DHCP lease with a working workstation.
If the workstation can reach the server by IP address but not by hostname, DNS becomes a strong area to investigate. If the workstation cannot even reach its local gateway, focus earlier in the path: interface, VLAN, addressing, cable, switch port, or local policy. Each test should narrow the fault domain.
Practical Design Principles
A good small business network is understandable, supportable, secure, and expandable. Technical choices should match actual requirements rather than fashion.
Use appropriate addressing and subnetting. Separate traffic where there is an operational or security reason. Provide redundant links or devices where downtime has significant consequences. Protect management interfaces. Keep firmware and configuration backups current. Monitor important services. Label cables and ports. Maintain diagrams that reflect reality.
For vocational work, the best design is not necessarily the most complex. A simpler design that meets requirements and can be maintained reliably is often better than unnecessary complexity.
Interactive Tasks
Quiz: Test Your Knowledge
Which device primarily forwards Ethernet frames according to learned MAC addresses? (Switch) (!Router) (!Modem) (!Printer)
What is the main purpose of a default gateway on a workstation? (Forward traffic toward remote networks) (!Assign a MAC address to the workstation) (!Convert fiber signals into copper signals) (!Create the workstation hostname)
Which protocol is normally used to map an IPv4 address to a MAC address on a local Ethernet network? (ARP) (!DNS) (!HTTP) (!SSH)
Which service commonly provides IP configuration automatically to clients? (DHCP) (!SMTP) (!FTP) (!NTP)
Which service translates hostnames into information such as IP addresses? (DNS) (!ARP) (!VLAN) (!Ethernet)
What does a slash 24 IPv4 prefix indicate? (The network prefix contains 24 bits) (!The network contains exactly 24 computers) (!The router has 24 interfaces) (!The cable carries 24 channels)
Which device normally separates IP broadcast domains and forwards packets between networks? (Router) (!Passive patch panel) (!Ethernet coupler) (!Keyboard)
Which statement about a VLAN is correct? (It creates a logical Layer 2 broadcast domain) (!It automatically encrypts all user traffic) (!It replaces all IP addressing) (!It is a type of fiber connector)
What is a good first step when troubleshooting a reported network fault? (Define the symptoms and scope) (!Replace every cable immediately) (!Reset all network devices) (!Disable every firewall rule)
Why should packet captures be handled carefully? (They may contain sensitive network information) (!They always damage switch hardware) (!They permanently change IP addresses) (!They disable wireless encryption)
Memory Game
| Switch | Forwards Ethernet frames inside a LAN using learned link-layer information |
| Router | Forwards IP packets between different networks |
| DHCP | Automatically supplies network configuration to clients |
| DNS | Resolves names to information such as IP addresses |
| VLAN | Creates a logical Layer 2 broadcast domain |
| Gateway | Provides a next hop toward destinations outside the local subnet |
Drag and Drop
| Match the correct terms. | Topic |
|---|---|
| Checks physical connectivity and link state | Physical layer |
| Forwards frames using MAC information | Ethernet switching |
| Chooses paths between IP networks | Routing |
| Provides automatic client addressing | DHCP |
| Converts names into address information | DNS |
...
Crossword Puzzle
| Ethernet | Which widely used LAN technology sends frames over wired network links? |
| Switch | Which device learns MAC addresses and forwards frames inside a LAN? |
| Router | Which device forwards IP packets between networks? |
| Subnet | What is an IP network segment defined by an address prefix called? |
| Gateway | What is the usual next-hop device for traffic leaving a local subnet? |
| Firewall | What security device or function applies traffic filtering policy? |
LearningApps
Cloze Text
Open-Ended Tasks
Easy
- Network Inventory: Inspect an authorized training network or classroom setup and create a one-page inventory of devices, cables, network interfaces, and visible port labels.
- Topology Sketch: Draw a clear physical topology of a small workplace network with at least one switch, one router, two client devices, and one shared service, then explain each connection.
- Connectivity Diary: Record the network settings of a training workstation and write a short explanation of what the IP address, prefix, gateway, and DNS values are used for.
- Cable Inspection: Examine several authorized network cables and connectors, photograph or sketch their visible features, and create a checklist for safe visual inspection before testing.
Standard
- Troubleshooting Interview: Interview a technician or trainer about a real connectivity fault and write a structured report describing symptoms, tests, evidence, root cause, solution, and verification.
- Packet Capture Investigation: In an authorized lab, capture a DNS lookup and identify the Ethernet, IP, transport, and DNS information visible in the packet analyzer, then explain how encapsulation appears in the capture.
- Subnet Planning Project: Design an IPv4 addressing plan for a small training company with separate office, workshop, and guest networks, justify the prefix sizes, and show the usable address ranges.
- Network Demonstration Video: Produce a three-to-five-minute video showing how a workstation reaches a remote network through a switch and default gateway, using your own diagram or lab simulation.
Advanced
- VLAN Lab: Build or simulate two VLANs on authorized training equipment, verify same-VLAN and inter-VLAN behavior, document the configuration, and explain why routing is required between the VLANs.
- Fault Injection Exercise: In a controlled lab, introduce one fault at a time such as an incorrect gateway, wrong VLAN, disconnected cable, or invalid DNS setting, then develop a decision tree that identifies each fault efficiently.
- Network Security Review: Assess a small authorized lab network for management access, segmentation, wireless security, unused services, update status, and documentation quality, then propose prioritized improvements.
- Workplace Network Improvement Proposal: Visit an authorized workshop, training center, or technical department, study its networking needs without collecting confidential data, and produce a professional proposal with topology, addressing, resilience, security, maintenance, and cost considerations.
Learning Assessment
- Layered Fault Analysis: Given a case where a workstation has link lights but cannot open a web application, create a test sequence that distinguishes physical, VLAN, IP, DNS, transport, and application faults, and justify the order.
- Addressing Decision: Compare two proposed IPv4 subnet plans for a growing small company and select the more suitable plan based on host capacity, segmentation, future growth, and manageability.
- Switching and Routing Explanation: Use one packet journey to explain when a switch uses MAC information and when a router uses IP information, including what changes at each routed hop.
- Service Dependency Analysis: Analyze a scenario where users can reach servers by IP address but not by hostname, identify likely causes, propose safe tests, and explain what evidence would confirm or reject each cause.
- VLAN Transfer Task: Design a solution for separating office, production, guest, and management devices while allowing only required communication between them, and explain which functions belong to switches, routers, and firewalls.
- Professional Troubleshooting Report: Produce a concise service report from a simulated network incident that includes user impact, initial symptoms, measurements, hypotheses, tests, corrective action, rollback consideration, final verification, and preventive recommendations.
Evidence of Learning
- Knowledge
- You can explain network scope, topology, media, devices, layered models, Ethernet switching, IP addressing, routing, DHCP, DNS, VLANs, wireless networking, and basic security principles in accurate technical language.
- Skills
- You can inspect links, read interface settings, interpret IP configuration, use appropriate diagnostic commands, calculate basic IPv4 subnets, follow a packet path, compare working and faulty systems, and use packet capture responsibly in an authorized lab.
- Products
- Your portfolio can contain a topology diagram, IP addressing plan, troubleshooting checklist, packet-capture analysis, VLAN lab record, security review, and professional incident report.
- Professional Practice
- You can work methodically, protect sensitive information, avoid unauthorized changes, record evidence, communicate clearly with users and colleagues, and verify service after a change.
- Transfer Achievement
- You can apply the same principles to unfamiliar equipment or software by identifying layers, interfaces, addresses, routes, services, policies, and evidence rather than relying only on memorized command sequences.
OERs on the Topic
The English Wikipedia article on computer networks provides a broad reference for network concepts, hardware, architecture, and services.
You can also continue learning through related English-language topics such as Ethernet, Internet Protocol, IPv4, IPv6, Network switch, router, Domain Name System, Dynamic Host Configuration Protocol, VLAN, Wi-Fi, Wireshark, and Network security.
Linked Learning Areas
The topic connects networking with Information technology, Computer science, Telecommunications, Cybersecurity, System administration, Electrical engineering, Industrial automation, Cloud computing, and vocational workplace practice. Understanding these links helps you transfer network knowledge to support, maintenance, production, administration, and technical service roles.
aiMOOC Projects
MOOCwiki · Deutsch
Nach dem Lernen ist vor dem Lernen
Entdecke direkt den nächsten Lernkurs. Weitere Inhalte erscheinen, wenn Du weiter nach unten scrollst.
Zur MOOCwiki-HauptseiteMediathek
Mediathek
Mediathek wird aus dem Wiki geladen ...
Keine passenden Inhalte gefunden. Bitte ändere Suche oder Filter.