Of proxies, NATs and more.

image

I recall someone saying that it would take many months for someone to develop, from scratch, their own client/server proxy system and even then, the publisher couldn’t do it because it would require changes to the game.

37,138 views 22 replies +1 Loading…
Reply #1 Top



In your faces!


End of quote

 

k1  

Reply #5 Top

Quoting carpwrist, reply 4
i wish the TF2 updates hadn't gone live this week, i'm very torn between games now

 
End of carpwrist's quote

Heh, know what's funny though? Demigod works great for me and TF2 (since the new spy/sniper update) isn't working at all.

Anyways, Great job Stardock and Frog as well as GPG. Keep it up guys, being a college IT student, I'm beginning to understand how complex networking really is. You guys are doing great, keep your heads up, and learn form the experience, so that when Demigod 2 comes around it will be perfect. :D XD :blush:

Reply #6 Top

So when are the proxies available? Already or in the next few days, any ETA? Thanks.

Reply #7 Top

The proxies make a huge difference. I've played 3 games so far, where people had to use proxies. I also like that I can see ho people are connected.

Reply #8 Top

Appreciate your hard work and honesty about the situation frogboy

Reply #9 Top

i can still connect like not at all...

why worked everything fine before patch 14/5 and after that not at all...

even when i open ports remove my router and turn off firewall i get "can not connect to NAT".

ohh yeah and the proxy thing does not work aswell i get the error even faster with that option on tho... when i can not connect i guess i can not connect to any numbers of proxy servers because the way u connect to them is the same...

Reply #10 Top

Love the proxies. It allowed me to play with one of my friends that I haven't been able to play with yet.

Reply #12 Top

You really need to to do something about bad pathfinding and the don't move/don't attack/don't cast bug.

Reply #13 Top

You really need to to do something about bad pathfinding and the don't move/don't attack/don't cast bug.
End of quote

We've reported that to GPG.  But once you're in that lobby, our part is over. :)

Reply #14 Top

:star: i've been connecting with people i haven't been able to connect to before. Keep up the good work

Reply #15 Top

great job! thanx, now we're gonna rule the multiplayer world :)

Reply #16 Top

Great job, will 'test' this today

and ofcourse a wish :-):
Would be nice to be able to set commandline parameters within Impulse

Reply #17 Top

the program is still using more ports then I configured in ImpulseReactorOptions.exe

only workaround for now, is for me to open ALL ports to my internal IP.

Please fix that, and everything would be fine. Opening ALL ports should normally not be necessary....

[05-22-2009 11:34:57 156] Connected to facilitator at 209.124.63.249:6004.  My External: 92.227.119.116:10592  My Internal: 192.168.1.2:6002 (CONNECTION ACTIVITY)

People do connect to my external IP Adress right?

Vashan

Reply #18 Top

I recall someone saying that it would take many months for someone to develop, from scratch, their own client/server proxy system and even then, the publisher couldn’t do it because it would require changes to the game.
End of quote

To do it properly it could take several months, because now it is STILL NOT WORKING AS IT SHOULD!!! As before, almost everyone can connect to me, but I still have difficulties to connect to other players, even with proxies. And if I don't put the /serverproxyonly, he doesn't seem to take the initiative to do it himself.

What remains weird is that I can't use the impulsereactor configuration, because he can't find the NAT facilitator if I do!

Where can I send my log files to investigate or where can I get a refund?

PhXDragon

Reply #19 Top

Quoting Vashan, reply 17
the program is still using more ports then I configured in ImpulseReactorOptions.exe

only workaround for now, is for me to open ALL ports to my internal IP.

Please fix that, and everything would be fine. Opening ALL ports should normally not be necessary....

[05-22-2009 11:34:57 156] Connected to facilitator at 209.124.63.249:6004.  My External: 92.227.119.116:10592  My Internal: 192.168.1.2:6002 (CONNECTION ACTIVITY)

People do connect to my external IP Adress right?

Vashan
End of Vashan's quote

Your router must be setup with Symmetric NAT which causes a port to be randomly picked (10592 in your case) when it leaves the router. I don't know if demigod trys to connect back to this port for its direct connection attempt (instead of the open range 6000-6200 for example). I suspect it does, as I had a router that was doing as yours was and had to forward all ports to get demigod to work 100%.

I have since swapped out my Symmetric NAT router for an older one i had that i think is using CONE NAT, i now get the same external port in the impulse reactor log as my internal port. With this router i only have to open the 6000-6200 range to connect without problems.

Perhaps demigod should send the port the internal client is listening on within the connection packet, and ignore the external port number the router has allocated (to take advantage of people forwarding ports). If a direct connect on this port fails, then try doing a NAT punchthrough via the port from the router.

Reply #20 Top

Quoting Rocah, reply 19



Quoting Vashan,
reply 17
the program is still using more ports then I configured in ImpulseReactorOptions.exe

only workaround for now, is for me to open ALL ports to my internal IP.

Please fix that, and everything would be fine. Opening ALL ports should normally not be necessary....

[05-22-2009 11:34:57 156] Connected to facilitator at 209.124.63.249:6004.  My External: 92.227.119.116:10592  My Internal: 192.168.1.2:6002 (CONNECTION ACTIVITY)

People do connect to my external IP Adress right?

Vashan


Your router must be setup with Symmetric NAT which causes a port to be randomly picked (10592 in your case) when it leaves the router. I don't know if demigod trys to connect back to this port for its direct connection attempt (instead of the open range 6000-6200 for example). I suspect it does, as I had a router that was doing as yours was and had to forward all ports to get demigod to work 100%.

I have since swapped out my Symmetric NAT router for an older one i had that i think is using CONE NAT, i now get the same external port in the impulse reactor log as my internal port. With this router i only have to open the 6000-6200 range to connect without problems.

Perhaps demigod should send the port the internal client is listening on within the connection packet, and ignore the external port number the router has allocated (to take advantage of people forwarding ports). If a direct connect on this port fails, then try doing a NAT punchthrough via the port from the router.
End of Rocah's quote

I have seen some odd ports being used in my Reactor Log as well.  Enabling a specified port range in ReactorOptions, even if it's just the default range, stops that behavior.  A software setting like that wouldn't stop the router using random ports as you suggest above as the router would just do it's own thing regardless of what the software did if that was the case.

That being said, even when I stopped it from using those random ports in the logs, it still would not connect properly both ways to some people.  Forwarding all ports, ie being in a DMZ, would also not resolve connectivity issues with some people.

I will say though that the proxies do seem to be working fairly well as a band aid over the remaining underlying connection issues.  Aside from a little lenghty fallback period (if you're not forcing them), they seem to perform quite well and better than I was expecting for the added intermediary connection.

-dolynick

Reply #21 Top

I have seen some odd ports being used in my Reactor Log as well.  Enabling a specified port range in ReactorOptions, even if it's just the default range, stops that behavior.  A software setting like that wouldn't stop the router using random ports as you suggest above as the router would just do it's own thing regardless of what the software did if that was the case.

That being said, even when I stopped it from using those random ports in the logs, it still would not connect properly both ways to some people.  Forwarding all ports, ie being in a DMZ, would also not resolve connectivity issues with some people.

I will say though that the proxies do seem to be working fairly well as a band aid over the remaining underlying connection issues.  Aside from a little lenghty fallback period (if you're not forcing them), they seem to perform quite well and better than I was expecting for the added intermediary connection.

-dolynick

As i understand it, unlike TCP, the UDP "connection" (a connection in as much as the router storing a pass through for a specific port) has to be done on both sides, so you opening up all your ports (DMZ) will mean that anyone will be able to connect to you. However you may still have issues connecting to others to the reasons i gave above. The direct connection that demigod does in some cases (people with symmetric NAT routers) is really doing a NAT punch through without the facilitator. I still think it would be better if demigod attempted to connect to the internal port if it is different than the external to see if that user has forwarded ports, as at least my other symmetric NAT router was very glitchy when forwarding udp packets back to my internal client when recieved on the random port its just sent data out on.

It may be all moot soon anyway if Frogboy proceeds with proxying every connection.

Reply #22 Top

Are there many proxies in europe? Sometime other players in europe have 300 ping when on proxy which would indicate that they might be using a proxy on another continent. It works great even with high pings so it's just curiousity.