fratrue
-
Posts
2 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by fratrue
-
-
Hi!
I have set up a Pi-hole docker with a macvlan custom network. The ultimate goal is to reach the Pi-hole instance both from my local LAN and from Wireguard clients connected to the unRAID server.
Network details:
unRAID IP: 192.168.0.3
Pi-hole IP: 192.168.0.129
Gateway: 192.168.0.1
The issue is that, while macvlan appears to work and I can reach the Pi-hole instance from my LAN, I can't access it from unRAID or any Wireguard clients connected to it.
root@unRAID:/mnt# ping 192.168.0.129 PING 192.168.0.129 (192.168.0.129) 56(84) bytes of data. From 192.168.0.3 icmp_seq=1 Destination Host Unreachable From 192.168.0.3 icmp_seq=2 Destination Host Unreachable From 192.168.0.3 icmp_seq=3 Destination Host Unreachable
I have enabled Host access to custom networks under Docker settings and even turned it on and off a few times but no differences.
Thanks!
Cannot reach docker container over macvlan
in Docker Engine
Posted · Edited by fratrue
Looks like this was due to Host access to custom networks not working immediately with user-defined custom networks. I had to enable a "br0" custom network in the GUI and then the server started to reach the containers with custom IP.
However, now I have the issue that Wireguard clients can no longer reach LAN IPs. I have set NAT to Off and added the requested static route in my router but unfortunately if doesn't work.
Any tips? Is this kind of setup supposed to work?
Thanks!