Ir al contenido

Configurazione Manuale di WordPress e Database con Router Trinux

La chiave di questa configurazione è la maschera di rete /25 (o 255.255.255.128). Questa maschera divide la rete 172.26.0.0 in due blocchi:

0letture

Nome: Team Portelcore

Corso: CE Cybersecurity 25/26

La chiave di questa configurazione è la maschera di rete /25 (o 255.255.255.128). Questa maschera divide la rete 172.26.0.0 in due blocchi:

  1. Rete Web (Blocco 1): 172.26.0.0/25 (IP da .1 a .126)
  2. Rete DB (Blocco 2): 172.26.0.128/25 (IP da .129 a .254)

Il nostro piano è:

MacchinaIPMascheraGateway (Uscita)Rete
Ubuntu Web (WP)172.26.0.20/25172.26.0.1Rete Web (1)
Ubuntu DB (MySQL)172.26.0.150/25172.26.0.129Rete DB (2)
Trinux (Router)172.26.0.1 (eth0)/25-Connette alla Rete 1
Trinux (Router)172.26.0.129 (eth1)/25-Connette alla Rete 2

2. Ordine di Esecuzione (Molto Importante)

Sección titulada «2. Orden de Ejecución (Muy Importante)»

Dobbiamo seguire questo ordine. I server Ubuntu non potranno comunicare finché il router (Passaggio 3) non sarà funzionante.

  1. Passaggio 3: Configurare il Router Trinux
  2. Passaggio 4: Configurare l'Ubuntu DB
  3. Passaggio 5: Configurare l'Ubuntu Web (WP)

3. Passaggio 1: Configurazione del Router Trinux

Sección titulada «3. Paso 1: Configuración del Router Trinux»

Ci connetteremo alla macchina Trinux.

3.1. Configurare le Interfacce di Rete

Sección titulada «3.1. Configurar Interfaces de Red»

Assegneremo un IP a ogni porta del router. La maschera 255.255.255.128 è la stessa di /25.

# Pata conectada a la red del Servidor Web (Red 1)
# Esta será la puerta de enlace (gateway) para 172.26.0.20
ifconfig eth1 172.26.0.1 netmask 255.255.255.128 up
# Pata conectada a la red del Servidor BBDD (Red 2)
# Esta será la puerta de enlace (gateway) para 172.26.0.150
ifconfig eth0 172.26.0.129 netmask 255.255.255.128 up

Questo è il comando che trasforma Trinux in un router.

Ventana de terminal
echo "1" > /proc/sys/net/ipv4/ip_forward

3.3. Configurare IPTables (Permettere il traffico)

Sección titulada «3.3. Configurar IPTables (Permitir tráfico)»

Per impostazione predefinita, imposteremo le regole su DROP. Ci assicureremo che il traffico tra le nostre due reti interne sia consentito.

Ventana de terminal
# --- 2. REGLAS IPTABLES (NAT - Network Address Translation) ---
# Vaciamos reglas NAT por si acaso
iptables -t nat -F PREROUTING
iptables -t nat -F POSTROUTING
# REGLA NAT 1: MASQUERADE (SNAT)
# Permite que las dos redes internas (Web y BBDD) salgan a Internet
# "enmascaradas" bajo la IP pública de eth0.
iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
# REGLA NAT 2: PORT FORWARDING (DNAT) para HTTP (Port 80)
# Todo lo que entre por la pública (eth0) al puerto 80...
# ...se redirige a nuestro Servidor Web (172.26.0.20).
iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 80 -j DNAT --to-destination 172.26.0.20:80
# REGLA NAT 3: PORT FORWARDING (DNAT) para HTTPS (Port 443)
iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 443 -j DNAT --to-destination 172.26.0.20:443
# Ocultar la red BBDD detrás de la IP de la red Web.
iptables -t nat -A POSTROUTING -o eth1 -j MASQUERADE
# --- 3. REGLAS IPTABLES (FORWARD - Filtrado de Paquetes) ---
# Vaciamos reglas FORWARD
iptables -F FORWARD
# REGLA FORWARD 1: Política por Defecto
# Cerramos TODO el tráfico que quiera cruzar el router.
iptables -P FORWARD DROP
# REGLA FORWARD 2: Permitir Conexiones Establecidas
# Permite que los paquetes de RESPUESTA vuelvan.
iptables -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT
# REGLA FORWARD 3: Permitir el Port Forwarding
# Permitimos explícitamente que los paquetes (HTTP/S) que hemos
# redirigido antes (DNAT) puedan llegar al Servidor Web.
iptables -A FORWARD -i eth0 -o eth1 -p tcp --dport 80 -d 172.26.0.20 -j ACCEPT
iptables -A FORWARD -i eth0 -o eth1 -p tcp --dport 443 -d 172.26.0.20 -j ACCEPT
# REGLA FORWARD 4: Permitir Web -> BBDD (MySQL)
# Permite que SOLO el Servidor Web (172.26.0.20)...
# ...se conecte al Servidor BBDD (172.26.0.150) al puerto 3306.
iptables -A FORWARD -i eth1 -s 172.26.0.20 -o eth2 -d 172.26.0.150 -p tcp --dport 3306 -j ACCEPT
# REGLA FORWARD 5: Permitir a las Redes Internas salir a Internet
# Permite que tanto la Red Web (eth1) como la BBDD (eth2)
# puedan iniciar conexiones hacia Internet (p.ej. para actualizaciones).
iptables -A FORWARD -i eth1 -o eth0 -j ACCEPT
iptables -A FORWARD -i eth2 -o eth0 -j ACCEPT

Il router Trinux è pronto.

4. Passo 2: Configurazione di Ubuntu DB (172.26.0.150)

Sección titulada «4. Paso 2: Configuración del Ubuntu BBDD (172.26.0.150)»

Ci connetteremo al server Ubuntu che fungerà da DB.

Primo, identificheremo il nome della nostra interfaccia (es: ens33, eth0) con: ip a

Ora, modificheremo il file di Netplan con sudo.

Ventana de terminal
user.portelcore@ubuntu-BBDD:~$ sudo nano /etc/netplan/50-cloud-init.yaml

Il contenuto del file è il seguente.

network:
version: 2
ethernets:
enp0s3:
dhcp4: true
enp0s8:
dhcp4: no
addresses:
- 172.26.0.150/25
routes:
- to: default
via: 172.26.0.129
nameservers:
addresses: [8.8.8.8, 1.1.1.1]

Verificheremo che l'IP sia corretto:

Ventana de terminal
user.portelcore@ubuntu-bbdd:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 06:00:27:a8:9d:4e brd ff:ff:ff:ff:ff:ff
inet 172.18.33.171/24 metric 100 brd 172.18.33.255 scope global dynamic enp0s3
valid_lft 6999sec preferred_lft 6999sec
inet6 fe80::400:27ff:fea8:9d4e/64 scope link
valid_lft forever preferred_lft forever
3: enp0s8: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 06:00:27:15:e4:03 brd ff:ff:ff:ff:ff:ff
user.portelcore@ubuntu-bbdd:~$ sudo netplan apply
user.portelcore@ubuntu-bbdd:~$ sudo ip link set enp0s8 up
user.portelcore@ubuntu-bbdd:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 06:00:27:a8:9d:4e brd ff:ff:ff:ff:ff:ff
inet 172.18.33.171/24 metric 100 brd 172.18.33.255 scope global dynamic enp0s3
valid_lft 6763sec preferred_lft 6763sec
inet6 fe80::400:27ff:fea8:9d4e/64 scope link
valid_lft forever preferred_lft forever
3: enp0s8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 06:00:27:15:e4:03 brd ff:ff:ff:ff:ff:ff
inet 172.26.0.150/25 brd 172.26.0.255 scope global enp0s8
valid_lft forever preferred_lft forever
inet6 fe80::400:27ff:fe15:e403/64 scope link
valid_lft forever preferred_lft forever
user.portelcore@ubuntu-bbdd:~$
Ventana de terminal
user.portelcore@ubuntu-bbdd:~$ sudo apt update
user.portelcore@ubuntu-bbdd:~$ sudo apt install -y mariadb-server

4.3. Configurare l'accesso remoto a MariaDB

Sección titulada «4.3. Configurar el Acceso Remoto a MariaDB»

Dobbiamo dire a MariaDB di accettare connessioni sul suo IP, non solo su localhost.

Ventana de terminal
user.portelcore@ubuntu-bbdd:~$ sudo nano /etc/mysql/mariadb.conf.d/50-server.cnf

Cercheremo la riga bind-address = 127.0.0.1 e la sostituiremo con:

bind-address = 172.26.0.150

Salveremo il file e riavvieremo il servizio MariaDB:

Ventana de terminal
user.portelcore@ubuntu-bbdd:~$ sudo systemctl restart mariadb
user.portelcore@ubuntu-bbdd:~$ sudo systemctl enable --now mariadb
Synchronizing state of mariadb.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
Executing: /usr/lib/systemd/systemd-sysv-install enable mariadb
user.portelcore@ubuntu-bbdd:~$

Accederemo alla console di MariaDB:

Ventana de terminal
user.portelcore@ubuntu-bbdd:~$ sudo mariadb -u root

Eseguiremo i comandi SQL. Questi comandi creano il database e concedono i permessi all'utente ‘user.portelcore’ SOLO dall'IP del server web (172.26.0.20).

Ventana de terminal
user.portelcore@ubuntu-bbdd:~$ sudo mariadb -u root
Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 31
Server version: 10.11.13-MariaDB-0ubuntu0.24.04.1 Ubuntu 24.04
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
MariaDB [(none)]> CREATE DATABASE wordpress_db;
Query OK, 1 row affected (0,001 sec)
MariaDB [(none)]> GRANT ALL PRIVILEGES ON wordpress_db.* TO 'user.portelcore'@'172.26.0.20' IDENTIFIED BY 'P@ssw0rd';
Query OK, 0 rows affected (0,010 sec)
MariaDB [(none)]> FLUSH PRIVILEGES;
Query OK, 0 rows affected (0,001 sec)
MariaDB [(none)]> EXIT;
Bye
user.portelcore@ubuntu-bbdd:~$

Il server del database è pronto.

5. Passo 3: Configurazione di Ubuntu Web (172.26.0.20)

Sección titulada «5. Paso 3: Configuración del Ubuntu Web (172.26.0.20)»

Ci connetteremo al server Ubuntu che fungerà da WordPress.

Come prima, identificheremo il nome dell'interfaccia con ip a.

Ventana de terminal
user.portelcore@ubuntu-web:~$ ip a
user.portelcore@ubuntu-web:~$ sudo nano /etc/netplan/50-cloud-init.yaml

Incolleremo questo contenuto. Notiamo che il gateway è differente (.1):

network:
version: 2
ethernets:
enp0s3:
dhcp4: true
enp0s8:
dhcp4: no
addresses:
- 172.26.0.20/25
routes:
- to: default
via: 172.26.0.129
nameservers:
addresses: [8.8.8.8, 1.1.1.1]

Applicheremo la configurazione:

Ventana de terminal
user.portelcore@ubuntu-web:~$ sudo netplan apply
user.portelcore@ubuntu-web:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 08:00:27:c3:4e:ed brd ff:ff:ff:ff:ff:ff
inet 172.18.33.171/24 metric 100 brd 172.18.33.255 scope global dynamic enp0s3
valid_lft 6747sec preferred_lft 6747sec
inet6 fe80::a00:27ff:fec3:4eed/64 scope link
valid_lft forever preferred_lft forever
3: enp0s8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 08:00:27:80:64:e4 brd ff:ff:ff:ff:ff:ff
inet 172.26.0.20/25 brd 172.26.0.127 scope global enp0s8
valid_lft forever preferred_lft forever
inet6 fe80::a00:27ff:fe80:64e4/64 scope link
valid_lft forever preferred_lft forever
user.portelcore@ubuntu-web:~$
Ventana de terminal
user.portelcore@ubuntu-web:~$ sudo apt update
user.portelcore@ubuntu-web:~$ sudo apt install -y apache2 php libapache2-mod-php php-mysql wget

Ora scaricheremo e prepareremo WordPress:

Ventana de terminal
# Descarregar a /tmp
user.portelcore@ubuntu-web:~$ sudo wget https://wordpress.org/latest.tar.gz -P /tmp
# Descomprimir al directori web (esborrant l'index.html d'Apache)
user.portelcore@ubuntu-web:~$ sudo rm /var/www/html/index.html
user.portelcore@ubuntu-web:~$ sudo tar -xzvf /tmp/latest.tar.gz -C /var/www/html --strip-components=1
# Netejar
user.portelcore@ubuntu-web:~$ sudo rm /tmp/latest.tar.gz

Creeremo il file di configurazione di WordPress a partire dall'esempio:

Ventana de terminal
# Copiamos el ejemplo
user.portelcore@ubuntu-web:~$ sudo cp /var/www/html/wp-config-sample.php /var/www/html/wp-config.php
# Lo editamos
user.portelcore@ubuntu-web:~$ sudo nano /var/www/html/wp-config.php

Modificheremo queste righe chiave.

// ...
/** The name of the database for WordPress */
define( 'DB_NAME', 'wordpress_db' );
/** MySQL database username */
define( 'DB_USER', 'user.portelcore' );
/** MySQL database password */
define( 'DB_PASSWORD', 'P@ssw0rd' );
/** MySQL hostname */
define( 'DB_HOST', '172.26.0.150' );
// ...

5.4. Regolare i permessi e riavviare Apache

Sección titulada «5.4. Ajustar Permisos y Reiniciar Apache»

Infine, daremo i permessi al web server sui file:

Ventana de terminal
user.portelcore@ubuntu-web:~$ sudo chown -R www-data:www-data /var/www/html
user.portelcore@ubuntu-web:~$ sudo systemctl restart apache2

Ora, per verificare, apriremo il browser e vedremo se è possibile accedere a WordPress.

Pertanto, apriremo un browser web all'indirizzo http://172.26.0.20:

image.png

image.png