http://bugs.winehq.org/show_bug.cgi?id=7929
--- Comment #100 from Erich Hoover ehoover@mines.edu 2009-11-17 11:48:20 --- (In reply to comment #99)
... I compiled wine with your patches and all went well so far.
Great! What distribution are you using? I would like to test converted my Debian packages to RPMs if you're interested in testing.
However I couldn't test LAN support just yet. I tried last weekend and it didn't work, but I think i was having problems with Hamachi since I couldn't see the other player online there, so that might be the cause. Hopefully I will test it again soon.
So you say I don't need to add hamachi's IP on /etc/hosts? No need to route to 255.255.255.255 either?
That's correct. Unless you need to do something with your configuration to get hamachi to work at all then these patches should remove the need to do the old tweaking. Relevant explanations:
/etc/hosts: The patch does a test to see if the loopback IP is returned for gethostbyname("your_computer_name") and if this would be the case then it returns instead the list of IP addresses corresponding to all of the "local" IP addresses. This list is returned based on the routing priority, as it is according to the documentation and under all my Windows testing. So, provided that your hamachi VPN connection has the highest routing priority then that is the IP address that gets returned to the game (you can check this in-game by going to the network settings).
route 255.255.255.255: I never saw this configuration actually work; however, my understanding of the code and this option is that this change allows the game to send to the broadcast address as if it is any old IP. This set of patches should not require such a change as it is setup to do broadcasting "properly."