(Sorry for the delay. One of the most interesting aspects of the community forum is the opportunity to learn 'new things' about networking - at least new to me!)

My earlier comment was exactly backwards. iOS and Android support only the tun interface for OpenVPN. (Internet searches will turn up lots of articles comparing tap vs. tun, with pros and cons for both.)

The key to the present situation is that with the tun interface, there is a static route on the Orbi which knows how to get from the VPN IP subnet to the Orbi primary LAN IP subnet. Any packet destined for a LAN IP will get there. Any packet not specifically sent to a LAN IP address will not. That reserved multicast IP address (224.0.0.251) is not intended for the 10.1.0.x subnet, so it does not go there. (and thus no device responds "Here I am at IP 10.1.0.xxxx")

In addition to iOS and Android not supporting VPN over tap, there appear to be similar restrictions on MacOS:

https://tunnelblick.net/cTunTapConnections.html

On Windows, the solution would be relatively simple: modify the hosts file with entries for these devices. Surely there cannot be very many of these devices that respond to Bonjour. Alas, I have spent some time searching two topics and come up with nothing:

tap VPN interface for iOS
Modiify hosts file file in iOS
(Actually, Windows supports the VPN tap interface already, so either method would work.)

Sorry to have failed to come up with a solution.

Forum Discussion

A7000 runs at usb 2.0 speeds when connected to usb 3.0