Tunnel via TCP due to network restrictions #1107

Closed
opened 2026-04-05 18:19:12 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @SelfhostedPro on 8/6/2025

Looking through the docs and didn't see it so I'm making this, I was wondering if there's a possibility of having pangolin use wireguard tunnels that are tunneled via tcp? Similar to something like htun or what is described in this article

So that all that would be needed is outbound traffic on port 443 for edge servers running newt instead of using a separate port for wireguard?

flowchart LR

    subgraph InternalNetwork["Internal Network"]
    pangolin["Pangolin"]
    gerbil["Gerbil"]

    pangolin <--> gerbil
    end

    subgraph RemoteNetwork["Remote Network"]
      subgraph RemoteServer["Remote Server"]
      ssh["SSH Service"]
      newt["Newt"]
      end
    end

    newt <-->|TCP Tunnel on 443| gerbil

    newt <--> ssh
*Originally created by @SelfhostedPro on 8/6/2025* Looking through the docs and didn't see it so I'm making this, I was wondering if there's a possibility of having pangolin use wireguard tunnels that are tunneled via tcp? Similar to something like [htun](https://github.com/AdrianVollmer/htun/) or what is described in [this article](https://www.eduvpn.org/running-wireguard-over-tcp-a-solution-for-udp-blocking-issues/) So that all that would be needed is outbound traffic on port 443 for edge servers running newt instead of using a separate port for wireguard? ```mermaid flowchart LR subgraph InternalNetwork["Internal Network"] pangolin["Pangolin"] gerbil["Gerbil"] pangolin <--> gerbil end subgraph RemoteNetwork["Remote Network"] subgraph RemoteServer["Remote Server"] ssh["SSH Service"] newt["Newt"] end end newt <-->|TCP Tunnel on 443| gerbil newt <--> ssh ```
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/pangolin#1107