Networking Configuration
---
- Networking Configuration
This article details the networking configuration necessary for a robust and secure MediaWiki 1.40 installation. Proper networking is critical for performance, security, and accessibility. This guide is aimed at system administrators and those responsible for maintaining the MediaWiki server environment. It assumes a basic understanding of networking concepts such as TCP/IP, DNS, and firewalls. Refer to Manual:Configuration for general configuration information.
Overview
A well-configured network allows MediaWiki to efficiently serve content to users, connect to external databases (if applicable), and communicate with other services like caching servers (e.g., Memcached). Security considerations are paramount, requiring careful firewall rules and potentially the use of a reverse proxy like Apache or Nginx. The following sections detail key networking components and configuration options.
Network Interface Configuration
The primary network interface of your server is the gateway for all MediaWiki traffic. Static IP addresses are *strongly* recommended for production environments. The following table outlines common settings.
| Parameter | Value | Description |
|---|---|---|
| Interface Name | eth0 (example) | The name of the network interface. May vary (e.g., enp0s3). |
| IP Address | 192.168.1.100 (example) | The static IP address assigned to the server. |
| Netmask | 255.255.255.0 (example) | The network mask defining the network size. |
| Gateway | 192.168.1.1 (example) | The IP address of the default gateway. |
| DNS Servers | 8.8.8.8, 8.8.4.4 (example) | The IP addresses of the DNS servers. Consider using your ISP's DNS servers or public options like Google's. |
Configuration typically involves editing network configuration files specific to your operating system. For example, on Debian/Ubuntu, you'd modify `/etc/network/interfaces`. Consult your operating system's documentation for specific instructions. After making changes, restart the networking service. Verify connectivity using `ping` to the gateway and a public DNS server. See Networking Basics for more information.
DNS Configuration
Properly configured DNS is crucial for users to access your MediaWiki site. You'll need to create an A record pointing your domain name (e.g., `wiki.example.com`) to the static IP address of your server.
| Record Type | Name | Value | TTL |
|---|---|---|---|
| A | wiki.example.com | 192.168.1.100 (example) | 3600 |
| MX | example.com | mail.example.com | 3600 |
Consider using a Content Delivery Network (CDN) for improved performance, especially for geographically dispersed users. A CDN caches static content closer to users, reducing latency. See Setting up a CDN for more details. Also, ensure that reverse DNS (PTR records) are configured correctly, especially if you plan to use email features within MediaWiki.
Firewall Configuration
A firewall is essential for protecting your MediaWiki server from unauthorized access. Configure your firewall to allow only necessary traffic. The following table lists common ports that need to be opened.
| Port | Protocol | Description |
|---|---|---|
| 80 | TCP | HTTP (for non-SSL access - *not recommended*). |
| 443 | TCP | HTTPS (for secure SSL/TLS access - *strongly recommended*). |
| 22 | TCP | SSH (for remote administration - restrict access to trusted IPs). |
| 3306 | TCP | MySQL/MariaDB (if the database server is on a separate machine). Restrict access to the MediaWiki server. |
| 11211 | TCP/UDP | Memcached (if using Memcached caching). Restrict access to the MediaWiki server. |
Use a firewall management tool like `iptables` (Linux) or the Windows Firewall. Be sure to regularly review and update your firewall rules. Consider using a Web Application Firewall (WAF) for advanced protection against common web attacks. See Security Best Practices for more information. Ensure that your firewall logs are monitored for suspicious activity.
Load Balancing and High Availability
For high-traffic sites, consider using a load balancer to distribute traffic across multiple MediaWiki servers. This improves performance and provides redundancy in case of server failure. Load balancing can be implemented using hardware load balancers or software solutions like HAProxy or Nginx. Implementing a clustered database solution (e.g., MySQL replication) is also crucial for high availability. Refer to Setting up a Load Balancer for guidance.
Important Considerations
- **SSL/TLS:** Always use HTTPS to encrypt traffic between users and your MediaWiki server. Obtain an SSL/TLS certificate from a trusted Certificate Authority (CA). Let's Encrypt provides free SSL/TLS certificates.
- **Reverse Proxy:** A reverse proxy (e.g., Apache, Nginx) can improve security, performance, and scalability. It can handle SSL/TLS termination, caching, and load balancing.
- **Monitoring:** Implement network monitoring tools to track server performance, bandwidth usage, and potential security threats.
- **Regular Updates:** Keep your operating system, web server, database server, and MediaWiki software up to date with the latest security patches.
Manual:Configuration Manual:Database setup Manual:Cache configuration Manual:Using a reverse proxy Help:Networking basics Manual:Setting up a CDN Manual:Security best practices Manual:Setting up a load balancer Extension:VisualEditor Help:Installing MediaWiki Manual:Upgrading MediaWiki Help:Configuration Form Manual:Command-line tools Manual:Maintenance tasks Manual:API Special:Version Help:Contents Manual:FAQ
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 configuration
Need Assistance?
- Telegram: @powervps Servers at a discounted price
⚠️ *Note: All benchmark scores are approximate and may vary based on configuration. Server availability subject to stock.* ⚠️