Creating a server....

by PugSchnizzle on 12/02/2007 03:54, 13 messages, last message: 12/14/2007 20:40, 2489 views, last view: 05/05/2024 09:12

Hi! I have been trying to make a server for some time now.... and I fowarded the ports, just like i was supposed to, and then it still says "cannot respond to ping... check your firewall settings" also i think it sometimes appears on the list of servers in the game, but always says "waiting for response" HOW can i create one?!?!!?!?!? i've been trying for so long!

   Board Index   

#1: router

by Hirato Kirata on 12/02/2007 03:58

Most routers allow you to set forwarded ports quite easily, others like alcatel you need to do it via telnet.

if you have an alcatel router, look at this guide http://homepages.paradise.net.nz/kemyst/id30.htm

it does help if you set a static network IP y'know

reply to this message

#2: Re: router

by PugSchnizzle on 12/02/2007 04:02, refers to #1

ummmmmm i really dont get what that is... im not really the kind of person that does code and stuff.... i would just like my own server to go on sometimes. :)
so that link...what exactly is it? I opened it and there was a bunch of codes and it was just so confusing. lol.... explain how please? D:

reply to this message

#3: ..

by MeatROme on 12/02/2007 17:56

Have you read
http://cube.wikispaces.com/Multiplayer+Guide#tocMultiplayer%20Guide8

If your router has a webinterface with a section regarding portforward ... which I kinda read between the lines ... I'm pretty sure you should be able to host your server.

Did you really forward UDP, not TCP?

Have you tried adding your LAN IP via "/addserver" - because it registers with your internet IP and this usually isn't routable - use your LAN ip to connect via sauerbraten - remote users can use the regular serverbrowser though.

For more help you need to elaborate on your problem. Give us brand and make of your router for example ... describe test-scenarios in which remote and/or LAN users have tried to access via serverbrowser and IP seperatedly.

reply to this message

#4: Re: ..

by PugSchnizzle on 12/03/2007 04:13, refers to #3

i am sure it was UDP

my router is WRT300N v1. 1

i dont know what you mean by /addserver
and i dont want LAN, i want it to be a big one that people can go on

so what exactly do i do?

reply to this message

#5: Re: ..

by MovingTarget on 12/03/2007 05:14, refers to #4

Hey Pug! Even though I don't know anything about routers or port forwarding, I want you to think about how much bandwidth you have; if you want it to be a large server, your bandwidth needs double for every client. A good option would be to go to your internet provider and extremely politely ask them if they can host a server for you. I find my Comcast high-speed internet utterly insufficient for even 4 clients; with just 2 there are some lags involved. Also how fast is the machine you are going to be hosting it on?

reply to this message

#6: THE TRUTH ABOUT SAUER_SERVER BROADBAND and FIREWALLS

by d4z on 12/04/2007 00:34

THE TRUTH ABOUT SAUER_SERVER BROADBAND and FIREWALLS

The bandwidth a sauer_server uses is roughly equal to the square of the number of people. Not
the heavily misleading doubling factor that is documented.

So bandwidth doubles per person for roughly the first 3 or 4 people. After that, the documented
guideline is far more misleading than useful.

Sixteen players is roughly a T1 of bandwidth. (1.4 megabytes per second.)

That's about seven times as much as a six-player server. (It's not the thousand-times-as-much
bandwidth that the documented doubling guideline implies!)

Note that although most home DSL/Cable modems get great download speeds, the upload speeds are
often pitiful by comparison.

FIREWALLS

As far as firewalls, the firewall needs to pass the following in order to run a sauer_server:

UDP 28785
UDP 28786

In order to run on the master list, you also need:

TCP 80
UDP 53

Your server also can't be pinged unless you allow ICMP to get through.

Note that UDP 53 is for DNS lookups. The master-server at sauerbraten.org, doesn't accept
HTTP/1.0, so referring to it by IP-address alone isn't good enough.

A typical way for a firewall to work is to automatically allow inbound traffic that matches
your outbound traffic to get though.

That will work for TCP 80 and UDP 53, which are also almost always allowed by default anyways.

But you still have to allow UDP 28785 and 28786 explicitly so that players can initiate a UDP
connection when they try to connect to your server.

Unfortunately, some home broadband services don't allow any non-matching incoming packets at
all. So in that case you just plain won't be able to run a sauer_server at all on that modem
without some real hacking.

If your provider is friendly enough, they may allow you to tell them to allow the UDP 28785
and 28786 ports. With others, sans hacking, you may just be out of luck.

MACHINE SPEED

Lastly, the standalone server sauer_server is very efficient compared to modern desktop
machines.

Under Unix, chances are any machine you'd consider running them on is fast enough. A 100mhz
(one-tenth of a gigahertz) CPU for 16 people is more than good enough.

I don't know what M$-WindoZe might do to your server, but you really SHOULDN'T need a fast
machine because nearly all the hard work is done by the clients.

reply to this message

#7: THE TRUTH ABOUT SAUER_SERVER BROADBAND and FIREWALLS

by d4z on 12/04/2007 00:35

THE TRUTH ABOUT SAUER_SERVER BROADBAND and FIREWALLS

The bandwidth a sauer_server uses is roughly equal to the square of the number of people. Not
the heavily misleading doubling factor that is documented.

So bandwidth doubles per person for roughly the first 3 or 4 people. After that, the documented
guideline is far more misleading than useful.

Sixteen players is roughly a T1 of bandwidth. (1.4 megabytes per second.)

That's about seven times as much as a six-player server. (It's not the thousand-times-as-much
bandwidth that the documented doubling guideline implies!)

Note that although most home DSL/Cable modems get great download speeds, the upload speeds are
often pitiful by comparison.

FIREWALLS

As far as firewalls, the firewall needs to pass the following in order to run a sauer_server:

UDP 28785
UDP 28786

In order to run on the master list, you also need:

TCP 80
UDP 53

Your server also can't be pinged unless you allow ICMP to get through.

Note that UDP 53 is for DNS lookups. The master-server at sauerbraten.org, doesn't accept
HTTP/1.0, so referring to it by IP-address alone isn't good enough.

A typical way for a firewall to work is to automatically allow inbound traffic that matches
your outbound traffic to get though.

That will work for TCP 80 and UDP 53, which are also almost always allowed by default anyways.

But you still have to allow UDP 28785 and 28786 explicitly so that players can initiate a UDP
connection when they try to connect to your server.

Unfortunately, some home broadband services don't allow any non-matching incoming packets at
all. So in that case you just plain won't be able to run a sauer_server at all on that modem
without some real hacking.

If your provider is friendly enough, they may allow you to tell them to allow the UDP 28785
and 28786 ports. With others, sans hacking, you may just be out of luck.

MACHINE SPEED

Lastly, the standalone server sauer_server is very efficient compared to modern desktop
machines.

Under Unix, chances are any machine you'd consider running them on is fast enough. A 100mhz
(one-tenth of a gigahertz) CPU for 16 people is more than good enough.

I don't know what M$-WindoZe might do to your server, but you really SHOULDN'T need a fast
machine because nearly all the hard work is done by the clients.

reply to this message

#8: Re: THE TRUTH ABOUT SAUER_SERVER BROADBAND and FIREWALLS

by MovingTarget on 12/04/2007 04:00, refers to #7

Please don't double post :-) And thanks for the correcting info.

reply to this message

#9: I need help as well

by Entrakan on 12/09/2007 16:59

im on a mac... how do i run it o a mac? from the very start? idk.....

reply to this message

#10: Re: I need help as well

by a--baby--rabbit on 12/09/2007 20:04, refers to #9

on a mac... use the launcher, hit the server button in the toolbar, then push the 'start' button. If you get 'masterserver ping' messages, then follow the generic info on this forum for how to open ports on routers, etc.

reply to this message

#11: I can't create a server, too

by Falco-Ger on 12/14/2007 17:13

hi all,
i can not create a server, too.
i opened ports:
open to ip to port
TCP 80 192.168.178.20 80

UDP 28785-28786 192.168.178.20 28785-28786

UDP 53 192.168.178.20 53


but master server did not repond to ping. i don't know what to do?!

reply to this message

#12: Re: THE TRUTH ABOUT SAUER_SERVER BROADBAND and FIREWALLS

by ATIRULE on 12/14/2007 17:44, refers to #7

your both wrong sauer don't use hardly and bandwidth even with 16 players
I used to host a 16 player on A home cable connection that was 9mbs down and 368k up
and i could still play on the pc that was hosting ever when the server is full
and not lagg

system spec's on there server where 2.0ghrz celaron cpu
265mb ram winxp pro ati 9600XT@256mb

reply to this message

#13: Re: I can't create a server, too

by Drakas on 12/14/2007 20:40, refers to #11

Did you restart your router?

reply to this message

   Board Index