Topic: Tor traffic exploding (Read 4135 times)
The Tor network can be used for a wide variety of things, it can host an attack, they can be setting up a new server network, etc., so i doubt that is the result of more traffic at silkroad.
Maybe a botnet owner has decided to donate his rooted machines.
I read an account, I thnk it was on reddit, of a guy who found his machine connecting to tor and acting as a relay on its own. It was infected.
Maybe a botnet owner has decided to donate his rooted machines.
I read an account, I thnk it was on reddit, of a guy who found his machine connecting to tor and acting as a relay on its own. It was infected.
Maybe a botnet owner has decided to donate his rooted machines.
I read an account, I thnk it was on reddit, of a guy who found his machine connecting to tor and acting as a relay on its own. It was infected.
I don't know the impact on battery yet.
I don't know the impact on your monthly bandwidth yet.
Actually, there shouldn't be any significant difference in that case. Unless you do lots of telnet, ssh and other frequent-tiny-packets protocols, Tor shouldn't really increase your bandwidth usage.
Quote
An alternative recurring explanation is the increased usage of botnets using Tor, based on the assertion that the increase appears to consist of mostly new users to Tor that apparently are not doing much given the limited impact on Tor exit performance. In recent days, we have indeed found evidence which suggests that a specific and rather unknown botnet is responsible for the majority of the sudden uptick in Tor users. A recent detection name that has been used in relation to this botnet is “Mevade.A”, but older references suggest the name “Sefnit”, which dates back to at least 2009 and also included Tor connectivity. We have found various references that the malware is internally known as SBC to its operators.
http://blog.fox-it.com/2013/09/05/large-botnet-cause-of-recent-tor-network-overload/
Also of importance to Tor users.
http://www.dailydot.com/news/tor-project-windows-firefox-vulnerability/
http://www.dailydot.com/news/tor-project-windows-firefox-vulnerability/
at SF ballgames i get seats near the concession stands and they have several big screen TVs showing the aired feed so fans can watch the replays.
That's handy. I'm surprised the umpires' union lets them get away with that.
We don't get that option at Skydome. Since I prefer to sit directly behind home plate near the front of the top deck, my only choice is the Jumbotron.
I'm not complaining though. By buying a 15-game flex-pack, I get my seats for $2 less than the cost of a beer. I attended 2 of 3 games in a recent series against the Yankees and the ticket (way out by 3rd base) that I bought at the box office cost twice as much as my flex-pack seat right behind the plate.
i use tor to watch blacked out mlb.com ballgames.
Yeah, it's better than Vipbox because mlb.com removes the commercials, while Vipbox leaves them in.
I'm lucky because it seems I somehow got my MLB.TV account cleared to watch all games (commercial-free) including Jays games which are normally blacked out in all of Canada.
Now if only Android had better Flash support so I could take my 7" shirt-pocket tablet to Skydome for "instant" (delayed only by buffering time) replays of controversial calls.
at SF ballgames i get seats near the concession stands and they have several big screen TVs showing the aired feed so fans can watch the replays.
Wait, what?! You guys use Tor to watch video streams? What bitrate is that?
Ya that's a surprise unless tricking the geo-check is all that is required and the streaming is done over the plain NSA ruled internet.
It seems to me though that going through the TOR network would just lead to longer buffering times, with Firefox compensating. Am I totally off-base with this?
sometimes, yes. sometimes you get a decent connection. i usually use a lower bitrate/video quality so it doesnt buffer much.
Wait, what?! You guys use Tor to watch video streams? What bitrate is that?
Ya that's a surprise unless tricking the geo-check is all that is required and the streaming is done over the plain NSA ruled internet.
It seems to me though that going through the TOR network would just lead to longer buffering times, with Firefox compensating. Am I totally off-base with this?
Wait, what?! You guys use Tor to watch video streams? What bitrate is that?
Ya that's a surprise unless tricking the geo-check is all that is required and the streaming is done over the plain NSA ruled internet.
Wait, what?! You guys use Tor to watch video streams? What bitrate is that?
i use tor to watch blacked out mlb.com ballgames.
Yeah, it's better than Vipbox because mlb.com removes the commercials, while Vipbox leaves them in.
I'm lucky because it seems I somehow got my MLB.TV account cleared to watch all games (commercial-free) including Jays games which are normally blacked out in all of Canada.
Now if only Android had better Flash support so I could take my 7" shirt-pocket tablet to Skydome for "instant" (delayed only by buffering time) replays of controversial calls.
i use a vpn which automatically activates on my phone and pc's. it's great and i pay with btc.
i use tor to watch blacked out mlb.com ballgames.
You posted the same chart with a differently-scaled x-axis...
Oh, crap. I was focused on the title of the thread, which said that network traffic was exploding, and was amazed to see the number of users exploding, too... That, and maybe the amyloid deposits in my brain... 
Do you think SilkRoad volume is increasing and this has an effect on price?
The spikes in the plot above are obviously outliers if you look at the variance of the rest of the data. I have no idea how to explain them. More alarming is the estimated number of users:
You posted the same chart with a differently-scaled x-axis...
if u drill down u will notice that certain countries have a 3 to 4x increase in users over the last 2 weeks.
and directory services are taking hit
https://metrics.torproject.org/network.html
and directory services are taking hit
https://metrics.torproject.org/network.html
Jump to: