Re: [tor-relays] "Bug: Duplicate call to circuit_mark_for_close"

2017-10-18 Thread tor
> 0.3.1.7 is stable Earlier in the thread you said "I wouldn't recommend upgrading to 0.3.0 or later, there are stability issues on some clients, and maybe relays." That's what I was referring to. I think we're having a semantic argument; "stable" release doesn't always mean the software is

Re: [tor-relays] atlas.cogentco.com Is blocking

2017-10-18 Thread Andy Isaacson
On Thu, Oct 19, 2017 at 01:19:21AM +, Paul Templeton wrote: Whoever runs that node will need to talk to their ISP support team to get it unblocked. Thanks Andy - the reason I asked because its not with the Service Provider it's there upstream carrier - I have lodged a ticket with the

Re: [tor-relays] atlas.cogentco.com Is blocking

2017-10-18 Thread Paul Templeton
> Whoever runs that node will need to talk to their ISP support team to get it unblocked. Thanks Andy - the reason I asked because its not with the Service Provider it's there upstream carrier - I have lodged a ticket with the carrier and waiting to here back. The ISP doesn't know anything. I

Re: [tor-relays] atlas.cogentco.com Is blocking

2017-10-18 Thread Andy Isaacson
On Wed, Oct 18, 2017 at 11:48:33PM +, Paul Templeton wrote: Has anyone come across a scenario where a carrier blocks IP traffic? atlas.cogentco.com is the point which drops any packet to 95.130.9.210 From where I sit it looks like .210 is null-routed. All of my ISPs drop the packets as

[tor-relays] atlas.cogentco.com Is blocking

2017-10-18 Thread Paul Templeton
Has anyone come across a scenario where a carrier blocks IP traffic? atlas.cogentco.com is the point which drops any packet to 95.130.9.210 The server is up and running internal monitoring says its OK. The ISP doesn't provide an interface to the Server so I can not log on to do any other

Re: [tor-relays] "Bug: Duplicate call to circuit_mark_for_close"

2017-10-18 Thread teor
> On 19 Oct 2017, at 08:17, tor wrote: > > It's a shame there's no Ubuntu package for the long-term support Tor release. > Thanks Teor for filing a ticket, but it doesn't look like it will be acted > upon. It seems like a problem to me. I guess it's a matter of what is >

Re: [tor-relays] "Bug: Duplicate call to circuit_mark_for_close"

2017-10-18 Thread tor
> I doubt this bug is the cause if it's just happened recently. > It's more likely that your relay is the HSDir for some popular > onion service. Or a genuine DDoS. I still don't know what's going on. I'd say any of these are possibilities: - The bug that results in fallback directories getting

[tor-relays] vsif.ca relays: MyFamily configuration

2017-10-18 Thread nusenu
Hello Vancouver Society for Internet Freedom, thanks for running tor relays. Unfortunately you are in a position that can potentially harm tor users if you do not set MyFamily (torrc) on all your relays. Please have a look at your MyFamily configuration.

Re: [tor-relays] tor LTS (0.2.9) repo

2017-10-18 Thread nusenu
> Thanks the info. Unfortunately I upgraded to 0.3.1.7 before reading this (it > didn't help), and can't figure out how to obtain 0.2.9.12 from the repos. > I've tried these repos: > > deb http://deb.torproject.org/torproject.org trusty main > deb http://deb.torproject.org/torproject.org