This is not a MUST-HAVE but would be very nice to avoid configuration issues when changing connection or using the system outside the tunnel. Nevertheless I can still not reach it via the dyndns name. Then I added the same rule for wg0 (phone) and can also reach it via phone from inside the tunnel via IP. I added the routing rule you suggested (variated it for only allowing the one IP of my pi) and it works nice. Forget my thoughts about mullvad (the thing where you just were "?"). So I thought it would be possible to access it via my DynDNS name. I was not able to access the Nextcloud via IP from inside my network. Okay, I see your questions and confusion and try to make things a little clearer.Īt the moment there are two open problems. So this the reason, why I can not choose it as an DNS server and have to chose the router as DNS and also see no adbocking on the phone when I disable the openwrt adblocking (since all DNS request from the phone run NOT over the pihole). After some more research I found out, that I can only use/ping it when I am in the LAN/WLAN, not when I am coming from the phone tunnel. I guess this is the same problem as with the PiHole. But why I can not go from my PC/Phone over Mullvad, use their DNS, look for my DynDNS IP and come back over the internet into the WAN port? All I found online was to activate NAT loopback, this is enabled for the port forwardings. Since it is in another VLAN it is clear that I can not reach it by IP. But I can not reach it anymore from the inside. Reaching it from outside (Phone LTE, no tunneling) works perfectly. I connected it to the VLAN without Mullvad. This is just a raspi with DynDNS and port forwarding. When connected to my router with the new fancy setup of two VLANs and two tunnels I can not reach my nextcloud anymore.
I found a new issue (might be the same as with the DNS things):
Nevertheless it is with focus on my system now, described above.
Please tell me if I should open a new ticket, since the original question was answered.
0 kommentar(er)
