I have two routers connected like this:
R1 (v7.22.3) ---- IPIP ---- R2 (v7.22.3)
There is an IPIP tunnel between R1 and R2, and on R2 the IPIP interface is placed inside a VRF.
Because of this, bandwidth-test and speed-test are not working.
Is there any solution or recommended workaround for this setup?
It seems indeed that the bandwidth "tool" does not allow "vrf aware" config settings, hence it will operate (only) within the default routing domain.
Why are you using VRF here ? Do you have overlapping IP-space that you need to counter ?
Technically you could think about some (static) route leaking between VRF's on both sides ? But if overlapping exists then NAT is needed etc,etc.
I’m pretty sure this was working fine in v6.
And yes, in this case I do need to use VRF.
I’m aware of options like route leaking, etc., but they don’t really fit my use case. Even if they did, they still wouldn’t resolve the issue with the bandwidth-test tool itself.
Perhaps add this as a feature request??
Dont use logic like, it was working on versionXX but now its not working.
Seems like people here dont believe in logic 
I’m about to raise the Supir ticket , I was just wondering if I might be missing something config-related.
ticket SUP-216464
from the support: Bandwidth test currently can work only on main table.
have you tested?
there is no option vrf in the line
Yes I tested and it works for both /tool/speed-test and /tool/bandwidth-test. But you have to use the CLI, WinBox doesn't have support for it yet.
On the CLI you add @VRF_name to the end of the hostname or IP address in the address= parameter (see screenshot above), for example:
/tool speedtest address=test.example.com@myVRF
that works,
basically that is from VRF -> main table.
doesn't work VRF to VRF.
Yes the changes are for the client side. The btest server has no setting to bind it to a specific VRF yet.
Honestly, I prefer that the services (server side) in RouterOS don't listen on a specific VRF but on all of them. It would much more useful. Like the built-in DNS resolver for example: Currently you have to specify a VRF interface for it and it can no longer serve as DNS server for the other VRFs, which is a bummer.