Hello there,

Just want to preface that this is for selfhosted purposes, I may be routing my network in other way later.

I wanted to be able to setup a wireguard docker container with gluetun such that I can connect multiple devices to it at home, in order to minimize my “five device limit” with mullvad. I have the following docker compose:

  gluetun:
    image: qmcgaw/gluetun
    container_name: gluetun-wireguard
    restart: unless-stopped
    cap_add:
      - NET_ADMIN
    devices:
      - /dev/net/tun:/dev/net/tun
    volumes:
      - ./gluetun:/gluetun
    environment:
      - VPN_SERVICE_PROVIDER=#
      - VPN_TYPE=wireguard
      - WIREGUARD_PRIVATE_KEY=#
      - WIREGUARD_ADDRESSES=#
      - SERVER_CITIES=#setup#setup
      # Timezone for accurate log times
      - TZ=#
      # Server list updater
      # See https://github.com/qdm12/gluetun-wiki/blob/main/setup/servers.md#update-the-vpn-servers-list
      - UPDATER_PERIOD=24h
    ports:
      - 51820:51820/udp
  wireguard-server:
    image: linuxserver/wireguard
    container_name: wireguard-server
    network_mode: service:gluetun # << important
    cap_add:
      - NET_ADMIN
      - SYS_MODULE
    environment:
      - PUID=1000
      - PGID=1000
      - SERVERPORT=51820
      - PEERS=iphone
      - PEERDNS=auto
    volumes:
      - ./config:/config
      - /lib/modules:/lib/modules
    restart: unless-stopped

Whenever I try connecting to it by iphone, which is my first attempt for the peer, it doesn’t quite work out. The packets are received by the container, and querying cloudflare as such works:

$ sudo docker exec -it wireguard-server ping -c 3 1.1.1.1

Is there any obvious error I’ve made?

If I’m making the XY Problem, please let me know. If there is a more apt community, please let me know.

  • rearview@lemmy.zip
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    60 minutes ago

    If you have the WireGuard config from Mullvad already, just edit your wg.conf files on client devices to route all traffic via the Mullvad servers. Basically replace all the values of the [Peer] block with Mullvad values.

    If you can share your Mullvad wg config file and your wireguard-server config file here, we can sort this out together

    Edit: actually since your only goal is to increase the Mullvad device limits, why not just use Mullvad-provided confs directly in your client WireGuard apps? Should be straightforward to do

  • illusionist@lemmy.zip
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    10 hours ago

    The network_mode: service: gluetun looks off to me but I can’t check.

    Does each one their own?

  • Tinkerer@lemmy.ca
    link
    fedilink
    English
    arrow-up
    7
    ·
    20 hours ago

    I’ve just setup headscale in docker and it worked right away. It’s even faster than when I was using tailscale. It was very easy to setup and I’ve been using it for about a month with no issues. Doesn’t really help but I haven’t used gluetun myself.

  • LazerDickMcCheese@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    8
    ·
    21 hours ago

    Gluetun is a great example of “I changed nothing and it suddenly works”. I’ve had to set up this exact docker container several times, and it usually takes me a week of retries until it chooses to work. I wish I had better advice for you

  • frongt@lemmy.zip
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    1
    ·
    19 hours ago

    I don’t think you want two VPN services, I think you want one VPN service and plain network routing. Use the VPN server as the local gateway, and the VPN server routes that traffic up the tunnel.

  • undefined@lemmy.hogru.ch
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    2
    ·
    20 hours ago

    Is doing this in Docker necessary? I like containerization too but a VPN server seems a little intense — why not install it directly?