Route added to wrong interface for ethernet but not wifi

I have an eWon Cosy in the field, and I am trying to connect to my devices on its LAN. I can make a remote connection to it using eCatcher. However, when I establish a connection using the ethernet adapter on my remote PC, I cannot ping any of my devices on the eWon LAN. On the other hand, when I establish a connection using the Wifi adapter on my remote PC, I can ping my devices on the eWon LAN. By looking at the log file and route table on my PC, and I was able to determine that when using Wifi on my PC, a route was added using the correct interface for the TAP adapter. But when I use ethernet on my PC, the route is added using my ethernet interface instead of my TAP adapter. If I manually delete the route and add it back using the TAP adapter, I can now ping all of my devices while using ethernet on my PC. Why does this happen? Is there a way to fix this without having to manually delete and add the route every time?

Topic closed due to inactivity.