Host can not access wg-easy peers, but the wg-easy container on host can

[dacianpeng]

Say,
wg-easy host 192.168.1.1/32
wg-easy container on the host 10.0.0.111/32
Peers are 10.0.0.0/24

wg-easy host can not ping peers. But inside the container shell, can ping peers.

Is there any way to access peers on wg-easy host?

[Pleonazm]

The easiest is to run a container in Network Host mode. The wg0 interface is shared with the host
The host has no access to wg0 interface, and route to 10.0.0.0/24 (only container).
It depends why do you want it.
Can clients reach other clients/server on 10.0.0.0/24 subnet?

[dacianpeng]

Yes, clients can reach other clients/server on 10.0.0.0/24 subnet. Everything is good and expected.

But run a container in Network Host mode is difficult and will produce many bugs.
I want a simple command which will give the host 10.0.0.111/32 too, instead of only the wg-easy container 10.0.0.111/32.

I haven't figured out a way to fix this.

[ghost]

I solved it by simply create a wireguard-interface on the host to connect to the container via local IP address. Works like a charm.

[rambonette]

@Dave-AC1 do you mind showing the steps? was it something done via docker-compose?

[deulizealand]

@Dave-AC1 share the step. so we who need it can follow. thanks

[DMax-YT]

@rambonette @deulizealand I had the same problem so here's my solutions (you need the last one)
https://superuser.com/questions/1824728/how-to-proxy-requests-into-wg-easy-docker-container/1824944#1824944

[deulizealand]

thanks for your reply, i'll try this method asap.