Asus Merlin - bug/change in latest firmware (380.64_2)?

[webreaper]

Just wanted to mention, I upgraded to the latest firmware today (I was on 380.63, and upgraded to 380.64_2) and found a small problem (more quirk, really).

I have policy routing set up on the router, so that NAS traffic (primarily downloads) goes through my Netherlands-based OpenVPN client, and then the remaining clients on the LAN use a London-based OpenVPN client/endpoint. There's also a couple of devices which go straight to the WAN and avoid the VPN altogether.

I have two devices, which I'd named as "Jim's MacBook pro" and "Jim's S7 Edge", and today I suddenly noticed they were returning google.nl when I did a network search. After a bit of rooting around, it turned out the policy routing was not working - it was sending them to the second OpenVPN client - despite having routing rules set up to direct them to the first. I played around with the settings, and it turns out that removing the space and apostrophes from the device names made it all come good again.

So everything is working as expected. Is it possible this issue was introduced as part of the OpenVPN upgrade?

Anyway, I'm back up and running, but it might be worth adding validation into the client name fields so apostrophes aren't allowed?

 

[Dezzo]

I also run OpenVPN client on 64_2 and have had some odd quirks as well.

Even though my OpenVPN client is using Client 3, I see entries in the log such as "Adding route for 192.168.xxx.xxx to 0.0.0.0 through VPN client 1" for most of the devices on my policy routing list. However, two recently added devices are shown in the log as being routed correctly through Client 3.

Also, every time I make a change to the VPN settings (usually the policy routing table) I will get "Routing Conflict" warning errors on the VPN status page until the router is rebooted.

This only started happening recently.

The only thing I changed was that I moved my VPN from Client 1 to Client 3.
I manually created Client 3 and restored Client 1 to defaults during this process.

I'm thinking something became corrupted somewhere, yet things appear to be working normally otherwise.
I really can't handle another factory reset at the moment so I'm hoping it's a bug that will be fixed in the next release.