helvede.net is one of the many independent Mastodon servers you can use to participate in the fediverse.
Velkommen til Helvede, fediversets hotteste instance! Vi er en queerfeministisk server, der shitposter i den 9. cirkel. Welcome to Hell, We’re a DK-based queerfeminist server. Read our server rules!

Server stats:

167
active users

#openvpn

0 posts0 participants0 posts today

The Open Technology Fund has filed a lawsuit against the Trump administration for cutting funding previously authorized by Congress

The organization is part of the United States Agency for Global Media and is a major sponsor for #Tor, #letsencrypt #OpenVPN, and many anti-surveillance projects

The White House cut USAGM funding earlier this month through a presidential executive order
news.bloomberglaw.com/federal- (paywalled)

news.bloomberglaw.com · Open Technology Fund Sues Trump Officials Over Budget Freeze (3)By Daniel Seiden
#OpenVPN has a shitty #AI support bot. I asked it how to switch it off and it couldn't help me. Now, I've opened a case with their support to have them switch it off.

I encourage everybody to open extra cases with companies that employ shitty AI bots to have them spend time explaining to you that you cannot switch it off. Feel free to waste as much time playing stupid as possible.

With a bit of luck that'll pop to the top and they'll see that shitty useless AI bots cost more than they save.

#SysadminLife pondering…

Given
- Remote #Debian/#Ubuntu server
- can‘t be accessed from internet
- behind (CG-)NATv4, no IPv6
- can reach any outside tcp/udp port

- A network under my full control
- Firewall can do: #IPSec, #Wireguard, #OpenVPN, #Tailscale/#Headscale Client
- I can self host any opensource service/container, and expose it

Challenge
- Make services on that server accessible TO my network
- server MUST NOT reach ONTO my network
- No 3rd party service dependence

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.

I'm doing the #ansible configuration of #OpenVPN server:

* at home
* on a #FreeBSD host
* with a dynamic IP address

May be an interesting challenge - I've been doing it for 10+ years, but most of the heavy lifting has been handled by the appliance.

e.g. when an IP address change happens

* handling IP address change
* getting the routing right
* any pf stuff to reset?
* other issues I'm not comprehending yet

I'm guessing that some of the issues may not be relevant because I'm just not using those features

Replied to Max Resing

@resingm @T_X The code for #WireGuard ( wireguard.com/repositories/ )has been designed with ease-of-implementation and simplicity in mind with very few lines of code, and easily auditable for security vulnerabilities. Compared to #IPsec or #OpenVPN #OpenSSL, WireGuard is meant to be comprehensively reviewable by single individuals rather than teams.

So faster point-to-point #VPN , due to #Linux kernel integration (since Linux 5.6 ~2020) and simpler and easier to maintain code base

www.wireguard.comRepositories - WireGuard
Replied in thread

@ifixcoinops

ProtonVPN's software is terrible on Linux, but I use it with `openvpn` and it's been rock-solid for me. The tunnel hasn't even gone down once since I last rebooted ... 120 days ago.

Are you using their terrible software/GUI, or what? They have #openvpn config files, that's all I'm using.

Replied in thread

@mullvadnet I don't like it at all, to be honest.

Right now I can setup #OpenWrt using your #XTLS bridges and #OpenVPN. And that's probably most advanced bypass setup.

But for #WireGuard you do not provide something comparable to this in terms of switchover/failover, easy setup, censorship bypass.
I can not use your custom mix of #Shadowsocks and #WireGuard on my OpenWrt router. And Shadowsocks is much worse than #xtlsreality

I will probably switch to a different VPN provider.

Amazing! @reynir wrote an article about his discoveries of two CVE in OpenVPN while re-implementing the same protocol -- TL;DR: it's worth to spend time and money on re-developing network & security protocols. Read it at blog.robur.coop/articles/2024-

blog.robur.coop Robur's blog - MirageVPN and OpenVPN Discoveries made implementing MirageVPN, a OpenVPN-compatible VPN library

Now and then it would be nice to run a few commands with VPN enabled without interfering with other tasks.

OpenVPN does not support network namespaces directly, but as a proof of concept I have written an `up` script that configures the tun device inside a network namespace.

This allows me to run commands (including bash) with `ip netns exec vpn cmd`

codeberg.org/pmakholm/openvpn-

Codeberg.orgopenvpn-netns/vpn-up.sh at mainopenvpn-netns - Configure OpenVPN connections with tunnel endpoint in a Linux Network Namespace