Stop being the product.
Become the owner.
Experiment: making VPN sessions survive relay and…
Experiment: making VPN sessions survive relay and transport failure Hi all, I've been experimenting with a networking idea that treats the session as the stable identity rather than the transport. Traditional VPNs bind connection identity to a tunnel or socket. If the transport breaks, the connection usually resets. In this prototype I'm exploring a different model: connection = session identity transport = replaceable attachment The goal is to see whether session continuity can survive events like: • relay failure • path switching • NAT rebinding • transport migration Current prototype includes: • session runtime with deterministic state machine • transport abstraction layer • relay forwarding experiments • session migration demo • multi-hop prototype (client → relay → relay → server) Example flow: SESSION CREATED client → relay1 → server relay1 failure RELAY SWITCH client → relay3 → server SESSION SURVIVES This is still a research prototype (not production). Repo: https://github.com/Endless33/jumping-vpn-preview I'm curious what networking / distributed systems engineers think about a session-centric model vs tunnel-centric VPNs. Would love to hear criticism or ideas. #technology | earnings |
| 4,000 mlx total |
| $0
total |
| engagement |
| 6 views |
| 0 reactions |