Re: [PATCH 0/1] MR9769: nsiproxy.sys: Assign the highest metric value to loopback adapters.

[Paul Gofman (＠gofman)]

I am going to do a bit of tests around that. As that looks a bit weird to me, in principle interface or route metric estimates a cost of interface or route connection, why would it be maximum for loopback interface? The issue is complicated by the fact that Windows distinguishes route and interface metrics while the latter is mostly unsupported on Linux, and in nsi / iphlpapi we sort of establish equivalence between the two. So potentially different things may go wrong here.

Do we know exactly what the app calls and what depends on? Is that adapter order from GetAdapterAddesses or maybe metric attribute itself?

-- 
https://gitlab.winehq.org/wine/wine/-/merge_requests/9769#note_125809