garycnew
Senior Member
All:
I'm in the process of migrating from Asuswrt-Merlin 384 => 388 and noticed VPN Director as an option for VPN Source/Destination Address-Based Split-Tunneling.
In Asuswrt-Melrin 384, I configured my Source/Destination Port-Based VPN Split-Tunneling Rules in the nat-start script as follows:
I just want to confirm that VPN Director is only Source/Destination Address aware (NOT Source/Destination Port aware) and that I should continue using the nat-start script for my Source/Destination Port-Based Split-Tunneling Rules?
Thanks, again.
Gary
I'm in the process of migrating from Asuswrt-Merlin 384 => 388 and noticed VPN Director as an option for VPN Source/Destination Address-Based Split-Tunneling.
In Asuswrt-Melrin 384, I configured my Source/Destination Port-Based VPN Split-Tunneling Rules in the nat-start script as follows:
Code:
iptables -t mangle -I PREROUTING -i br0 -p udp -m multiport --sport 11111,22222,33333,44444,55555 -j MARK --set-mark 0x2000/0x2000
iptables -t mangle -I PREROUTING -i br0 -p tcp -m multiport --sport 11111,22222,33333,44444,55555 -j MARK --set-mark 0x2000/0x2000
iptables -t mangle -I PREROUTING -i br0 -p udp -m multiport --sport 10000:10999 -j MARK --set-mark 0x2000/0x2000
iptables -t mangle -I PREROUTING -i br0 -p tcp -m multiport --sport 10000:10999 -j MARK --set-mark 0x2000/0x2000
I just want to confirm that VPN Director is only Source/Destination Address aware (NOT Source/Destination Port aware) and that I should continue using the nat-start script for my Source/Destination Port-Based Split-Tunneling Rules?
Thanks, again.
Gary