Jump to content
SubSpace Forum Network

Recommended Posts

Posted

Ok I know how to make the packets and send them, so I only need to ask protocol questions, which do not regard perl.

 

When I send a client key packet (00 01), I receive a sync request (00 05) packet, that is all I receive. Is this suppost to happen?

Posted

ts: 262217, size: 6

ts: 235077706, size: 6

ts: 640876619, size: 6

ts: 76, size: 6

 

This is the timestamp I got in the 00 05 packet after sending the 00 01, ts is the timestamp, I ran the program 4 times in a row, now is the timestamp suppost to be random like this?

Posted

If you handle the protocol correctly you are supposed to send your own sync request after you receive the 00 02 encryption response. Therefore those random 'timestamps' aren't used for very long.

 

The actual purpose is to prevent people overloading the server by sending lots of spoofed 00 01 packets (fx: ip in packet is fake). But the current method is flawed as the server must cache the hash (what is in the timestamp field) along with the ip while it waits for the 00 06 'sync response'. Catid came up with an alternative method but it isn't widely accepted yet.

Posted

Well I sent a sync response

00 06 (server timestamp integer) (my timestamp integer)

I do not get a 00 02, or anything after I send that packet. I am sending the packet like I sent the 00 01 packet, no reliable/encrypted packets or anything. Could you tell me what I might be doing wrong?

 

Here is a sync response packet I have sent:

sync responst sent: 0 6 6 33 0 21 114 42 186 0, size: 10

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