Random Join Problem (RESOLVED)

Technical Support for all Defcon related issues

Moderator: Defcon moderators

Talesin
level4
level4
Posts: 875
Joined: Mon Oct 15, 2001 4:15 am
Location: Burbank, CA, USA

Random Join Problem (RESOLVED)

Postby Talesin » Sat Sep 30, 2006 1:42 pm

I can join games cleanly and play or spectate about 20% of the time, and have hosted a server once, so I'm relatively sure that my networking settings are correct.

About 80% of the time when I try to join a game though, the 'connecting' bit hangs and keeps retrying, with the progress bar at 50%. Very rarely I will get a 'connected' and it will proceed to 'Downloading', but the bar moves exceptionally slowly, expecting anywhere from 5 minutes to download all the way to 280-something. It does keep beep/chirp/pinging during all of this.

Anyone have ideas? My Client port is 10005, Server is 10007, meta is 5009 (tried it on 10009, made no apparent difference). 10001-10010 UDP/TCP are DNAT forwarded through a Linux NAT box.
Last edited by Talesin on Sun Oct 01, 2006 7:03 pm, edited 1 time in total.
Freyar
level2
level2
Posts: 152
Joined: Sat Sep 30, 2006 1:16 am

Postby Freyar » Sat Sep 30, 2006 1:44 pm

You found servers that work, correct?

Generally they are mis-configured servers that give you the problem you are getting.
Talesin
level4
level4
Posts: 875
Joined: Mon Oct 15, 2001 4:15 am
Location: Burbank, CA, USA

Postby Talesin » Sat Sep 30, 2006 9:26 pm

I've joined two servers total, and spent a good three hours trying to connect to any others. I've tried with almost empty servers, and 5/6 servers all with the same result... no dice. I've also had friends try to connect to a game I start, and they have the same problem of being unable to connect, though they apparently can join other games without any kind of problem.
Talesin
level4
level4
Posts: 875
Joined: Mon Oct 15, 2001 4:15 am
Location: Burbank, CA, USA

Postby Talesin » Sun Oct 01, 2006 7:02 pm

Problem resolved. For anyone using a Linux NAT who is having problems still, here's how I fixed my connection problem (most of the time).

Set Port Forwarding enabled in the Networking options within Defcon. Set your preferred ports.
For those using IPTables rulesets still, add the following:

iptables -t nat -A PREROUTING -s ! [your LAN IP address here] -p udp --dport [starting port]:[ending port] -j DNAT --to-destination [your IP address here]
iptables -t nat -A PREROUTING -s ! [your LAN IP address here] -p tcp --dport [starting port]:[ending port] -j DNAT --to-destination [your IP address here]

This essentially forwards the TCP/UDP ranges to your machine, originating from any machine other than your own. For added security, simply netmask off your LAN IP range so only externally originating requests get re-routed to your machine.


As an example, here's my ruleset:

iptables -t nat -A PREROUTING -s ! 192.168.1.4/255.255.255.0 -p udp --dport 10020:10022 -j DNAT --to-destination 192.168.1.4
iptables -t nat -A PREROUTING -s ! 192.168.1.4/255.255.255.0 -p tcp --dport 10020:10022 -j DNAT --to-destination 192.168.1.4

And my port forwards are set to 10020, 10021 and 10022, with my gaming machine's IP being 192.168.1.4.
Apparently I was having problems because the OUTGOING communications from Defcon were being 'bounced' back by the IPMasq. This ruleset solves that.

Return to “Windows Troubleshooting”

Who is online

Users browsing this forum: No registered users and 4 guests