RT-BE88U everything going over VPN.

[Ripshod]

Got this today and immediately installed Merlin 3001.102.3. Initial setup has gone very well, as well as adding my normal lineup of addons. 5 devices are currently connected on the IoT network with VPN activated, yet absolutely everything is going through the vpn. Have I missed something, a thread on these forums? Can I be so wrong?

 

[Tech9]

No idea what's wrong with your VPN, but enjoy your new router.

 

[biker3]

Hi Ripshod,
What kind of VPN are you using? Have you defined some rule in VPN Director?
By default all traffic is going over WAN.
I've the same router with same Merlin version and I get problems with Wireguard, but in case of OpenVPN everything goes well.
Regards

 

[Ripshod]

I'm running openVPN(Nord). I tried with rules in VPN Director (and also with rules directing everything else to WAN), but from what i understand as the Iot network is directed to VPN I shouldn't need to set up the individual devices. I did notice with the 3004 firmware that Guest devices were given their own subnet, but with this new router both the main and IoT networks share the same subnet.
*edit* Speedtests from the router go out through WAN, while speedtests from my notebook go out via VPN. I must have made a silly mistake with the settings somewhere but I just don't see it.

 

[biker3]

I had to remove the IoT default network and create a new one to can choose a new VLAN for it.
In addition, from my point of view, if you wan to be able to choose what source or destination from IoT goes over VPN and what not, you should disable this in the IoT network:

and use VPN to create rules depending on source and/or destination, even CIDR format.

 

[Ripshod]

I had to remove the IoT default network and create a new one to can choose a new VLAN for it.
In addition, from my point of view, if you wan to be able to choose what source or destination from IoT goes over VPN and what not, you should disable this in the IoT network:
View attachment 63585
and use VPN to create rules depending on source and/or destination, even CIDR format.

Why would they do it like that when (allegedly) setting a vpn on the IoT network would be enough?
Anyways, this little bit of info has got things working as they should now. Thank you @biker3