<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>
Thank you very much Joker, for your answer.<div><br></div><div>After my post, I got around iptables a little further and I figured it out... What happened is that when I opened the UDP port through iptables, I hadn't yet figured out that my router had an intrusion detection system, which detects the connection as a UDP flood... So, by that time, when I opened the UDP port on the box, the intrusion detection was on, and I wasn't checking the traffic through wireshark then, as I did more recently.</div><div><span style="font-size: 10pt; "><br></span></div><div><span style="font-size: 10pt; ">I apologize for the "spam" I caused, but I really been around this for last couple of weeks! Thankfully, it's fixed now.</span></div><div><span style="font-size: 10pt; "><br></span></div><div><span style="font-size: 10pt; ">Thank you for the support.</span></div><div><br><div><div id="SkyDrivePlaceholder"></div><hr id="stopSpelling">From: wynne.garland@hotmail.com<br>To: cod@icculus.org<br>Date: Wed, 18 Jan 2012 03:47:31 +0000<br>Subject: [cod] Call of Duty 4 Server - Public IP access doesn't work ("Awaiting connection")<br><br>
<meta http-equiv="Content-Type" content="text/html; charset=unicode">
<meta name="Generator" content="Microsoft SafeHTML">
<style>
.ExternalClass .ecxhmmessage P
{padding:0px;}
.ExternalClass body.ecxhmmessage
{font-size:10pt;font-family:Tahoma;}
</style>
<div dir="ltr">
Hi, <b>cod@icculus.org</b>.<div><br></div><div>I'm setting up a Call of Duty - Modern Warfare server on an Ubuntu 10.04 box, using the latest version of this Linux port of the server (I think), <font face="'Courier New'"><em style="font-size:small;font-style:normal;line-height:16px;background-color:rgb(255, 255, 255)">cod4</em><span style="color:rgb(34, 34, 34);line-height:16px;background-color:rgb(255, 255, 255);font-size:10pt">-linux-</span><em style="font-size:small;font-style:normal;line-height:16px;background-color:rgb(255, 255, 255)">server</em><span style="color:rgb(34, 34, 34);line-height:16px;background-color:rgb(255, 255, 255);font-size:10pt">-06282008</span></font><span style="font-size:10pt">.</span></div><div><br></div><div>The problem is simple to grasp: every time someone tries to connect to my box using my public IP, it just says "Awaiting connection", although the exact same setup works using the Windows version.</div><div><br></div><div>What I'm doing/already tried:</div><div>I'm forwarding the 28960 UDP port traffic to my Ubuntu box (through the router configuration system), and I know this is working because I see the traffic of my friends trying to connect getting to the box, with the server providing no answer. If I do it using the server's local network IP, it shows the traffic being replied and my friends do connect, as usual. My router has a firewall and an intrusion detection system (Thomson TG784), both of them were shutdown during every attempt, to make sure no security mechanism is blocking the traffic (and, as I said, I'm sure the box is receiving the external incoming packets, exactly the same way it receives the local ones).</div><div><br></div><div>When I set <font face="'Courier New'">dedicated</font> as 2, it says "dedicated is read only"; I read it somewhere that it already defaults to 2, so it should be correct.</div><div>I was not setting <font face="'Courier New'">net_ip</font> value; I read that it defaults to 0.0.0.0, so it should be listening on all interfaces (although local network traffic and external network traffic are coming through the same interface, but just to be sure...). I also tried setting it to the local IP and to the external IP. Nothing worked.<br><br></div><div>It gives me an error when trying to bind to the external IP; that's because it connects to a router that connects it to the Internet, no interface has that IP binded. I saw many people on the web saying that binding to the external IP is not exactly correct, so every attempt I make I use 0.0.0.0, just to be sure.</div><div><br></div><div>Is there any need to set some special rule on iptables? I've been tinkering with some rules, SNAT and DNAT essentially, mangling the packets so they appear to come from the internal network.</div><div><br></div><div>I've tried everything, googled a lot about my router and my setup, tried searching similar problems with people using the Linux version of the server... A person or two seem to have my problem, but all problems were solved by correctly forwarding the port.</div><div><br></div><div>Today I got a friend of mine to successfully connect to the Windows version of the server using the external IP, dismissing any thoughts that the router could be the problem.</div><div>I'm sure it must be something I'm forgetting to check.</div><div><br></div><div>I'd appreciate your help. If you need any kind of information to help me solve my problem just ask, I'll gladly provide anything I can.</div><div><br></div><div>Thank you very much in advance.</div> </div>
<br>_______________________________________________
cod mailing list
cod@icculus.org
http://icculus.org/mailman/listinfo/cod</div></div> </div></body>
</html>