Terrible_Josh
07-28-2002, 03:01 AM
If you play Diablo2 at all, and want to do so in Linux, there's a chance you will run into the WEIRDEST ****ing bug. I think it only happens if you're using NAT. Basically, your computer will start trying to resolve all its hostnames through DNS - and the problem is that it thinks its hostname is [hostname].domain. This hostname doesn't exist and cannot be resolved through DNS because the NAT is in between the hostname and the domain. Therefore, your computer will send THOUSANDS of DNS requests that cannot be answered (the DNS server will just keep answering back that the name cannot be resolved). Now, the weirdest part - it only happens when the game map is on. Yes, you read that correctly. Don't ask me.
I noticed the crappy performance and monitored it with a packet sniffer (ethereal). That's when I noticed that it only occurs when the map is on. I imagine that it has to do with a bug in winex, but I'm not sure. Once I realized it was a name resolution problem, I edited the hosts and lmhosts files to resolve all of the hostnames it was looking up through DNS to an IP address. That way, the computer thinks it has correctly resolved the its hostnames when, in fact, you've just fooled it. It doesn't matter that it can't resolve its hostname anyway, because if you're behind a NAT (and, as far as I can tell, it only occurs when you're behind a NAT) the only thing that addresses your computer is the gateway itself - which already knows your IP address.
I noticed the crappy performance and monitored it with a packet sniffer (ethereal). That's when I noticed that it only occurs when the map is on. I imagine that it has to do with a bug in winex, but I'm not sure. Once I realized it was a name resolution problem, I edited the hosts and lmhosts files to resolve all of the hostnames it was looking up through DNS to an IP address. That way, the computer thinks it has correctly resolved the its hostnames when, in fact, you've just fooled it. It doesn't matter that it can't resolve its hostname anyway, because if you're behind a NAT (and, as far as I can tell, it only occurs when you're behind a NAT) the only thing that addresses your computer is the gateway itself - which already knows your IP address.