Author |
Topic: Running CODUO server at home |
AndrewT |
General Member Since: Feb 28, 2005 Posts: 58 Last: Oct 27, 2017 [view latest posts] |
|
|
Category: CoD+UO General Posted: Thursday, Apr. 4, 2013 10:19 pm |
|
hi everyone
i know it's not a modding issue directly, but testing, bugfixing, troubleshooting and finally playing your maps and mods with your friends - that's gonna demand an option of running an own private server
here are the datas:
- vanilla coduo 1.51, without any mods
- a basic server.cfg in the uo folder
- a shortcut to coduomp.exe, with settings like this: "E:\Games\Call of Duty\CoDUOMP.exe" +set dedicated 2 +exec server.cfg +map_rotate
(- i even tried some kind of fixed exes for starting up a server, but nothing happened)
- comodo internet security firewall, with the particular exe files set as trusted
- linksys wrt54gl router with "block anonymus requests" disabled, and the following port ranges forwarded for my internal ip: 20500-20510, 20600-20610, 27900, 28900-28970 both udp and tcp
(router firewall is obviously enabled, and it it should remain this way, because the internets would punish me if i sacrifice the security for a server, so i hope there are other options to think about. i also cannot setup a static ip, net supply works only with DHCP set dynamic ip)
if i run this server via the shortcut mentioned above, a console/command line appears, and according to the messages, the server is up and running. when i add my external ip to the favourites in All-Seeing-Eye, and refresh, it does find the server, and i can join, i can be ingame, but in the console i can see that i am recognized by my internal ip (like 192.168.etc), and that's suspicious.
then i pass my external ip to my friends, like /connect 79.12.13.14:28960, and ask them to join the server this way, they stuck in "Awainting connection... 8... 9...", and it could go till the end of time, instead of awaiting gamestate after 3 waves as normal. if i ask them to do the same without the port at the end of the ip, the same thing happens.
so my questions are:
- is it possible to run a private/public/whatever server behind a router that folks knowing my ip can join?
- if it is, what did i do wrong? what can i try?
thanks in advance |
|
|
|
|
|
AndrewT |
General Member Since: Feb 28, 2005 Posts: 58 Last: Oct 27, 2017 [view latest posts] |
|
|
|
.KiLL3R. |
|
General Member Since: Oct 26, 2006 Posts: 1437 Last: Jul 3, 2017 [view latest posts] |
|
|
|
AndrewT |
General Member Since: Feb 28, 2005 Posts: 58 Last: Oct 27, 2017 [view latest posts] |
|
|
Category: CoD+UO General Posted: Friday, Apr. 5, 2013 04:01 pm |
|
.KiLL3R. writes...Quote: You need to have UDP port 28960 forwarded to your PCs LAN IP, which can be done somewhere in your router settings, then other players should be able to connect and your server should show up on the server browser.
thanks for the reaction mate, as i mentioned above, i have forwarded 28900-28970 both udp and tcp which i believe pretty much covers this |
|
|
|
.KiLL3R. |
|
General Member Since: Oct 26, 2006 Posts: 1437 Last: Jul 3, 2017 [view latest posts] |
|
|
Category: CoD+UO General Posted: Friday, Apr. 5, 2013 04:16 pm |
|
AndrewT writes...Quote: .KiLL3R. writes...Quote: You need to have UDP port 28960 forwarded to your PCs LAN IP, which can be done somewhere in your router settings, then other players should be able to connect and your server should show up on the server browser.
thanks for the reaction mate, as i mentioned above, i have forwarded 28900-28970 both udp and tcp which i believe pretty much covers this
Oops, forgot you said that part when I was replying >.<
You say comodo firewall is allowing the exe, but is Windows firewall disabled? If not then you need to allow it on that too.
Quote:
and i can join, i can be ingame, but in the console i can see that i am recognized by my internal ip (like 192.168.etc), and that's suspicious.
That's because of NAT redirection, the router sees that you are connecting to your external IP from within the LAN, so it keeps it all in the LAN.
You can also try running a program called Wireshark and see if your computer is receiving packets from your friends when they try to connect. |
|
|
|
AndrewT |
General Member Since: Feb 28, 2005 Posts: 58 Last: Oct 27, 2017 [view latest posts] |
|
|
Category: CoD+UO General Posted: Saturday, Apr. 6, 2013 08:45 am |
|
.KiLL3R. writes...
Quote:
AndrewT writes...
Quote: and i can join, i can be ingame, but in the console i can see that i am recognized by my internal ip (like 192.168.etc), and that's suspicious.
That's because of NAT redirection, the router sees that you are connecting to your external IP from within the LAN, so it keeps it all in the LAN.
You can also try running a program called Wireshark and see if your computer is receiving packets from your friends when they try to connect.
thanks for mentioning this application, didn't think about involving such program, but looks promising, i'll try to figure out the situation when my friends will try to connect next time.
the windows (7) firewall is turned off (i didn't see a reason to lock resources for it, as i have comodo as my primary application, and do trust it)
but to sum it up, if the router detects my own connection attempt as coming from inside the LAN, does it also consider that the whole CODUO server should be inside the LAN, and that's why noone outside the LAN can see it join? so is this some kind of NAT negotiation failure? i thought that port forwarding enables a pc with the desired local IP address to send and receive data to and from the internet in cases the NAT fails to deliver it to the specific computer requested it.
so now i'm a bit confused, but i'll of course keep trying. thanks for the answers again, and if you have some more useful advices, please share them, they are more than welcome. thanks |
|
|
|
morgawr |
General Member Since: Dec 15, 2004 Posts: 377 Last: Mar 19, 2023 [view latest posts] |
|
|
|
AndrewT |
General Member Since: Feb 28, 2005 Posts: 58 Last: Oct 27, 2017 [view latest posts] |
|
|
|
general99 |
|
General Member Since: Oct 31, 2004 Posts: 323 Last: Dec 18, 2013 [view latest posts] |
|
|
Category: CoD+UO General Posted: Sunday, May. 12, 2013 02:54 pm |
|
I have previously run a coduo server from home, years ago. Connection was 512k both up and down, and worked ok for 10 players, although we mostly had about half that.
Only the LAN address would show up for users on the LAN, users at other locations would see the correct external IP.
I'll see if I can dig up my old notes, may still have them.
Big drawback was ping - those on the LAN around zero ping, external users around 100. I live in a regional city, and I think other players, even though living locally, their signals had to bounce to the state capital and back. |
|
|
|