Re: [tor-relays] clarification on what Utah State University exit relays store ("360 gigs of log files")

2015-08-08 Thread Sharif Olorin
> I would expect most US universities to be logging netflow in the very > least. Even if the Tor operator isn't keeping logs, it seems safe to assume > the network operator is. I'd be surprised if it was different for non-US universities - I'd expect this to be the case for every university with i

Re: [tor-relays] Guard flag flapping

2015-08-08 Thread Green Dream
On Sat, Aug 8, 2015 at 1:41 AM, wrote: > > I ran some tests against your node. While performance is generally very > good, it has very low performance connecting to some exit nodes. Thanks for running the tests. Which exit nodes led to poor performance? I would like to try to reproduce any perf

Re: [tor-relays] clarification on what Utah State University exit relays store ("360 gigs of log files")

2015-08-08 Thread Green Dream
>> If you can confirm that the comment is authentic I'd be interested >> what kind of tor related data you are logging at your exit relays and why. > It's most likely netflow logs. Quite popular in Uni / regional ISP > environments. People collect them for network stats, and to track > down "secur

Re: [tor-relays] BoingBoing: What happened when we got subpoenaed over our Tor exit node

2015-08-08 Thread grarpamp
On Fri, Aug 7, 2015 at 5:38 PM, Damian Busby wrote: > Personally, if I had been the person in comment #2, I would have sent all > those logs anyway. Mind telling us what relays you're operating so we can block them in our clients? > Then they would have been compelled to review them. That's up

Re: [tor-relays] clarification on what Utah State University exit relays store ("360 gigs of log files")

2015-08-08 Thread grarpamp
On Sat, Aug 8, 2015 at 2:03 AM, nusenu wrote: > that implies that USU exit relays store significant amount of logs > >> node. I said that we had extracted and filtered the requested data, >> it was 90 4 gig files (for a total of 360 gigs of log files) or >> about 3.2 billion log entries. > > If yo

Re: [tor-relays] Guard flag flapping

2015-08-08 Thread torrry
Original Message From: starlight.201...@binnacle.cx Apparently from: tor-relays-boun...@lists.torproject.org To: tor-relays@lists.torproject.org Subject: [tor-relays] Guard flag flapping Date: Sat, 08 Aug 2015 14:39:48 -0400 > My advice is that this QWest service is third-rate >

[tor-relays] Guard flag flapping

2015-08-08 Thread starlight . 2015q3
[apologies to all for thread-breaking, am really going on hiatus but the horror-show performance GBE topic was too darn interesting--last post I promise!] >I would call it a dedicated gigabit link. This is >probably up for debate. The provider's overall >capacity is very likely not [number of

Re: [tor-relays] OT: starlight vs. email threading

2015-08-08 Thread Roman Mamedov
On Sat, 08 Aug 2015 11:23:52 -0400 starlight.201...@binnacle.cx wrote: > Hi nusenu, > > Normally I respond to list messages > and threading works, but lately > I've turned off list delivery > in an effort to pay less attention > to the tor-relays list. Sorry about > the resultant messy thread co

[tor-relays] Guard flag flapping

2015-08-08 Thread starlight . 2015q3
>The problem is likely that your ISP is routing >some traffic via an overloaded peering point. Running traceroute -w 1 -q 5 -A 1400 may provide more detail on this issue. The -A option causes 'traceroute' to show Autonomous System numbers with each route hop, where ASNs are Internet routing

[tor-relays] Guard flag flapping

2015-08-08 Thread starlight . 2015q3
>. . .have physical access to the . . . ONT. > Doubt this is the case, but on the off chance that the ONT is configured to flow IP traffic over a coaxial cable attached to a CPE router (customer premise equipment), the configuration should be changed to deliver data over a Gigabit Ethernet directl

Re: [tor-relays] OT: starlight vs. email threading

2015-08-08 Thread starlight . 2015q3
Hi nusenu, Normally I respond to list messages and threading works, but lately I've turned off list delivery in an effort to pay less attention to the tor-relays list. Sorry about the resultant messy thread continuity. With luck I'll be posting less, and if I come back in a few weeks or months I

Re: [tor-relays] onionoo.thecthulhu.com: 500 Server Error

2015-08-08 Thread nusenu
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 > it'll need to catch up on the data. Thanks for the info. There might be a problem with the data as well: https://lists.torproject.org/pipermail/tor-dev/2015-August/009227.html -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJVxgm5AAoJEFv7XvVCELh0gZ

Re: [tor-relays] onionoo.thecthulhu.com: 500 Server Error

2015-08-08 Thread Thomas White
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Karsten just gave the thing a boot. The classic "Have you turned it off then on again?" scenario because you know, we're all cybering. Give it a few hours and we'll check on it again as I imagine it'll need to catch up on the data. T On 08/08/2015 0

[tor-relays] OT: starlight vs. email threading

2015-08-08 Thread nusenu
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 hi starlight, is there any chance we can talk you into setting the usual email headers for proper email threading? (decent MUAs take care of this by default) At times it is hard to follow the flow of a discussion if every email starts a new thread

Re: [tor-relays] Guard flag flapping

2015-08-08 Thread torrry
Original Message From: Green Dream Apparently from: tor-relays-boun...@lists.torproject.org To: tor-relays@lists.torproject.org Subject: Re: [tor-relays] Guard flag flapping Date: Fri, 7 Aug 2015 21:49:16 -0700 > I've learned from this thread that the Guard flag flapping is a d