sswany

Members
  • Posts

    1
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

sswany's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Having the same issue, but not quite sure where to go from here. I use Pi-hole through Docker on br0 with its own IP address (10.0.1.7). Adding a static route to the Unraid IP (10.0.1.5) allowed me to access external domains using Remote Tunneled Access but only with an external DNS server set in the Wireguard profile. I can access all other LAN IPs on the network except for the Pi-hole IP. If I use my router IP (10.0.1.1) for DNS, it still works, but I get DNS leaks (I'm assuming its because the primary DNS IP for Pi-hole that's set is failing so its falling back to the external secondary). ** Edit: Read up on the other Wireguard thread and tried using a VLAN for Pi-hole to fix the issue. Looks like everything is working on a remote client (using iOS to test) and can access all Docker IPs remotely. In case this helps anyone else, thought I'd post screenshots. Unraid network settings for VLAN: Unraid Docker settings after setting that up: Unraid Pi-hole settings (I also set the "ServerIP" variable to the same and left "INTERFACE" variable as eth0): Unifi Static route: Unifi VLAN settings: Wireguard client settings: I'm no expert on this stuff, but from what I got from the other thread and setup here, it seems to be working and the IP shows as the Unraid/home network when accessing external domains when Wireguard is turned on.