It is probably a result of a routing command being pushed from your VPN server.
There should have been a change to the Vero4K kernel in the latest (January) update that added support for multiple route tables, which might have helped. Unfortunately, it doesn’t seem to have made it into the build.
Even on the latest version, adding a separate routing table gives a similar message: RTNETLINK answers: File exists.