http://bugs.winehq.org/show_bug.cgi?id=15711
Erich Hoover ehoover@mines.edu changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |ehoover@mines.edu
--- Comment #6 from Erich Hoover ehoover@mines.edu 2009-09-28 19:21:23 --- (In reply to comment #4)
Edit your /etc/hosts file to not assign 127.0.0.1 to your hostname.
We been here before this is a won't fix. The bug is in system configuration. Everything that could have been fixed in Wine is fixed.
I've been looking into this issue (from a usability perspective it affects some other things I'm working on), and it can be fixed without forcing users to continually edit their /etc/hosts file. First, a knowledge base article on how they intended this "feature" to work: http://support.microsoft.com/kb/160215
As a result of reading that article a light-bulb went off for me, this command is intended to return all the addressable IPs (or in unix parlance, the IP associated with each unique route) in order from highest to lowest priority. So, after digging through RTNETLINK a bit I was able to create a small example application that does this (obtains each unique route and gets the associated IP, though RTNETLINK reports routes from lowest priority to highest). I believe that this is a legitimate route to obtain the behavior desired by Windows without forcing users to edit their /etc/hosts file every time their IP changes. If this sounds acceptable then I can whip up a patch that will do this if Wine would otherwise have reverted to the "magic IP."