- cross-posted to:
- hackernews@derp.foo
- cross-posted to:
- hackernews@derp.foo
Hopefully this is not too long! There has been a lot of changes since the last time I posted a full overview like this
Hopefully this is not too long! There has been a lot of changes since the last time I posted a full overview like this
Hi OP. If you’re reading this, I have a few questions:
It was great reading about your lab. I’ll try and follow your blog on RSS if you have a feed. Thanks.
Yes, I also access the lab via the Linode box. I do however have direct VPN access too. The reason for using the Linode box is that for some reason, the speed and latency via the Linode box is far better that directly in. I can only assume its some kind of peering thing. I always connect in via my phone on T-Mobile, so perhaps the connection between T-Mobile and Linode, and the connection between AT&T and Linode, is better than T-Mobile to AT&T Residential? Unsure, all I know is that it works 100x better. And it also means I don’t need 2 different connections for the primary and secondary WAN, I can just connected to Linode and it will connect over whatever connection is active
This really is a whitebox build, it uses very little power. The disks use the most amount of power, which there is no getting around
The 1Gb switches? yes, I ran out of ports on the Dell, or am very, very close
Everything that can run in containers already is, on Debian VM’s within ESXi
I am using CloudFlare in front of it, so that’s probably why. But even directly its pretty quick. I guess NVMe storage and decent internet means its fast?
Thanks!
How do you relay your VPN connection over your Linode box? I can understand a direct VPN connection, but I can’t understand the networking behind relaying the VPN connection around the Linode box.
Ah, yes CloudFlare is a great proxy/CDN. Thanks
Not OP, but also curious about number 5, I noticed that blog article loaded lickety-split!
Good to hear! I replied above about it, here was my reply