Networking Fundamentals
# Networking Fundamentals
This article provides a foundational understanding of networking concepts essential for setting up and maintaining a MediaWiki installation. It's geared towards newcomers to server administration and aims to clarify the core components involved in server communication. Understanding these concepts is crucial for troubleshooting connectivity issues, optimizing performance, and ensuring the security of your wiki.
What is Networking?
At its core, networking is the practice of connecting computers together to share resources. In the context of a MediaWiki server, this means enabling communication between the server itself, client computers (browsers accessing the wiki), and potentially other servers like database servers. This communication relies on a set of rules and standards known as *network protocols*.
Core Networking Components
Several key components work together to facilitate network communication. These include:
- Network Interface Card (NIC): The hardware that allows a server to connect to a network.
- IP Address: A unique numerical label assigned to each device on a network.
- Subnet Mask: Defines the network portion of an IP address.
- Default Gateway: The IP address of the router that allows the server to communicate with networks outside of its local network.
- DNS Server: Translates domain names (like `www.mediawiki.org`) into IP addresses.
- Firewall: A security system that controls incoming and outgoing network traffic.
- TCP (Transmission Control Protocol): Provides reliable, connection-oriented communication. Used for web traffic (HTTP/HTTPS). See TCP/IP model for more details.
- UDP (User Datagram Protocol): Provides faster, connectionless communication. Used for DNS lookups and streaming media.
- HTTP (Hypertext Transfer Protocol): The foundation of data communication for the World Wide Web. HTTP requests are critical for wiki access.
- HTTPS (HTTP Secure): A secure version of HTTP, using encryption to protect data. SSL certificates are required.
- DNS (Domain Name System): Translates domain names to IP addresses. DNS records are essential for wiki accessibility.
- SSH (Secure Shell): Provides secure remote access to the server. SSH keys are recommended for authentication.
- Cannot access the wiki from a browser: Check the server's IP address, DNS configuration, and firewall rules. Use `ping` and `traceroute` to diagnose connectivity issues. See Network troubleshooting.
- Slow wiki performance: Investigate network latency, bandwidth limitations, and server resource utilization.
- Database connection errors: Verify the network connectivity between the MediaWiki server and the database server. Check Database configuration for details.
- DNS resolution failures: Confirm the DNS server settings on the server and client computers.
- System administration
- Server security
- MediaWiki installation
- Load balancing
- Virtual hosting
- Web server configuration
- Telegram: @powervps Servers at a discounted price
IP Addressing and Subnetting
IP addresses are fundamental to networking. There are two main versions: IPv4 and IPv6. IPv4 addresses are 32-bit numerical addresses, typically represented in dotted decimal notation (e.g., 192.168.1.1). IPv6 addresses are 128-bit hexadecimal addresses, which offer a significantly larger address space.
Subnetting divides a network into smaller, more manageable sections. This improves network performance and security. The subnet mask determines the size of these subnets.
Here's a table illustrating common private IP address ranges:
| Network Range | Subnet Mask | Use Case |
|---|---|---|
| 10.0.0.0 - 10.255.255.255 | 255.0.0.0 | Large organizations |
| 172.16.0.0 - 172.31.255.255 | 255.255.0.0 | Medium-sized organizations |
| 192.168.0.0 - 192.168.255.255 | 255.255.255.0 | Home and small office networks |
Common Network Protocols
Several protocols govern how data is transmitted over a network. Important protocols for a MediaWiki server include:
Network Configuration Examples
The specific network configuration will vary depending on your environment. Here's a table showing a typical server configuration:
| Configuration Item | Example Value |
|---|---|
| IP Address | 192.168.1.100 |
| Subnet Mask | 255.255.255.0 |
| Default Gateway | 192.168.1.1 |
| Preferred DNS Server | 8.8.8.8 (Google Public DNS) |
| Alternate DNS Server | 8.8.4.4 (Google Public DNS) |
| Hostname | wiki.example.com |
Firewall Configuration
A firewall is essential for protecting your MediaWiki server from unauthorized access. Common firewall software includes `iptables` (Linux) and Windows Firewall. You need to configure the firewall to allow incoming traffic on ports 80 (HTTP) and 443 (HTTPS). Consider also allowing port 22 (SSH) for remote administration, but restrict access to trusted IP addresses.
Here's a simplified example of firewall rules (conceptual):
| Port | Protocol | Action | Source |
|---|---|---|---|
| 80 | TCP | ALLOW | Any |
| 443 | TCP | ALLOW | Any |
| 22 | TCP | ALLOW | 192.168.1.0/24 (Trusted Network) |
| All other | Any | DENY | Any |
Troubleshooting Common Network Issues
Further Reading
Intel-Based Server Configurations
| Configuration | Specifications | Benchmark |
|---|---|---|
| Core i7-6700K/7700 Server | 64 GB DDR4, NVMe SSD 2 x 512 GB | CPU Benchmark: 8046 |
| Core i7-8700 Server | 64 GB DDR4, NVMe SSD 2x1 TB | CPU Benchmark: 13124 |
| Core i9-9900K Server | 128 GB DDR4, NVMe SSD 2 x 1 TB | CPU Benchmark: 49969 |
| Core i9-13900 Server (64GB) | 64 GB RAM, 2x2 TB NVMe SSD | |
| Core i9-13900 Server (128GB) | 128 GB RAM, 2x2 TB NVMe SSD | |
| Core i5-13500 Server (64GB) | 64 GB RAM, 2x500 GB NVMe SSD | |
| Core i5-13500 Server (128GB) | 128 GB RAM, 2x500 GB NVMe SSD | |
| Core i5-13500 Workstation | 64 GB DDR5 RAM, 2 NVMe SSD, NVIDIA RTX 4000 |
AMD-Based Server Configurations
| Configuration | Specifications | Benchmark |
|---|---|---|
| Ryzen 5 3600 Server | 64 GB RAM, 2x480 GB NVMe | CPU Benchmark: 17849 |
| Ryzen 7 7700 Server | 64 GB DDR5 RAM, 2x1 TB NVMe | CPU Benchmark: 35224 |
| Ryzen 9 5950X Server | 128 GB RAM, 2x4 TB NVMe | CPU Benchmark: 46045 |
| Ryzen 9 7950X Server | 128 GB DDR5 ECC, 2x2 TB NVMe | CPU Benchmark: 63561 |
| EPYC 7502P Server (128GB/1TB) | 128 GB RAM, 1 TB NVMe | CPU Benchmark: 48021 |
| EPYC 7502P Server (128GB/2TB) | 128 GB RAM, 2 TB NVMe | CPU Benchmark: 48021 |
| EPYC 7502P Server (128GB/4TB) | 128 GB RAM, 2x2 TB NVMe | CPU Benchmark: 48021 |
| EPYC 7502P Server (256GB/1TB) | 256 GB RAM, 1 TB NVMe | CPU Benchmark: 48021 |
| EPYC 7502P Server (256GB/4TB) | 256 GB RAM, 2x2 TB NVMe | CPU Benchmark: 48021 |
| EPYC 9454P Server | 256 GB RAM, 2x2 TB NVMe |
Order Your Dedicated Server
Configure and order your ideal server configurationNeed Assistance?
⚠️ *Note: All benchmark scores are approximate and may vary based on configuration. Server availability subject to stock.* ⚠️