litlec wrote:
Hi KevinZ,
Thanks for your response.
My problem isn't traffic is heading to the wrong interface but with the route NeoRouter takes to when initiating its login connection to the server.
Once my VPN is connected, all traffic is sent via that TAP 'virtual' interface, which under normal circumstances is great and the intended outcome to hide my traffic from my ISP. Unfortunately this is causing latency when NeoRouter is connecting over the VPN.
So basically I have a tunnel within a tunnel and packets are taking far too long to get to their destination. This is more of a problem with my VPN provider who I wont be renewing my subscription with next year, but until then I need a work around.
What I am trying to figure out is if it is possible to bind the NeoRouter application to the physical Gigabit interface so all NeoRouter traffic is sent over it and it does not touch the VPN.
The solution could be something as simple as putting static routes to all NeoRouter IP addresses in the Windows routing table or maybe a line of config in an XML/config files NeoRouter uses but I am not sure what those settings might be.
Any advise is appreciated, thanks
Can you see if you can login to Neorouter FIRST, then connect to VPN and see if the Neorouter traffic stays off the VPN?
Also, from a command prompt, can you paste the output of "route print" when connected to VPN and Neorouter? That will give a better idea of what's happening. I think the best chance of a workaround is using the Metric allocation.