The Sefthy Connector: inside the NanoPi R3S LTS
Why we picked a NanoPi R3S LTS in a CNC case. SoC, real throughput, out-of-band management and why a mini-PC was the wrong call.
Tag
10 articles
Why we picked a NanoPi R3S LTS in a CNC case. SoC, real throughput, out-of-band management and why a mini-PC was the wrong call.
Flipping DNS records under stress is the worst part of L3 DR. With an L2 tunnel you skip it entirely because the IP does not change.
Legacy apps with hard-coded IPs are the main obstacle to clean DR. An L2 tunnel makes them recoverable without rewriting them.
What a Layer-2 tunnel is, why in DR it matters more than anything else and how this single architectural choice separates a 4-minute RTO from a 4-hour one.
One head office, two branches, one shared DR cloud. How to do it with the Connector without creating IP collisions.
Encryption, tenant isolation, mutual auth: what makes an enterprise-grade L2 tunnel actually secure and the questions to ask vendors.
Real Connector ↔ Sefthy datacentre latency in three setups: fibre, FTTH 2.5G, 5G. What works and what does not.
Layer 3 DR is the historical default, but it brings NAT, DNS reconfiguration and site-to-site VPN. Layer 2 eliminates roughly 70% of that work.
A technical walkthrough (with ARP captures) showing how a Sefthy Connector extends the customer subnet into the Sefthy cloud while preserving original IPs.
A site-to-site VPN routes packets between different subnets. An L2 tunnel extends the same subnet. The difference only shows up when something breaks.