freeatlantis.com is one of the many independent Mastodon servers you can use to participate in the fediverse.

Administered by:

Server stats:

197
active users

#openvpn

0 posts0 participants0 posts today

Hey #homelab users!

You probably already know me by my free @BoxyBSD project and I often got asked about IPv4 addresses. Currebtly, I tinker with a new but also honestly not free service. The idea is creating a static IP service for homelab users. I'm aware that there're already some around, so what could be some benefits here?

- Static single #IPv4 & #IPv6 /48 (so you can subnet your homelab to several /64 without breaking #slacc)
- Bigger subnets (IPv4: /29, /28, /27 | IPv6: /32)
- Full RIPE personalization (inc. abuse & Co)
- #OpenVPN, #Wireguard, #GRE Support
- Auto configure (e.g., you load the wireguard config on any client and the addresses Arena immediately bound to that interface)
- Split usage / multiple tunnels: Use different IPs from your subnets at different locations
- Integration into #BoxyBSD
- Location in Germany or Netherlands (selectable)
- Hosted on redundant #FreeBSD nodes

Pricing:
- The starter package probably around 10€/month (not more) + 15€ setup including 2T traffic
- Pricing for addiriinal/larger subnets not yet sure, probably higher setup fees to avoid hoppers and spamers to keep the addresses clean
- Optional traffic packages (when exceeding speed Limit of 10Mbit which should still be ok for most homelabs)

World this be interesting? Im aware that many ones already do this by VPS themselves, so this might just be a bit easier and optionally offering whole networks including RIPE personalizations.

Replied in thread

@geffrey I'm no expert, but the best way is to use a VPN. It is the only way to guarantee no one can see what you're sending and receiving.

For example, ISPs can intercept connections even if you're using HTTPS. I've caught my ISP doing that a lot of times. But they can't do anything if I'm using a VPN. (While the intention of the ISP is good, and because they were forced by the government, it still is not something I personally would tolerate.)

IF, the network in your work is blocking a lot of ports, there is still a way… your VPN needs to support #OpenVPN TCP, you can then bypass most setups. If they're good… then, probably no luck in using a VPN.

Maybe using DoH (DNS-over-HTTPS) or DoT (DNS-over-TLS) can help minimise it. But, there's no guarantee on that. The example I mentioned above, I was completely behind DoH and my ISP can still intercept and scan. ;)