Actually, the 4991 is the +1'd port for server communication. Continuum connects via UDP port 4990.
Bak - Sun Sep 24, 2006 2:10 am
Post subject:
gawd damnit, 3 hours later i figure it's 4990 and not 4991 by going through catid's directory server and mgb beats me to saying it... o well good times.
CypherJF - Sun Sep 24, 2006 10:47 am
Post subject:
Ah well I'm sure if you had looked around you would have found the answer quicker. Ya know, +/- 1 aint bad.
Bak - Thu Sep 28, 2006 4:25 am
Post subject:
ehhh ok try this one... Program works fine with catid's directory server, not with the one sscentral.sscuservers.net is using. The traffic is as follows:
Code: Show/Hide Me -> Directory Server 00 01 00 00 00 00 01 00 // I'm a subspace client connecting without encryption Directory Server -> Me 00 02 00 00 00 00 // you're in; no encryption ok! Me -> Directory Server 01 00 00 00 00 // send me the player list, every zone with at least 0 players Directory Server -> Me 00 03 7b 00 b8 8b e8 d7 8a 61 71 15 da // here's a reliable packet, with packet id 7b 00 b8 8b, and payload d7 8a 61 71 15 da Me -> Self wtf's a d7 packet? and why is the packet id 7b 00 b8 8b and not 00 00 00 00?!? |
with catid's directory server, the reliable packet I get is:
Code: Show/Hide 00 03 00 00 00 00 00 0a ... // reliable packet with packet id 00 00 00 00, and payload is the beginning of a really big chunk |
So... what gives? My only guess is that the other directory server is still using encryption but I thought if the encryption key you get back is all 0's you aren't using encryption.
Bak - Thu Sep 28, 2006 6:46 am
Post subject:
got it working... it always encrypts, even if you send it 00 00 00 00.
CypherJF - Thu Sep 28, 2006 5:50 pm
Post subject:
Why would it encrypt using a null key?
Smong - Fri Sep 29, 2006 10:51 am
Post subject:
It would seem something is missing from the code to handle the different types of key. Perhaps because it was ripped and not written, or badly copy/pasted.