Pico

Hi, I decided to go with a fresh start to see what could be the issue. I disabled bounding in the network settings since I don't have a use for it, removed the Dynamix WireGuard plugin, removed the WireGuard config folder on the USB and set up everything from scratch. After configuring my phone, everything worked as expected (Tunneled and/or LAN)! 😀 I setup WireGuard as part to the RC of 6.8. That probably messed things up somewhere 🤔 With Unraid 6.8.1 and a fresh version of the Dynamix WireGuard plugin (2020.01.17a), it solved the issues I were having. Maybe that will help someone in the future.

When I did this test, the phone was connected to 4G/LTE (so different network entirely) with the WireGuard VPN turned ON – I could access the UnRaid server using both IPs: 192.168.0.13 for LAN or via WireGuard's subnet at 10.42.0.1 (I believe phone is at 10.42.0.7). All physical devices are on 192.168.0.0/24 subnet since I have only one router (Ethernet/Wi-Fi) for the entire house. The UnRaid server is at 192.168.0.13 on this LAN (Ethernet / eth0). I am trying to remotely access using the WireGuard VPN, devices on this subnet.

Hi, first of all, awesome work on Unraid and implementing WireGuard within it! I am able to connect remotely (with LTE/4G or separate Wi-Fi) without issues. I can access my UnRaid server and some Docker containers (in `host` mode). I am however stuck on making `Remote access to LAN` or `Remote tunneled access` work. When I am connected with my phone (or a test PC connected on another Wi-Fi network) I can't access any of the LAN devices. With `Remote tunneled access` I can't reach any website. I updated the config on my phone every time I made changes on Unraid. I did a `ping -t 1 192.168.0.1` on my phone using ADB to see what's wrong and emulate the `traceroute` command. This is the IP of my router (home LAN) that I can normally ping from any device connected to the LAN. The UnRaid server is at 192.168.0.13. I configured the WireGuard server to use the range `10.42.0.0/24` for peers. I see that the ping returns `10.42.0.1` which is the IP of the WireGuard server. It seems correct up to that point. Then I run `ping -t 2 192.168.0.1`. Here all packets are lost. I cannot go any further than the WireGuard server. Probably explaining why `Remote access to LAN` or `Remote tunneled access` don't work. I have `Local server uses NAT` (WireGuard), `Enable bridging` and `Enable bounding` (Network settings) all set to `Yes`. Does someone know where this could come from?