Rtsg.1023 > csam.login: S 768512:768512(0) win 4096 <mss 1024>

rtsg.1023 > csam.login: S 768512:768512(0) win 4096
csam.login > rtsg.1023: S 947648:947648(0) ack 768513 win 4096
rtsg.1023 > csam.login: . ack 1 win 4096
rtsg.1023 > csam.login: P 1:2(1) ack 1 win 4096
csam.login > rtsg.1023: . ack 2 win 4096
rtsg.1023 > csam.login: P 2:21(19) ack 1 win 4096
csam.login > rtsg.1023: P 1:2(1) ack 21 win 4077
csam.login > rtsg.1023: P 2:3(1) ack 21 win 4077 urg 1
csam.login > rtsg.1023: P 3:4(1) ack 21 win 4077 urg 1

How much data, if any, was transfered from the client to the server?

None because your server is imaginary.

Provide me with the documentation of said data format and I'll tell you.

We're not psychic.

while valid, incorrect.

nor am i. this is all i have to go off of. i was told this was enough.

i don't ask for much, Sup Forumsuys.

can you point me in the right direction?

solution found
give more pics from OP and I'll post.

...

horse shit that's her
i meant the girl from op

Unfortunate feet

>her

...

(Me)
OP ya got a couple minutes before I'm hopping. More of first pic and I'll give you answer + explanation.

Lurking in hope of some more yellow puss

I know shit about shit. I would guess just by looking at it that where it says P1:2 it means one package of data out of 2 was sent?. Aren't TCP/IP standard in size? So calculate how many packs all together and multiply it by said size???

Why am I doing your fucking homework

Socks like that give me a boner.

...

Looks like tcpdump output

...

aw fuck she's gorgeous
alrighty you knobhead

> rtsg.1023 > csam.login: S 768512:768512(0) win 4096
> csam.login > rtsg.1023: S 947648:947648(0) ack 768513 win 4096
> rtsg.1023 > csam.login: . ack 1 win 4096
> rtsg.1023 > csam.login: P 1:2(1) ack 1 win 4096
> csam.login > rtsg.1023: . ack 2 win 4096
> rtsg.1023 > csam.login: P 2:21(19) ack 1 win 4096
> csam.login > rtsg.1023: P 1:2(1) ack 21 win 4077
> csam.login > rtsg.1023: P 2:3(1) ack 21 win 4077 urg 1
> csam.login > rtsg.1023: P 3:4(1) ack 21 win 4077 urg 1

tcpdump gives you a shitload of information, the key stuff to look for is the start:end(length) that you see a lot, such as the 1:2(1) or the 2:21(19). Incase that doesn't spell that out for you:
> find all instances of #:#(#)
> Grab 3rd number
> add them all together
thus, 0 + 0 + 1 + 19 + 1 + 1 + 1 =
> 23

if you like that, then post some more ;)

= *

I say 20 bytes

woops minor typo
23 was the total bytes sent in the entire transaction,
if you look just for rtsg.1023 > csam.login packets you get
(20).

Glad I know what im doing. After I do this shit a lot at my job...

'preciate it. tcpdump isn't anything i even occasionally use.

Honestly I haven't messed with tcpdump in a while, but the power of boners will get me to google some shit (probably would've quicker to just reverse search, but why not help someone in the process)

np m8, thx for the pix

Oh shit, those are hosts!
Non standard shit, but yeah.

rtsg.1024 > (sends) shit to csam.login and vice versa.

I thought it was some dump from Wireshark, but it's tcpdump.

...

aw you're just spoiling me now ;)

thanks, all, for the enlightenment.

and to all, a good night.

'why not help someone in the process'
= ]

aw that's a good one to end on
~ goodnight