[Help] Packets ...

[romeoromeo]

Greetings every one ...
i have searched on the fourms here about any thread that teach
anything about packets . and i have read all what i found and almost was
able to understand what posted on them .... but got 150% fail to find
anything related to packets on Google search . ... and its almost impossible
to learn it in real life coz many factors started with destance .. .
so , my question is ... if any of you have anything related to packets in
general ... on this fourm or any other sites . or if you have ur own knowldge
(and time ) to post it here in this topic .. i would be very thankful for all of you .
it doesnt have to be related to TQ packets . im trying to understand
packets in general .. like :
1- how to find or hunt them .
2- how to sort out the wanted ones .
3- how to analize .
4- how to write the correct code for the wanted packet.
.... i almost know about how to find ( using programs ) and also how to
analize ( not sure but i think fang realise it b4 ) , sorry to forget the thread
owner's name ..
and the last thing is related to conquer i dont really care if
you did not answer this last part ... its about the socket code , if
you can explain it in general or even factors about how to make my own
socket code

have a wonderful day and Thanks for alll

[BaussHacker]

Packets have nothing to do with sockets other than sockets send/receive them.

And here you go:

[pro4never]

Originally Posted by BaussHacker

Packets have nothing to do with sockets other than sockets send/receive them.

And here you go:

Ooh you with your shameless self promotion and dashing good looks...

hey, wait! Is that sum hypocrisy I see approaching?



With the key thing to pull from it being...



Once you understand what packets are, how they are structured and what that means for conquer then you can work your way into applying them to actual programming imho.

[romeoromeo]

Originally Posted by BaussHacker

Packets have nothing to do with sockets other than sockets send/receive them.

And here you go:

i know that packets and sockets are diff... the packets was 1st question which i care to find the answer ... and socket was the 2nd and last question which i dont care that much to know about it now ...
Thank you for the fast answer

Originally Posted by pro4never

Ooh you with your shameless self promotion and dashing good looks...

hey, wait! Is that sum hypocrisy I see approaching?



With the key thing to pull from it being...



Once you understand what packets are, how they are structured and what that means for conquer then you can work your way into applying them to actual programming imho.

Thank you so much ... i still have questions but will not ask any right now . coz i see a new link here . so i will read it carefuly first , then ask away if i did not get the answer from threads . Thanks alot for help .

Hello Again ,
First : THE SOCKET ...
the socket thread was excellent , but there is some factors that lead connection to fail still do not know what does it even mean . or why it used example >>
if (type == 1060) OR
CAST_cfb64_encrypt OR
GameCryptographyKey = "BC234xs45nme7HU9"


in fact i do want to understand it how it go, not with codes but with logic order . for example >>
1- listen , 2- recive call 3- check 4- accept or reject 5- connect
just the logic order with more details . i do not want any code at all . so you can be so sure there is no copy and paste thing... just want a step by step .......as if you follow the code , it go from here to there , and do that then that . .... coz if i know what i want to do , then i can know what should i do to get it , and i think this is the goal we are all trying to get , either teachers ( like u ) or studients ( like me ) and i hope that you will understand what do i mean , coz i feel that i always ask my question with a wrong way that cause a wrong answer usually . im sorry for that .

2nd is the Packets :
just one question . how to know how many bytes are needed for each thing ,
and again i do not mean conquer packets . lets say that i have myown packet from network. and want to analyse it .
but will give my example here for a conquer packet .
if we say that packet is >>>
Length + Type + UID + TargetUID + seal ( just example its not packet at all lol )
how would i find out how many bytes are needed for the UID OR the Target UID ... is it the exetra Zeros ??? for example if the uid xx xx xx 00 00 so its 5 bytes ?
and if its not the excetra zeros , then what ? ...
i hope that you can explain it with a real packet that Does not belong to conquer at all

[romeoromeo]

Hello Again . ... ...
too bad no answer here yet :-(
anyway ... i think i have found what i wanted .. but one more question still , coz my english is not that good to hear it well . what is the logger do in this vedio ...

... you can only write what he says about it if you can hear it well .... early thanks for who gonna Help.

[Lateralus]

A "packet" is just composed of packed data sent between applications. The length of its fields and information they contain is arbitrary and is determined (and split apart into its corresponding fields to be processed) by the applications.

If you want to find out how the client and server interpret this data, you can do it in two basic ways. First, and easiest, is develop a proxy that logs packets by establishing a connection between the client and server and receiving and printing out the contents of the packets. The other way that requires more experience is analyzing the compiled client and server applications in-depth with a debugger. In both methods, you have to logically deduce what the fields represent.

An example not pertaining to conquer is a chat program like WLM or yahoo. I want to say that the packets sent aren't encrypted, but I may be wrong.


For example, say a packet from a chat program contains 3 null terminated strings, and the dump (in ASCII strings) looks like this:

Lateralus\0PersonTo\0Hey! Here's a message!\0

Well, it's pretty obvious what these fields represent. The first is a null-terminated string of who the message is from, the second is a null-terminated string of who the message is to, and the last is the null-terminated message. If this is sent from the client program to the server, the server may do a lookup if PersonTo is online (or other conditions), and if this proves true, it may send it to the other client... which then splits apart the 3 strings and processes to display it like so:

Lateralus speaks to PersonTo:
Hey! Here's a message!

Of course, a more developed chat application probably has fields representing fonts, colors, and such, but hopefully you get the point... it's all "arbitrary" of how packets are designed.

[romeoromeo]

Thank you so much Lateralus