[Bug 53499] GetAdaptersInfo returns loopback interface while it should omit it
WineHQ Bugzilla
wine-bugs at winehq.org
Thu Aug 4 08:17:22 CDT 2022
https://bugs.winehq.org/show_bug.cgi?id=53499
--- Comment #7 from Hans Leidekker <hans at meelstraat.net> ---
(In reply to Stanislav Slow from comment #5)
> (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
No but in the source you pointed out loopback interfaces are skipped. Running
the iphlpapi tests also confirms it.
> 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
You should try to figure out where this ID comes from. Is it a MAC address? In
that case I would expect an all-zero ID if for the loopback address. Perhaps a
+relay trace will tell us more.
--
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.
More information about the wine-bugs
mailing list