Campaign server tcp port

presence · Post by **presence** » February 16th, 2006, 11:36 pm

Hey guys,

I noticed when I was trying to tunnel my connectivity to your campaign server through my home network that the port definition you had in the wiki was wrong. The wiki states that the port is tcp/15002 and while testing this (with a packet capture since the tunnel didn't work) I noticed that the port was actually 15003. I changed it in the wiki, and didn't want to do it on the sly.

This test was performed to download new campaign content, not to connect to the server for any other purpose. it seemed that the wiki information was tailored to downloads, so I changed it.

I don't know where else this information may be wrong.

Hope I didn't cause any pain.

Post by **freim** » February 16th, 2006, 11:48 pm

Just as we have several MP servers:
The Stable server runs on port 15000
The Development server (1.1.1 atm) runs on 14999
The SVN TRUNK server (1.1.1+svn atm) runs on 14998

... we have several campaign servers:
The Stable cmp server runs on 15002
The development cmp server runs on 15003

presence · Post by **presence** » February 16th, 2006, 11:50 pm

So what you are saying is:

If you currently have 1.1.1 you go to 15003, but previous versions like 1.1 go to 15002.

Might be worth documenting that.

Post by **freim** » February 17th, 2006, 12:09 am

presence wrote:So what you are saying is:

If you currently have 1.1.1 you go to 15003, but previous versions like 1.1 go to 15002.

Might be worth documenting that.

Yes, 1.0.x defaults to 15002, 1.1.1 to 15003 (1.1 should have done the same but wasn't updated).

Feel free to update the wiki with this information

Edit: the reason is because changes to the development branch has made campaigns made for it incompatible with the stable version of Wesnoth and the other way around.