• Gluetun or server vpn?

    From Shurato@1337:3/185 to All on Sat Jan 24 01:15:00 2026
    Should I run Gluetun, or my wireguard vpn on the server? Inbound traffic is using my ip dyndns for the most part, outbound traffic and torrents use the vpn. Right now I'm running wireguard (with protonvpn) on the server and I think that's good enough. It doesn't have a kill switch though, which I'm a little concerned about. What is the general opinion on this setup?

    --
    Shurato, Sysop Shurato's Heavenly Sphere (ssh, telnet, pop3, ftp,nntp,
    ,wss) (Ports 22,23,110,21,119,999)


    *** THE READER V4.50 [freeware]
    ---
    * Origin: Shurato's Heavenly Sphere telnet://shsbbs.net (1337:3/185)
  • From Arelor@1337:3/191 to Shurato on Sat Jan 24 19:15:09 2026
    Re: Gluetun or server vpn?
    By: Shurato to All on Sat Jan 24 2026 01:15 am

    Should I run Gluetun, or my wireguard vpn on the server? Inbound traffic is

    It depends on what you intend to do with your VPN.

    If you intend to link many office networks together through the Internet then I think handling the VPN is best left to your router, if it can handle it.


    --
    gopher://gopher.richardfalken.com/1/richardfalken
    --- SBBSecho 3.34-Linux
    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1337:3/191)
  • From Shurato@1337:3/185 to Arelor on Sun Jan 25 21:48:00 2026

    * In a message originally to Shurato, Arelor said:

    Re: Gluetun or server vpn? By: Shurato to All on Sat Jan 24 2026
    01:15 am

    Should I run Gluetun, or my wireguard vpn on the server? Inbound
    traffic is

    It depends on what you intend to do with your VPN.

    If you intend to link many office networks together through the Internet then I think handling the VPN is best left to your router, if it can
    handle it.

    It can, but some of my clients require split tunnel

    --
    Shurato, Sysop Shurato's Heavenly Sphere (ssh, telnet, pop3, ftp,nntp,
    ,wss) (Ports 22,23,110,21,119,999)


    ---
    * Origin: Shurato's Heavenly Sphere telnet://shsbbs.net (1337:3/185)