Jump to content
SubSpace Forum Network

server/zone help

gdogkiller

By gdogkiller
in Technical Support

 Share

Recommended Posts

gdogkiller Newbie

gdogkiller

Posted
Posted
ok so ive been doing some reading and nothing is seeming to work. my problem is that when i go to get on my zone in continuum it goes red. i have a linksys router and ive already forwarded my ports it still wont work im kinda stuck. someone please help me
rootbear75 Newbie

rootbear75

Posted
Posted
ok so ive been doing some reading and nothing is seeming to work. my problem is that when i go to get on my zone in continuum it goes red. i have a linksys router and ive already forwarded my ports it still wont work im kinda stuck. someone please help me

if your zone is hosted on your computer and you are trying to connect to it, you have to manually add it.

 

Zones -> Add Custom -> Zone Name: W/E -- IP: 127.0.0.1 -- Port: (w/e it's set to in server.ini)

Cancer+ Newbie

Cancer+

Posted
Posted

No you don't.

 

As long as you have the directory servers right, it will show up.

 

And root, he isn't trying to get it to SHOW UP, he is trying to get it GREEN. Do you read posts?

 

 

Flagger, post your .ini

Hakaku Newbie

Hakaku

Posted
Posted

I'm guessing this has nothing to do with what any of you said, but rather might be a problem related to ScoreID and ServerID found in your server.ini (they need to be the same).

 

Another reason could be that you need to add your zone's name, ip, and port manually. So when you go into Continuum, open the download zones menu, and click "Add custom". Put any name for you zone's name, then add "127.0.0.1" for your zone's IP, and then add your zone's Port number.

 

Forwarding ports could be another problem, but this normally affects other users and not yourself.

gdogkiller Newbie

gdogkiller

Posted
  • Author
Posted

ok i tried them and im still working on it but someone told me to post my server.ini up so here it is but the only thing is that the passwords are blank because i erased them but in the real server.ini their there.

 

 

 

 

 

//You can delete anything with the // infront, they are their to help you get the basics... Mine GO BOOM http://www.shanky.com/server/

//This is currently, at time of download, 1.34.14 subgame

 

[Custom]

ArenaMode=1

//1=Any player can create an own a new subarena

//2=Only mods+ can own newly created subarenas

//3=Smods+ own new subarenas

//4=Sysops own new subarenas

//5=New subarenas won't make new files, will just use spawn.cfg instead. If a .cfg is already created for subarena, will use that instead

 

[Arena]

ArenaMaxPlayers=200

ArenaDesiredPlayers=100

ArenaMinimumPlayers=25

SpawnKeepScores=1

MaxArenas=2000

MaxArenasMemory=64000

 

[Comms]

MaxQueueToLogin=16

PacketHistoryMax=2000

IncomingBufferSize=131072

OutgoingBufferSize=131072

EncryptMode=1

UnreliableBufferSize=128

TransportBufferSize=160

FlushTime=10

BandwithIdleTime=21600

SelectTime=10

 

[Misc]

DisableShareware=0

RegisterKickShareware=0

MaxSharewarePlayers=-1

MaxPlayers=200

MaxSharewareTime=90000000

DisableSharewareNames=0

DisableSharewareShips=0

DisableSharewareScores=0

MenuKickOutDelay=12000

NoAntiInSafe=1

//If 1, then if in a safty, SS will ignore that player's anti

LockFreqs=0

//If 1, then *lock doesn't allow freq change

PositionDataAccess=2

//if 0, sysops see player stats in spec. If 1, smods/sysops can. If 2, then mod/smods/sysops can

AlertCommand=cheater

//so ?cheater {text} will send to online mods

AllowPubScorereset=0

AllowPvtScorereset=1

//If 1, ?scorereset will reset player's score

TimerDropFlagTerritoryRadius=8

//If non-0, then all non-neutral droped flags X tiles away from ship. More info in FAQ at Server Help Site

ShipTypeSwitchResetPeriod=0

//If non-0, than if someone does X amount of shipchanges that is in the .cfg in this amount of time (in milliseconds), then kicks them off

CheckWeapons=1

//Leave this set to 1, so it detects more of different type of cheats.. will kick them out if in .cfg the [security] SecurityKickoff is 1

CheckFastBombing=0

//More info on website

FastBombingThreshold=30

//More info on website

ForceObsceneCheck=0

//0 = normal, 1 = everyone has obscene checking on

NoFlagRewardLimit=0

//If set non-zero reward multiplier limit is removed in FlagRewardMode 1. Multiplier is (maximumAllowedPerTeam / numberOfTeamMembers), if NoFlagRewardLimit is set 0

multiplier is limited by 2.

LogPoints=0

PointUpdateDiff=500

JackpotBroadcastPoints=0

ServerLog=1

KeepAliveDelay=500

DefaultLevelFile=_bzw.lvl

//Change to your map file name

Port=20000

//Make it something round, like 1000, 2000, etc. Change this if you are running more than one zone off same billing

AllowVIEClients=1

//If you wish to restrict your zone to continuum only, set to 0. If you want everyone to play, set to 1

StaffChat=

//Divide staff chat channels by commas. Only mods+ can join these local chats.

ForceContinuumOnly=0

//If set to 1, will only let continuum users enter zone

ServerIP=74.243.mega_shok.gif.26

//Set to the server's IP #. This is used for *einfo's proxy detection

AllowPrerelease=1

//Set to 1, people with newer continuum can enter. Set to 0, only current client will be allowed in

 

[CPU]

LoopDelay=0

ProcessMaxTime=4

SleepPerIteration=0

SlowIterationWarningLevel=100

SleepTime=0

 

[Permission]

AllowBadMachineId=1

AllowLowBandwidth=1

MinimumSecondsToLogin=0

PermissionMaxPoints=0

PermissionMode=0

AutoPermissionPoints=0

AutoPermissionIDList=0

AutoPermissionMessage=Congratulations

 

[password]

SysopP!@#$%^&*word=

EnergyP!@#$%^&*word=

ModeratorP!@#$%^&*word=

SuperModeratorP!@#$%^&*word=

VIPP!@#$%^&*word=

//Change all to what you want

 

[billing]

LogMessages=0

IP=127.0.0.1

password=

//What is the billing pw in the subbill.ini

ServerName= Killer Zone

//Zone name

Port=20000

ServerId=4483

//Make the same as in [Misc] Port=

GroupId=1

ScoreId=4483

//Make the same as in [Misc] Port=

ReconnectTime=12000

AttemptTime=6400

 

[Advertise]

SendMode=0

DisplayMode=0

Duration=6000

 

[Validation]

CheckMod=0

CheckSMod=0

CheckSysop=0

LogPubCommands=*

LogPvtCommands=*

DisablePubCommands=

DisablePvtCommands=

//Help at http://www.shanky.com/server/ in FAQ section for Subgame2

 

[Directory]

IP=sscentral.ds98.com,sscentral.subspace.inet.fi,sscentral.s

ubspace.net,sscentral.subspacehq.com

Description= Made by gdogkiller and 008flagger

//What you want to have for the description of zone

NameP!@#$%^&*word=

//Pick anything you want

Port=20000

Hakaku Newbie

Hakaku

Posted
Posted

Make your [billing] IP = localhost

 

You could also try making your serverid and scoreid match [Misc] Port

 

And make [Directory] Port = 4991

 

And finally [Directory] IP = sscentral.sscuservers.net, ssdir.playsubspace.com, warpath.bluetoast.org, sharvil.nanavati.net, dir.cz.sshq.net

 

Oh, and [billing] Port = # should be the same number that you have in your subbill.ini (Usually most people use [billing] Port = 185), and not the same as [misc] Port #.

Cancer+ Newbie

Cancer+

Posted
Posted
No you have to add your own zone as custom blum.gif

 

 

No, you don't. I hosted SSM for like a year+ and the only time I had to "add custom" is when the directory servers in the .ini were wrong. Every other time, it showed up just fine.

Hakaku Newbie

Hakaku

Posted
Posted
No, you don't. I hosted SSM for like a year+ and the only time I had to "add custom" is when the directory servers in the .ini were wrong. Every other time, it showed up just fine.

It might be a problem for those who have routers. Before I had wireless, I could start up and connect to a zone without any troubles; now I have to manually add my zone in order to connect. It'll show up in the directory server list without a problem, but it's the connecting part on my end that's the problem (others can enter though).

 

I believe the issue has been mentioned multiple times on MGB's server help forum, so I doubt it's merely a problem with the .ini file if it's also an ASSS problem.

L.C. Newbie

L.C.

Posted
Posted (edited)

From my understanding, the most logical perception I have from how the networking works is this:

 

If you are hosting your zone, whether you have a router or not, there are three primary different ways to connect to your zone.

 

1. Internet people connecting to you.

2. LAN people connecting to you.

3. You connecting to yourself.

 

The internet people are people that generally do not have reserved/restricted IP ranges, such as 192.168.x.x or those strange random ~163.191.x.x (~ for around these numbers), as well as 127.0.0.1 related numbers.

 

The LAN people are the ones that have IPs in the 192.168.x.x ranges, "random" ~163.191.x.x ranges, or a specifically defined IP range (defined by network admin).

 

Yourself will always be 'localhost' and/or 127.0.0.1.

 

The most appropriate way to connect to your zone follows as such:

1. They connect to your internet IP, the one ipchicken.com or whatismyip.com would display if you went there; this is the IP your ISP !@#$%^&*igned to your internet subscription (and any other private IP addresses that you may have ordered from your ISP).

2. They connect to your LAN IP, which is the IP that your router or network administrator !@#$%^&*igned to your machine; an example could be 192.168.2.57 or 163.194.5.119.

3. You use either localhost or 127.0.0.1 to connect to yourself, because it IS yourself.

 

While for #2 users (LAN) your internet IP might work, it isn't necessarily proper to use your internet IP since you are on the same LAN as they are; they should be using your LAN IP as it is most logical and proper.

 

For #3 (yourself), while in some cases you can use your internet or LAN IP, your 'localhost' or 127.0.0.1 would be most logical and appropriate, because it is yourself.

 

From my understanding, this is how it works. I find no flaw in this picture/concept that I understand, but I am open to be proven wrong upon valid and logical reasoning. smile.gif

 

Just my few cents.

 

EDIT :: This reply is only legitimate if my reason for making this reply by correctly understanding what subtopic is being discussed here is valid.

 

No, you don't. I hosted SSM for like a year+ and the only time I had to "add custom" is when the directory servers in the .ini were wrong. Every other time, it showed up just fine.
!@#$%^&*uming that SSM is a dedicated server in a datacenter, it makes perfect sense that you wouldn't have to add custom as long as your zones shown up in the directory server listing. The only time you'd have to "add custom" in this case is if you tried to have your SSM dedicated server connect to itself.

 

By the way, if another IP address for either #1, #2 or #3 works -- I don't think that'd debunk or disprove any part of the concept of networking that I understand. If it works, it works -- that's great! smile.gif

Edited by L.C.
rootbear75 Newbie

rootbear75

Posted
Posted
No you have to add your own zone as custom blum.gif

 

 

No, you don't. I hosted SSM for like a year+ and the only time I had to "add custom" is when the directory servers in the .ini were wrong. Every other time, it showed up just fine.

you didnt host SSM in your own house did you?

rootbear75 Newbie

rootbear75

Posted
Posted (edited)
No sir. Computer > router > modem > comcast.

 

Any other questions? Maybe I'm just not a re!@#$%^&* and read shanky.com very well and found the hidden goodness.

no, because the whole sense of logic saying you can connect to your own computer using the outside IP address is complete nonsense. It's just how the internet works. Look at L.C.'s explanation

to connect to your computer FROM your computer, you have to use 127.0.0.1 or 'localhost'

Edited by rootbear75
rootbear75 Newbie

rootbear75

Posted
Posted
You can connect using your internet IP as well.

that doesnt make sense.

I've tried to do that with the same setup before, and it sends me to my router, not my computer

unless he's using port fowarding then maybe i can see it, but otherwise that just never works

Hakaku Newbie

Hakaku

Posted
Posted
Port forwarding is the answer, then.

there's a big sticky topic about port forwarding at mgb's

I see someone hasn't been paying attention to the convo. The answer isn't port forwarding, neither is it an issue with configurations. I'm nearly 100% sure it's a router issue that prevents users from connecting to their zone from their own IP (which is why it has to be added manually as 127.0.0.1).

 

Port forwarding problems only prevent OTHERS from connecting to your zone. And if it really was a configuration problem, then someone tell me what's wrong here (and an ASSS configuration is attached for comparison).

asss_config.txt

Samapico Newbie

Samapico

Posted
Posted

I was replying to rootbear, though; sorry for the lack of quotes, I was lazy... and still am, cause I haven't quoted you either. (Still not sure if it makes my post more valid, but still...)

As in if you're trying to connect to yourself using your public ip, it would make sense if you also need port forwarding

Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...