Help with wireguard container routing
reddit / selfhosted

----------------------------------------------------------------------
Jaded_Confusion_1750 · 2023-11-02 13:56

Hello fellow `selfhosters` !

I have originally posted this question
[here](https://discourse.linuxserver.io/t/help-with-wireguard-
container-routing-setup/8220/1) but after having no answers I thought
I might have better luck on this sub.

I currently run `linux-server/wireguard` in server mode on a `VPS`,
serving as a “hub” on a [Site Gateway as a
Spoke](https://www.procustodibus.com/blog/2022/06/multi-hop-
wireguard/#site-gateway-as-a-spoke) topology which connects remote
clients to a `Pfsense`’s `wireguard` at home, acting as site gateway
to some services on my `homelab`.

After reading this [amazing
post](https://www.linuxserver.io/blog/advanced-wireguard-container-
routing), I’ve become tempted to implement a `mullvad` exit route for
requests that are not within the `homelab`. However, I've found three
problems on the path of such achievement:

1. The setup on the post assumes a `wireguard` at home acting as a
server with a listening port exposed, while on my setup I have
`wireguard` client at home with no ports exposed.

2. Another oddity of my setup is that I run `linux-server/wireguard`
with `network_mode=host`. This is because there are applications on
the host that are not containerized and need to communicate to hosts
on the `homelab` i.e: `loki-docker-driver` pushing logs

3. My networking skills are not something to be proud of 🙁

Any clues/comments are very welcome 😃

----------------------------------------------------------------------
Ordinary_Employer_39 · 2023-12-01 02:10

This might be what you're looking for
https://github.com/NOXCIS/Wiregate