[Bug 53499] GetAdaptersInfo returns loopback interface while it should omit it

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=53499

--- Comment #5 from Stanislav Slow <stanislav.rimsha at gmail.com> ---
(In reply to Hans Leidekker from comment #4)
> (In reply to Stanislav Slow from comment #3)
> > (In reply to Hans Leidekker from comment #2)
> > > ipconfig uses GetAdaptersAddresses(), which does include the loopback
> > > interface on Windows.
> > 
> > No problem with the ipconfig showing the loopback interface. I only added
> > the ipconfig info to show that the loopback is considered an ethernet
> > interface. Which might be the issue in the first place - it's not being
> > skipped because wine sees it as ethernet and not loopback.
> 
> But GetAdaptersInfo() (which is called in your log) doesn't include the
> loopback interface.

Can you tell that from the log? You might be right because I don't have any
direct proof for that. I only get an issue that all Wine clients on LAN
identify themselves with the same ID which is likely to be the hardware address
of the primary interface, while windows clients can distinguish themselves with
no problem. The only difference in the network configuration is the presence of
the lo interface on linux machines. There were similar issues reported earlier
in other dlls: https://bugs.winehq.org/show_bug.cgi?id=40247#c13

I can't tell exactly from the application log where does it get the id to use,
previous logs from wine-5.0 showed only the GetAdaptersInfo calls and winsock
bindings to interface indexes that were implying there 3 interfaces total,
while there are only 2 physical and one loopback. I somehow sticked to the idea
that GetAdaptersInfo even after updating to 7.14 and seeing the same behavior.

I'm adding wine-5.0 log for the same application, maybe you could point me to
the right direction then?

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.