Merlin 384.19 VPN Client - can I direct client connection to specific VPN client?
- Thread starter TomG
- Start date
CaptainSTX
Part of the Furniture
1. Assign devices that you want to use VPN static IPs on the router's LAN.
2. After getting VPN client(s) working on router enable policy based routing.
3. In the rules section in the VPN client select the devices you want to be tunneled through the VPN
4. Click apply and you are done.
eibgrad
Part of the Furniture
As CaptainSTX suggests, you can use PBR (policy based routing) to selectively route devices over the VPN. However, you can't differentiate wireless from wired users for those same purposes.
By default, all the wired and wireless clients are *bridged*, and therefore how any given client entered the network (wired vs. wireless) is lost for all other purposes (DHCP, firewall rules, PBR, etc.). The only way you could achieve this is if you can place the wireless users on their own network, which by definition would require its own unique IP network (e.g., 192.168.2.0/24). Then you could use PBR to route that specific IP network over the VPN. IOW, you can effectively router wireless users over the VPN, but only indirectly, because you *know* that IP network is only available to wireless users.
Of course, placing a subset of your users on their own network, merely for these purposes, has other negative consequences (e.g., network discovery won't work across networks, not unless you also implement Avahi, an mDNS proxy).
By default, all the wired and wireless clients are *bridged*, and therefore how any given client entered the network (wired vs. wireless) is lost for all other purposes (DHCP, firewall rules, PBR, etc.). The only way you could achieve this is if you can place the wireless users on their own network, which by definition would require its own unique IP network (e.g., 192.168.2.0/24). Then you could use PBR to route that specific IP network over the VPN. IOW, you can effectively router wireless users over the VPN, but only indirectly, because you *know* that IP network is only available to wireless users.
Of course, placing a subset of your users on their own network, merely for these purposes, has other negative consequences (e.g., network discovery won't work across networks, not unless you also implement Avahi, an mDNS proxy).
Similar threads
Similar threads
Similar threads
-
Site To Site VPN between Debian VM and AsusWRT-Merlin router, no routes exists
- Started by Freewill0592
- Replies: 2
-
-
-
-
-
-
-
CVE-2024-3661 Attackers can use TunnelVision to snoop on users’ VPN traffic.
- Started by Jacky10X
- Replies: 1
-
-