On 2/12/10, Michael Holstein wrote:
>
>> Could you bind your exit traffic to IPs outside your University's
>> primary block?
>
> Not sure what you mean by "bind to outside IP", but our network is a
> contiguous /16. We would have to register for extra /24s from ARIN, and
> that costs money.
Not n
On Feb 12, 2010, at 5:27 PM, Michael Holstein wrote:
Why not simply block that entire network in the Exit policy?
You're missing the point .. we already blocked our *own* /16 in the
exit. The problem was the thousands of academic journals, all of which
have distinct addresses, that consider
> Why not simply block that entire network in the Exit policy?
You're missing the point .. we already blocked our *own* /16 in the
exit. The problem was the thousands of academic journals, all of which
have distinct addresses, that consider any traffic from our /16 as being
"on campus" and thus n
On Feb 12, 2010, at 3:42 PM, Michael Holstein wrote:
Could you bind your exit traffic to IPs outside your University's
primary block?
Not sure what you mean by "bind to outside IP", but our network is a
contiguous /16. We would have to register for extra /24s from ARIN,
and
that costs mo
> Could you bind your exit traffic to IPs outside your University's
> primary block?
Not sure what you mean by "bind to outside IP", but our network is a
contiguous /16. We would have to register for extra /24s from ARIN, and
that costs money.
Cheers,
Michael Holstein
Cleveland State University
On 02/11/2010 05:58 PM, Peter Farver wrote:
> I meant clients for TOR were blocked. Yes, for all students and
> faculty. I believe the attacks were from the TOR exit nodes, but I
> will try to get more information from network administrators. I have
> not tried bridges yet, but maybe I will obta
Il 11/02/2010 22:17, Michael Holstein ha scritto:
> .. but the above problem is ultimately what forced us to do the same
> thing (although we just prohibit the operation of an exit).
My university's department of computer sciences stopped an exit node
because both a) some DMCA notices for alleged
>
> > Why couldn't your exit policy just block the IPs of the journal sites?
>
> Because there's > 1000 of them (and each would be a /32). It was
> discussed in another thread at the time, and the developers led me to
> the conclusion that such hugely long exit policies were a bad idea.
Could you
On Thu, Feb 11, 2010 at 04:20:49PM -0500, Flamsmark wrote:
> On 11 February 2010 16:17, Michael Holstein
> wrote:
> > Let's not debate the stupidity of authenticating a network by IP address
> > .. but the above problem is ultimately what forced us to do the same
> > thing (although we just prohib
I meant clients for TOR were blocked. Yes, for all students and faculty. I
believe the attacks were from the TOR exit nodes, but I will try to get more
information from network administrators. I have not tried bridges yet, but
maybe I will obtain a bridge to connect to test in the future.
>>
> Why couldn't your exit policy just block the IPs of the journal sites?
Because there's > 1000 of them (and each would be a /32). It was
discussed in another thread at the time, and the developers led me to
the conclusion that such hugely long exit policies were a bad idea.
Cheers,
Michael Hol
On 11 February 2010 16:17, Michael Holstein wrote:
>
> Let's not debate the stupidity of authenticating a network by IP address
> .. but the above problem is ultimately what forced us to do the same
> thing (although we just prohibit the operation of an exit). I should
> note that the original effo
> TOR is now blocked campus-wide at Auburn University (for all 24,000 students)
> because of apparent attacks emanating from the TOR network.
If your problem is anything like the one we had, I'm guessing the
"attacks" have more to do with the fact that many journal subscriptions
authenticate by
Hi Peter,
When you say blocked are you saying that faculty, staff, and students
are not allowed to run exit nodes in the TOR network? Or rather that the
above are not allowed to use TOR clients to connect into the TOR
network?
Cheers,
Harry
On Thu, 2010-02-11 at 13:15 -0600, Peter Farver wrote:
On Thu, Feb 11, 2010 at 11:15 AM, Peter Farver wrote:
> TOR is now blocked campus-wide at Auburn University (for all 24,000 students)
> because of apparent attacks emanating from the TOR network.
can you elaborate on that?
are these apparent attacks coming _from_ the Tor exits or are Tor
clients
TOR is now blocked campus-wide at Auburn University (for all 24,000 students)
because of apparent attacks emanating from the TOR network. Whenever trying to
run TOR, TOR cannot get past the 10% mark. Would it have been wiser for Auburn
University to block incoming connections from TOR nodes, b
16 matches
Mail list logo
