How to self-host servers in your living room on static IPs

13 points by lim


marginalia

You should configure SSH to accept keys only and (optional) only listen on a local IP address (e.g. 10 network). This is beyond the scope of the article, but it’s quite trivial to set up.

Besides only doing public key sign in, running sshd on a non-standard port is also nice. Gets rid of considerable log spam from low effort drive by intrusion attempts. Not really a security thing just a log noise reduction measure.

johnklos

I do something like this, using tinc.

I've got a machine on a "business" Internet circuit with several static IPs, and because we can't control the routing to our /29, we have to bridge. tinc allows that, so my home machine connects via tinc, keeps a route to the machine on the "business" Internet that runs tinc, and makes the "business" Internet default gateway its own.

It works quite well no matter where I am, and recovers quickly from network changes or network drops of all kinds. It works behind CG-NAT, or over IPv6, if available.

https://poofydoof.zia.io

I've run other servers over tinc tunnels for months, with hardly any problems.

ysun

I do it with ranet and run Babel on top of the IPsec mesh with BIRD. All my machines (nixos btw) have publicly reachable v4/6 address advertised under my own ASN and IP blocks thru a few VPS providers with BGP sessions. Took me a while to wire up vrf and play with segment routing, but it’s a very interesting and fun learning experience ;)

e.g. I have a public NTP server (with nts ofc) in the pool in my shitty apt that had already served probably over 10B requests behind sfr copper wire