tubbadu

joined 2 years ago
[โ€“] tubbadu@lemmy.kde.social 4 points 1 year ago (1 children)

I found this repo and image which may work for you as is or as a starting point.

Wow I completely missed this one! This is exactly what I was planning to do! I actually installed the original repo because I'm not on arm, and it seem to work very well! I have to do a few tests to check if the killswitch actually works

thank you very very much!

[โ€“] tubbadu@lemmy.kde.social 4 points 1 year ago* (last edited 1 year ago) (6 children)

isn't it an entire OS? I only need to bind the internet traffic of my container to the ones I want doing something like network_mode: container:myhidemecontainer in docker compose

[โ€“] tubbadu@lemmy.kde.social 36 points 1 year ago

my exact thought XD

[โ€“] tubbadu@lemmy.kde.social 35 points 1 year ago

It's the only way, they can go fuck themselves

[โ€“] tubbadu@lemmy.kde.social 13 points 1 year ago

Because he said so

Jesus Christ. It would be a good idea to format that file to have an exit as first line to avoid this

[โ€“] tubbadu@lemmy.kde.social 11 points 1 year ago (1 children)

That's a big ass mushroom tho

This is the official package that is now unmaintained, I use the fork of one of the original devs: https://github.com/Helium314/openboard

It supports adding an external swipe type library, and sadly the only working one is the gboard one, that works like a charm however

It is not on fdroid (yet), so you can install it manually or using obtainium

[โ€“] tubbadu@lemmy.kde.social 3 points 1 year ago (4 children)

Lemmy

Nope for me it works, I'm using the openboard fork with gesture typing

[โ€“] tubbadu@lemmy.kde.social 1 points 1 year ago (1 children)

the container has no internet connection at all :(
if I enter in the container shell and try to ping anything it says "bad address"

tubbadu@fedoraserver:~/docker/gluetun$ docker exec -it gluetun sh
/ # ping linux.org
ping: bad address 'linux.org'
[โ€“] tubbadu@lemmy.kde.social 1 points 1 year ago (3 children)
wgcf register
wgcf generate
[โ€“] tubbadu@lemmy.kde.social 1 points 1 year ago (5 children)

Hi! I tried to configure it as you suggested:

  • I used wgcf to generate wgcf-profile.conf
  • I then configured gluetun with the following docker compose file:
version: "3"

services:
	gluetun:
		image: qmcgaw/gluetun
		container_name: gluetun
		cap_add:
			- NET_ADMIN
		environment:
			- VPN_SERVICE_PROVIDER=custom
			- VPN_TYPE=wireguard
			- VPN_ENDPOINT_IP=162.159.192.1 # I resolved the ip running `host engage.cloudflareclient.com`
			- VPN_ENDPOINT_PORT=2408 # Endpoint from wgcf-profile.conf (engage.cloudflareclient.com:2408)
			- WIREGUARD_PUBLIC_KEY=asdfghjklqwertyuiopzxcvbnm # PublicKey from wgcf-profile.conf
			- WIREGUARD_PRIVATE_KEY=lkjhgfdsapoiuytrewqmnbvcxz # PrivateKey from wgcf-profile.conf
			# - WIREGUARD_PRESHARED_KEY= #I dnd't find anything about this in wgcf-profile.conf, but in gluetun wiki it says it's optional, so I removed it
			- WIREGUARD_ADDRESSES=172.16.0.2/32 # Address from wgcf-profile.conf (the first one)
		volumes:
			- ./gluetun:/gluetun
		ports:
			- 8080:8080 # qBittorrent
		restart: unless-stopped

However, it is stuck in a loop trying to authenticate:

2024-01-24T09:59:48Z INFO [vpn] starting

2024-01-24T09:59:48Z INFO [firewall] allowing VPN connection...

2024-01-24T09:59:48Z INFO [wireguard] Using available kernelspace implementation

2024-01-24T09:59:48Z INFO [wireguard] Connecting to 162.159.192.1:2480

2024-01-24T09:59:48Z INFO [wireguard] Wireguard setup is complete. Note Wireguard is a silent protocol and it may or may not work, without giving any error message. Typically i/o timeout errors indicate the Wireguard connection is not working.

2024-01-24T10:01:11Z INFO [healthcheck] program has been unhealthy for 1m21s: restarting VPN (see https://github.com/qdm12/gluetun-wiki/blob/main/faq/healthcheck.md)

2024-01-24T10:01:11Z INFO [vpn] stopping

2024-01-24T10:01:11Z INFO [vpn] starting

2024-01-24T10:01:11Z INFO [firewall] allowing VPN connection...

2024-01-24T10:01:11Z INFO [wireguard] Using available kernelspace implementation

2024-01-24T10:01:11Z INFO [wireguard] Connecting to 162.159.192.1:2480

2024-01-24T10:01:11Z INFO [wireguard] Wireguard setup is complete. Note Wireguard is a silent protocol and it may or may not work, without giving any error message. Typically i/o timeout errors indicate the Wireguard connection is not working.

2024-01-24T10:01:19Z INFO [dns] downloading DNS over TLS cryptographic files

2024-01-24T10:01:34Z WARN [dns] cannot update files: Get "https://www.internic.net/domain/named.root": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

2024-01-24T10:01:34Z INFO [dns] attempting restart in 10m40s

2024-01-24T10:01:47Z ERROR [ip getter] Get "https://ipinfo.io/": context deadline exceeded (Client.Timeout exceeded while awaiting headers) - retrying in 10m40s

2024-01-24T10:02:38Z INFO [healthcheck] program has been unhealthy for 1m26s: restarting VPN (see https://github.com/qdm12/gluetun-wiki/blob/main/faq/healthcheck.md)

2024-01-24T10:02:38Z INFO [vpn] stopping

2024-01-24T10:02:38Z INFO [vpn] starting

2024-01-24T10:02:38Z INFO [firewall] allowing VPN connection...

2024-01-24T10:02:38Z INFO [wireguard] Using available kernelspace implementation

2024-01-24T10:02:38Z INFO [wireguard] Connecting to 162.159.192.1:2480

2024-01-24T10:02:38Z INFO [wireguard] Wireguard setup is complete. Note Wireguard is a silent protocol and it may or may not work, without giving any error message. Typically i/o timeout errors indicate the Wireguard connection is not working.

2024-01-24T10:04:09Z INFO [healthcheck] program has been unhealthy for 1m31s: restarting VPN (see https://github.com/qdm12/gluetun-wiki/blob/main/faq/healthcheck.md)

2024-01-24T10:04:09Z INFO [vpn] stopping

2024-01-24T10:04:09Z INFO [vpn] starting

2024-01-24T10:04:09Z INFO [firewall] allowing VPN connection...

2024-01-24T10:04:09Z INFO [wireguard] Using available kernelspace implementation

2024-01-24T10:04:09Z INFO [wireguard] Connecting to 162.159.192.1:2480

2024-01-24T10:04:09Z INFO [wireguard] Wireguard setup is complete. Note Wireguard is a silent protocol and it may or may not work, without giving any error message. Typically i/o timeout errors indicate the Wireguard connection is not working.

Is my configuration correct or am I missing something?

thank you very very much in advance!

view more: โ€น prev next โ€บ