rtsg.1023 > csam.login: S 768512:768512(0) win 4096 <mss 1024>
csam.login > rtsg.1023: S 947648:947648(0) ack 768513 win 4096 <mss 1024>
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.
>>54952939
Provide me with the documentation of said data format and I'll tell you.
We're not psychic.
>>54952976
while valid, incorrect.
>>54952994
nor am i. this is all i have to go off of. i was told this was enough.
i don't ask for much, /g/uys.
can you point me in the right direction?
solution found
give more pics from OP and I'll post.
>>54953192
...
>>54953242
horse shit that's her
i meant the girl from op
>>54953052
Unfortunate feet
>>54953264
>her
...
>>54953192 (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
>>54952939
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
![56774482_p1_master1200[1].jpg](https://i.imgur.com/dpQLZjj.jpg "56774482_p1_master1200[1].jpg")
Socks like that give me a boner.
>>54953323
...
Looks like tcpdump output
...
>>54953354
aw fuck she's gorgeous
alrighty you knobhead
> rtsg.1023 > csam.login: S 768512:768512(0) win 4096 <mss 1024>
> csam.login > rtsg.1023: S 947648:947648(0) ack 768513 win 4096 <mss 1024>
> 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
>>54953386
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
>>54953390
(20).
>>54953402
Glad I know what im doing. After I do this shit a lot at my job...
>>54953386
'preciate it. tcpdump isn't anything i even occasionally use.
>>54953417
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)
>>54953429
np m8, thx for the pix
>>54952939
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.
>>54953434
>>54953455
aw you're just spoiling me now ;)
>>54953402
>>54953454
thanks, all, for the enlightenment.
and to all, a good night.
>>54953469
'why not help someone in the process'
= ]
>>54953488
aw that's a good one to end on
~ goodnight
