Hey mate, just wanted to say first up this thing is awesome, usually open source linuxy things just don't work for me but this has been great!
I have a bit of an odd issue at the moment, have only noticed it on latest update to 0.0.1-16. What appears to be happening is if I make a change in the GUI on an existing rule to change which interface it will use, the entry in the PREROUTING chain doesn't seem to get updated. If i restart the vpn-policy-routing service in CLI then it works fine, so it seems at least for me that hitting save in the GUI doesn't actually update iptables.
I can probably put all the config up but an example is as below. I have two nordvpn tunnels setup, tun0 and tun1, which in LEDE are interface names nordvpntun and nordvpntun1 respectively.
What I have done to arrive at the below output is config for kuja working as expected on tun0, then in the GUI I change kuja to use tun1, which updates in /etc/config/vpn-policy-routing but seems nowhere else.
After making the change I would expect the PREROUTING rule for kuja to change from 0x30000 to 0x40000, but this will only happen if I manually restart the vpn-policy-routing service on the CLI.
config vpn-policy-routing 'config'
option verbosity '2'
option strict_enforcement '1'
option dnsmasq_enabled '1'
option enabled '1'
option comment 'Kuja'
option local_addresses '192.168.1.253'
option interface 'nordvpntun1'
Relevant lines from /etc/init.d/vpn-policy-routing support:
32742: from all fwmark 0x40000 lookup 204
32743: from all fwmark 0x30000 lookup 203
IP Route Tables
IPv4 Table 203: default via 10.x.x.x dev tun0
IPv4 Table 204: default via 10.x.x.x dev tun1
-A VPR_PREROUTING -s 192.168.1.253/32 -m comment --comment Kuja -c 5157 717410 -j MARK --set-xmark 0x30000/0xff0000
-A VPR_PREROUTING -m set --match-set nordvpntun1 dst -c 0 0 -j MARK --set-xmark 0x40000/0xff0000
-A VPR_PREROUTING -m set --match-set nordvpntun dst -c 0 0 -j MARK --set-xmark 0x30000/0xff0000