tin-ot / pi_cluster_blog

PI CLUSTER

MOTIVATION

This repo is kind of a blog to follow the step towards having a highly available pi cluster. Moreover having the main block of an organization ( web servers, registry, vpn...) with a minimum of single point of failures.

Its open in case it is of any use to someone else later.

Or to get feedback if anyone has anything that could help. Please do open an issue.

I do this for educational purposes. In order to get a grip on the technicalities of many fields that I don't get to encounter normally.

I could use this as a base to create some form of organization in my life. I don't have any concrete objective on this yet, just an eventuality.

I may open my code.

DESIGN

main goal :

flowchart LR
A(wild) --> |fa:fa-certificate PubIP| B[fa:fa-shield-alt Livebox5]
    B --> C{fa:fa-arrows-alt Mikrotik\nCRS112-8P-4S}
    C -->|Ip 1| D[fa:fa-server Pi4_01]
    C -->|Ip 2| E[fa:fa-server Pi4_02]
    C -->|Ip 3| F[fa:fa-server Pi5_03]

Loading

Having any Pi that could fail at any given point.

pi_cluster_blog's Issues

tcp syn never acked when DNATing to node001:80

reproduce :

srcnat livebox to mikrtoik ( ping ok from node001 to anywhere )
dstnat redirect wan link on mikrotik 8080 to node001:80
node001 listening correcly on 80

curl to wan_mikrtoik:8080 ===> tcp SYN indeed sent but never SYN-ACKed

possible root cause :
route to lan (between node001 and test machine .. livebox ) is annouced on routing table through wlan0
192.168.1.0/24 via wlan0

possible long term mitigation scripting the switch between 2 routing tables in case of connectivity loss ( mah ... )