Re: hidden services stopped working

2016-06-12 Thread polezaivsani
Took the same path - updated to the latest snapshot and could no longer access hidden services, while clearnet routing worked just fine. I also route all the traffic through tor transparently. In my case though there was no time jitter but it turned out that the 127/8 -> 127.0.0.1 route got

Re: hidden services stopped working

2016-06-01 Thread Chris Cappuccio
I have several i210s on Supermicro motherboards and now APU2, and I haven't seen these issues. I wonder if your problem is related to a combination of features? Have you tried to isolate what process or kernel feature makes this behaviour occur? Juuso Lapinlampi [w...@partyvan.eu] wrote: > This

Re: hidden services stopped working

2016-05-31 Thread ares
I'm not sure it's the same problem. Though it sounds interesting, what's in your torrc? Try the enabling: CloseHSClientCircuitsImmediatelyOnTimeout 1 CloseHSServiceRendCircuitsImmediatelyOnTimeout 1 UserspaceIOCPBuffers 1 AvoidDiskWrites 1 I'm not sure what happened to my setup quite yet I've

Re: hidden services stopped working

2016-05-31 Thread Juuso Lapinlampi
This may be related: em(4) interface hangs randomly, receive buffer full (Intel i210) https://marc.info/?l=openbsd-misc=145696725605233=2 I've been having those Tor hangs for months. The same issue, clock skips ahead some minutes and breaks Tor connections but not clearnet. They happen quite

Re: hidden services stopped working

2016-05-28 Thread ares
Ok, I'm not sure where how this thread went sideways quite so quickly but just to be clear I'm running as of right now the most current snapshot available on ftp5.usa and the only things I have installed are lynx and tor, I have made sure the system time is correct and turn tor's log doesn't throw

Re: hidden services stopped working

2016-05-28 Thread Theo de Raadt
> a...@riseup.net: > > Thanks for the reply and the help Ivan but I'm actually already doing > > exactly > > what you suggested. Checking the time is one of the first things I thought > > of > > but this is not that unfortunately. I don't have this problem on 5.9 myself > > and even snapshots

Re: hidden services stopped working

2016-05-28 Thread Ivan Markin
Theo de Raadt: > I am really impressed by the analytical skills I observe here. > > I observe: "the system is complex, I can't figure it out, I'll blame > everything, and use more stuff I don't understand". The problem is definely with ntpd because ntpd reports about invalid-then-valid peers to

Re: hidden services stopped working

2016-05-28 Thread ares
Thanks for the reply and the help Ivan but I'm actually already doing exactly what you suggested. Checking the time is one of the first things I thought of but this is not that unfortunately. I don't have this problem on 5.9 myself and even snapshots were fine up until the update. Your problem is

Re: hidden services stopped working

2016-05-28 Thread Ivan Markin
a...@riseup.net: > Thanks for the reply and the help Ivan but I'm actually already doing exactly > what you suggested. Checking the time is one of the first things I thought of > but this is not that unfortunately. I don't have this problem on 5.9 myself > and even snapshots were fine up until the

Re: hidden services stopped working

2016-05-28 Thread Ivan Markin
Theo de Raadt: >> As a quick fix I recommend you to disable `ntpd` [2] and use `tlsdate` >> [3] to fetch time over TLS. It works fine for me for several days by now. > > That is the worst possible advice ever. > > You are far better off letting your machines free-run. Why it's so wrong? ares,

Re: hidden services stopped working

2016-05-28 Thread Ivan Markin
Hi ares, a...@riseup.net: > After a snapshot update on the 26th for amd64 I have lost the ability to > connect to hidden services. I have pf rules to transparently proxy all > connections taken from the wiki @ https://trac.torproject.org/projects/ > tor/wiki/doc/TransparentProxy#BSDPF. With the

Re: hidden services stopped working

2016-05-28 Thread Theo de Raadt
> As a quick fix I recommend you to disable `ntpd` [2] and use `tlsdate` > [3] to fetch time over TLS. It works fine for me for several days by now. That is the worst possible advice ever. You are far better off letting your machines free-run.