Ok, well I am new to the server scene, and since I like armagetron so much, I decided to start a server. I got the newest binaries off the website and started the app in the folder up to find terminal open and this message pop up
NEW PROBLEM
Finally booted up my server, yet it seems to have a problem..
Here's the log.
Last login: Fri Dec 23 14:01:57 on ttyp1
Welcome to Darwin!
SET-BCs-Computer:~ setbc$ cd /Users/setbc/Desktop/Armagetron\ 0.2.7.1\ dedicated\ server/
SET-BCs-Computer:~/Desktop/Armagetron 0.2.7.1 dedicated server setbc$ /Users/setbc/Desktop/Armagetron\ 0.2.7.1\ dedicated\ server/Armagetron
[0] Connecting to master server...
[0] Login information sent. Waiting for reply..
[0] Logging out...
[0] Done!
[0] Killing user 0, ping 10.
[0] Login information sent. Waiting for reply..
[0] Login failed: Timeout. *Problem here*
[0] Logging out...
[0] Done!
[0] Killing user 0, ping 10.
[0] Sending my server info...
[0] Ping charity changed from 100 to 100100.
[0] Nobody there. Taking a nap...
[0] Timestamp: 2005/12/23 14:03:58
Can someone tell me what this it is trying to do?
Mac OS X Server Setup Help!
Ok I was able to join it from server bookmarks. Is that ok? If so, I suppose server admins can't see there own server on the list of all servers. Right?
Also, how do you make your bikes go faster, and reduce the longitivity of how long the cycle walls stay? And how do you make the arena smaller. Thats all i need to know.
Thanks for all your help
Also, how do you make your bikes go faster, and reduce the longitivity of how long the cycle walls stay? And how do you make the arena smaller. Thats all i need to know.
Thanks for all your help
Re: Mac OS X Server Setup Help!
That's your server trying to make itself known to the master server. The master had problems since a few hours ( see here and was unreachable. Try restarting your server, it should work again now.NovaFlame wrote:[0] Connecting to master server...
[0] Login information sent. Waiting for reply..
[0] Logging out...
[0] Done!
[0] Killing user 0, ping 10.
[0] Login information sent. Waiting for reply..
[0] Login failed: Timeout. *Problem here*
[0] Logging out...
[0] Done!
You can make the arena smaller by reducing SIZE_FACTOR, for example to -4. Each integer decrement makes the area of the arena half as big as before. Similarly, each increment of SPEED_FACTOR by one multiplies all speed related settings by sqrt(2)~=1.41. Both have separate versions for the "single player" mode that is active when only one client is online, they are SP_SIZE_FACTOR and SP_SPEED_FACTOR. Alternatively, you can play with the individual settings CYCLE_SPEED, CYCLE_ACCEL and so forth. The lifetime of walls after their owner's is determined by [SP]_WALLS_STAY_UP_DELAY.
All those are console commands you can edit in settings_dedicated.cfg where there are some more explanations. Better than editing them directly, copy them over into a new file called autoexec.cfg and edit them there, they won't get overwritten when you upgrade the server then.
The wiki has some more hints:
http://wiki.armagetronad.net/index.php/ ... nistration
It's very odd. Many people that run a server can't see the server on the master list from their own lan, but I've always been able to (and still can). AFAIK, Swampy can see his two servers as well. Still, many other admins can't.
Very odd. I wish I knew why. I think there's a fundamental universal truth buried in the reason...
Very odd. I wish I knew why. I think there's a fundamental universal truth buried in the reason...
Check out my YouTube channel: https://youtube.com/@davefancella?si=H--oCK3k_dQ1laDN
Be the devil's own, Lucifer's my name.
- Iron Maiden
Be the devil's own, Lucifer's my name.
- Iron Maiden
The reason is quite simple:
When pinging the server, the client sends the packet to the public internet IP address. In some setups, the packets the server sends back to the client take the shortcut over the LAN and appear to come from a wrong address. The client won't associate them with the server then.
The shortcut can be closed by setting SERVER_IP to the true internet address in 0.2.8 servers and the server will appear on the internet server browser, but then the server will no longer appear in the LAN server browser. You get both with
SERVER_IP <true address> any:1
at the expense of blocking two ports.
When pinging the server, the client sends the packet to the public internet IP address. In some setups, the packets the server sends back to the client take the shortcut over the LAN and appear to come from a wrong address. The client won't associate them with the server then.
The shortcut can be closed by setting SERVER_IP to the true internet address in 0.2.8 servers and the server will appear on the internet server browser, but then the server will no longer appear in the LAN server browser. You get both with
SERVER_IP <true address> any:1
at the expense of blocking two ports.
Presumably you're running behind a router, is that true? I'll assume that you are, and that you don't know what that means. 
So, on the internet, your IP address is how other computers know where yours is. But you don't have to be on the internet to have an IP address. An IP address is just a generic address which can be used on any network that uses the IP protocol.
In my house, I have one single internet connection. With that connection, I get one IP address available to the internet. But I have 4 (count them!) devices I want to connect to the internet. I have two options. I can get 4 internet connections from my ISP, which would cost $40*4=$160/month. Or I can buy a NAT router.
Let's ignore the NAT part. What a router does is it connects to the one single internet connection that I have, and allows all the devices connected to it to use the same internet connection. In order to do that, it has to give IP addresses to each device. So it does it using a private network. On my private network, my 4 devices each have IP addresses that are invalid on the internet. So if I give you the IP address of this computer (192.168.1.102), you cannot use that IP address to connect to it.
So, when your armagetron server connects to the master server, the master server knows only its public internet address. But the game server on your network doesn't know its public internet address, it only knows its private network address, which is only valid inside your house. Your router resolves the differences so that people can connect to your server and play the game.
So when you run the game on your desktop and browse the master server list, that list is comprised of the public internet addresses for each game server. Then your client will ping each internet address to see if its available.
Now comes the clever bit. Are you ready for the clever bit?
Some routers that you put in your home are smart enough to recognize when a machine inside your network is trying to talk to another machine inside that network. In that case, it doesn't send the packet out to the internet, it just routes it right through inside your network. This is good for you because it speeds up local communications, and also makes local communications more secure.
So your client gets the public internet address of your game server from the master server and attempts to ping that address. Your router recognizes that this communication is directed from one to another computer on your network and doesn't send it out to the internet.
So what z-man's saying, when these packets arrive at your game server, your game server sees that it came from the local network. Of course, it doesn't know the difference anyway, but the effect is that it responds on the local network. Your router doesn't do any magic on communications on the local network like it would if they were going to the public internet, so your client receives the packet from an address on the local network.
So it sends the packet to an address like 65.128.23.10 and receives it from an address like 192.168.1.100. And it discards the packet it receives because it's obviously a fake. Right? Only it's not. So the result is that your client can't ping the server.
However, it can connect to the server. I assume that the network code allows connecting in spite of this situation and there's a good reason for it, but I don't know what it is.
Does that make sense?
Edit: Note that the last part is definitely an oversimplification. If I were to guess, I'd guess that the thing happens like this: Your client sends the packet from a certain port (say 10234) to the public address of the game server. Your router, doing the NAT part of the NAT name, rewrites that to a different port number, say 11543, and sends it to the game server. The game server sees the port number 11543 and responds to that port, using the IP address the router gave it. The router, seeing that the client you're using is on the local network, doesn't change the IP address. So your game server responds to the wrong port. I don't see how this behavior on the part of the router makes sense, so it's probably a bug, if tht's how it's happening. I don't know, maybe the ping code does work more like the oversimplification I gave and less like this braindead NAT implementation I've described.
So, on the internet, your IP address is how other computers know where yours is. But you don't have to be on the internet to have an IP address. An IP address is just a generic address which can be used on any network that uses the IP protocol.
In my house, I have one single internet connection. With that connection, I get one IP address available to the internet. But I have 4 (count them!) devices I want to connect to the internet. I have two options. I can get 4 internet connections from my ISP, which would cost $40*4=$160/month. Or I can buy a NAT router.
Let's ignore the NAT part. What a router does is it connects to the one single internet connection that I have, and allows all the devices connected to it to use the same internet connection. In order to do that, it has to give IP addresses to each device. So it does it using a private network. On my private network, my 4 devices each have IP addresses that are invalid on the internet. So if I give you the IP address of this computer (192.168.1.102), you cannot use that IP address to connect to it.
So, when your armagetron server connects to the master server, the master server knows only its public internet address. But the game server on your network doesn't know its public internet address, it only knows its private network address, which is only valid inside your house. Your router resolves the differences so that people can connect to your server and play the game.
So when you run the game on your desktop and browse the master server list, that list is comprised of the public internet addresses for each game server. Then your client will ping each internet address to see if its available.
Now comes the clever bit. Are you ready for the clever bit?
Some routers that you put in your home are smart enough to recognize when a machine inside your network is trying to talk to another machine inside that network. In that case, it doesn't send the packet out to the internet, it just routes it right through inside your network. This is good for you because it speeds up local communications, and also makes local communications more secure.
So your client gets the public internet address of your game server from the master server and attempts to ping that address. Your router recognizes that this communication is directed from one to another computer on your network and doesn't send it out to the internet.
So what z-man's saying, when these packets arrive at your game server, your game server sees that it came from the local network. Of course, it doesn't know the difference anyway, but the effect is that it responds on the local network. Your router doesn't do any magic on communications on the local network like it would if they were going to the public internet, so your client receives the packet from an address on the local network.
So it sends the packet to an address like 65.128.23.10 and receives it from an address like 192.168.1.100. And it discards the packet it receives because it's obviously a fake. Right? Only it's not. So the result is that your client can't ping the server.
However, it can connect to the server. I assume that the network code allows connecting in spite of this situation and there's a good reason for it, but I don't know what it is.
Does that make sense?
Edit: Note that the last part is definitely an oversimplification. If I were to guess, I'd guess that the thing happens like this: Your client sends the packet from a certain port (say 10234) to the public address of the game server. Your router, doing the NAT part of the NAT name, rewrites that to a different port number, say 11543, and sends it to the game server. The game server sees the port number 11543 and responds to that port, using the IP address the router gave it. The router, seeing that the client you're using is on the local network, doesn't change the IP address. So your game server responds to the wrong port. I don't see how this behavior on the part of the router makes sense, so it's probably a bug, if tht's how it's happening. I don't know, maybe the ping code does work more like the oversimplification I gave and less like this braindead NAT implementation I've described.
Check out my YouTube channel: https://youtube.com/@davefancella?si=H--oCK3k_dQ1laDN
Be the devil's own, Lucifer's my name.
- Iron Maiden
Be the devil's own, Lucifer's my name.
- Iron Maiden
Thanks, Ima go change the settings round again.nemostultae wrote:http://generalconsumption.org/armagetro ... macosx.dmg
Thanks for all your help guys!