THANK YOU! You were the only one who was able to explain this to me! I almost thought it wasnt possible in unify which would be pretty weird. Great explanation!
@@MrTimTech2022 well I can ping my nas, and rule is there. I think main problem is different subnet. Is your NAS discoverable from VPN client lets say on Windows pc?
I absolutely cannot get Wireguard or OVPN to work on a Linux desktop client. They work on phones like your video, but can't get to work with network-manager in linux (arch, debian, etc.). Wireguard (unifi) only seems to connect with an ipv6 and OVPN seems to keep prompting for authentication. Just keep popping up. Any ideas?
To be honest I'm not really a techie as far as Linux is concerned, it's been years since I last used/tried Linux. I hate to redirect you to other channels but I wonder if Tom over at Laurence Systems might assist if you post a comment (ruclips.net/channel/UCHkYOD-3fZbuGhwsADBd9ZQ) I hate not being able to provide help on a solution but I think on this one I'm not able, sorry 😟
Very clear video, but one question. At ruclips.net/video/eUfeL1KgoiI/видео.html it looks like you block all LAN traffic, not just with the Wireguard VPN.
No it's only blocking Inter VLAN traffic, not LAN traffic. So it just stops Wireguard VPN traffic from accessing other VLANS on my network. The Wireguard client can only access certain VLANS or devices using the rules I create. Hope that makes sense.
@@MrTimTech2022 Same question here, I was thinking the same. You're blocking all possible internal IP's from connecting to each other if I understand correctly? Or does it have something to do with the 'LAN IN' option you are choosing?
THANK YOU! You were the only one who was able to explain this to me! I almost thought it wasnt possible in unify which would be pretty weird. Great explanation!
You're very welcome lofiplays_live - glad you were able to set this up using my instructions. Thanks again, your feedback is much appreciated.
Brilliant !! Clear and easy. Thank You so much.
Glad you liked it! - You're very welcome!
Great job on the firewall settings will be watching out for more stuff
Hey Tony, thanks very much, I appreciate your kind words. Certainly I will be doing further videos
Thanks for the video. It helped me a lot.
Hey Daniel - You're most welcome. Glad it helped you out, let me know if there's anything else I can assist with (video wise)!
Worked well, but NAS and VPN client are on differenet subnets x.x.1.x and x.x.2.x, so NAS is not discoverable
I think you would have to create a firewall rule to allow inter LAN traffice between the static IP of your NAS and the VPN client range.
@@MrTimTech2022 well I can ping my nas, and rule is there. I think main problem is different subnet. Is your NAS discoverable from VPN client lets say on Windows pc?
I absolutely cannot get Wireguard or OVPN to work on a Linux desktop client. They work on phones like your video, but can't get to work with network-manager in linux (arch, debian, etc.). Wireguard (unifi) only seems to connect with an ipv6 and OVPN seems to keep prompting for authentication. Just keep popping up. Any ideas?
To be honest I'm not really a techie as far as Linux is concerned, it's been years since I last used/tried Linux. I hate to redirect you to other channels but I wonder if Tom over at Laurence Systems might assist if you post a comment (ruclips.net/channel/UCHkYOD-3fZbuGhwsADBd9ZQ) I hate not being able to provide help on a solution but I think on this one I'm not able, sorry 😟
I thought vpn rules needed to be created under LAN Out?
These rules are for incomming connections for connecting to the UDM which is being used as a VPN server.
Very clear video, but one question.
At ruclips.net/video/eUfeL1KgoiI/видео.html it looks like you block all LAN traffic, not just with the Wireguard VPN.
No it's only blocking Inter VLAN traffic, not LAN traffic. So it just stops Wireguard VPN traffic from accessing other VLANS on my network. The Wireguard client can only access certain VLANS or devices using the rules I create. Hope that makes sense.
@@MrTimTech2022 Same question here, I was thinking the same. You're blocking all possible internal IP's from connecting to each other if I understand correctly? Or does it have something to do with the 'LAN IN' option you are choosing?
I changed the rule "from RFC1918 to RFC1918" to "From WireGuard VPN to RFC1918"
@@emperorblade It just stops clients connecting via wireguard from accessing other VLANS on your local network.