You're referring to this, right? I've tried it but I still can't get a connection.
Is there a reason to ignore the br-lan interface? This might work if there are no other interfaces and the internal traffic in lan is not hitting the router. If there are other interfaces and we want inter-interface traffic, they must be in the both in the custom routing tables.
For example br-lan is 192.168.1.0/24 and br-iot is 192.168.2.0/24, we make a policy for lan via wan and iot via vpn. They will be assigned to different routing tables, but this was there won't be communication between them.
1 Like
Got the same suggestion from @vgaetera. Could you gentlemen please help test this version, which has the suggested fix: https://repo.openwrt.melmac.net/vpn-policy-routing_0.3.2-2_all.ipk
If you're using WebUI you may have to update that too: https://repo.openwrt.melmac.net/luci-app-vpn-policy-routing_git-20.358.64958-f3417f2_all.ipk. Since the luci packages naming was changed recently, you'll have to manually grab the IPK as the opkg update from my repo may not work.
2 Likes
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.