People Who Know about RTSP!

So I'm currently testing a method I have figured out and find that the result in Wireshark is different that seen before when using SPK/MV/YTF etc...

Can someone enlighten me and tell me what this value is, if you know what your talking about when it comes to RTSP!!

'FIN: SET'... I'm guessing its the finish value and therefore potentially counting views!...

Would Love to Know!

Thanks

Check the Image below..

http://tinypic.com/view.php?pic=2433pyb&s=6

You mean the teardown parameter? I already tried that. Giving 10 views to a video with RTSP using these new params resulted in 0 views. 10k views resulted in 30 views.

Thanks for your quick reply!
Yeah, I obviously know about the teardown Paramater, it's just I have never seen a value of 1 next to the FIN: SET Flag..

So you are getting this value too from what you've tested?

FIN has nothing to do with RTSP, at least in the sense of what you're looking for. It is a FLAG associated with the underlying TCP protocol (SYN, FIN, ACK, etc) that initiates a teardown of a TCP connection.

Can you explain why it happens in some instances and the majority not?

Looks like a bad news.

I will be pray youtube that it will be not work anymore
And you need to stop creating fuck threads about RTSP views,mobile views,or something like that when youtube has other loopholes

then name those loopholes

antonio69 said:

I will be pray youtube that it will be not work anymore
And you need to stop creating fuck threads about RTSP views,mobile views,or something like that when youtube has other loopholes

Click to expand...

antonio69.. Why the hating.. not exactly like I'm asking for a bot, like the majority of wankers on this forum, I'm taking the initiative to create 1 so hush your gums bro..

Dark Lord said:

FIN has nothing to do with RTSP, at least in the sense of what you're looking for. It is a FLAG associated with the underlying TCP protocol (SYN, FIN, ACK, etc) that initiates a teardown of a TCP connection.

Click to expand...

this

they seem to be getting better at filtering teh fake rtsp views ;D

Bro move on. You should try something that is more efficient. Vagex and others still work well.

Na Bro.. Vagex is shit...!.. and if i moved on, I wouldn't work it out!.. don't give up man with whatever you do, to just move on is a losers game!

Man it's just about the IP addresses. You need proxies and a lot of them. Kind of odd they never took IP's into account from the start. Sure mobile phones share IP addresses, but there is still a shit ton of them, and it's unlikely you will get too many users with the same IP who watched the same video within a short period of time of each other.

Hmm..

Ok thanks man

FIN: SET means that the FIN flag is set (ie set to 1)

this means that the host that sent wants to close the connection

the reason the flag is not always set is because of some anti congestion algos that govern over how tcp works (naggle algo)

if you send info to the server/client you use let's say tcpsend('somedata') that data is not sent instantly it's put in a buffer and awaits sending
but if you call another tcpsend('otherdata') or tcpclose before the buffer is sent... all the data will be sent together


so you call tcpsend("etc....")
and then tcpclose

if the buffer was emptied before tcp close you would see to packets.. one with data and no FIN flag + one empty with the FIN flag

if the buffer was not emptied you would get one packet with data and FIN

this has nothing to do with the rtsp session either way the application on the other end probably won't even care if you sent 1 or 2 packets for this

if you disable naggle's algo then you will see data with fin always 0 and an empty packet right after it with fin 1