Re: [tor-relays] obfs4 bridge stuck at 0% bootstrap
When I was running a bridge on my Raspberry Pi the only success I had was when I compiled from source. Don’t be overwhelmed, the instructions are very easy to follow. https://2019.www.torproject.org/docs/debian.html.en On Tue, Oct 8, 2019 at 4:16 AM, Alexander Dietrich wrote: > You can use "deb.torproject.org" in Raspbian: > https://support.torproject.org/apt/tor-deb-repo/ > >> Volker Mink hat am 8. Oktober 2019 um 08:29 geschrieben: >> >> Could be, i am not so deep into this whole linux-magic. >> Its raspian stretch with kernel 4.19.66 on a PI2B, which is -as far as i >> know- from august 2019. >> >> apt install tor offers me tor version 2.9.6.xx, enabling the experimental >> from debian-stack offers 0.3.4.x >> >> Any idea how to get a newer version? >> >> Gesendet: Dienstag, 08. Oktober 2019 um 01:09 Uhr >> Von: "Roger Dingledine" >> An: tor-relays@lists.torproject.org >> Betreff: Re: [tor-relays] obfs4 bridge stuck at 0% bootstrap >> On Mon, Oct 07, 2019 at 11:09:53PM +0200, Volker Mink wrote: >>> After a fresh installation syslog is full with entries like this: >> [...] >>> Oct 7 23:05:09 pi-hole systemd[1]: Failed to start Anonymizing >>> overlay network for TCP. >> >> My next guess is that you have an old-style raspbian, with an old >> arm-based cpu architecture that is not compatible with modern Debian, but >> you have installed the modern Debian tor deb. If that's what's happening, >> the binary won't run because it's for a different arch. >> >> Now your quest has simplified to "get Tor running at all, by figuring >> out what operating system you're actually running, and finding an >> up-to-date Tor package that is intended for that operating system." :) >> >> --Roger >> >> ___ >> tor-relays mailing list >> tor-relays@lists.torproject.org >> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays >> ___ tor-relays mailing list >> tor-relays@lists.torproject.org >> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] New relay in USA: bridge or middle relay?
Good morning from Wisconsin, After reading about how middle relays in the USA go largely underutilized, and having quietly run my own middle relay for several years, would it be more beneficial to the network to launch several new bridges instead of more middle relays? Make your day great, Isaac Grover, Senior I.T. Consultant Aileron I.T. - " Because #ProactiveIsBetter " O: 715-377-0440, F:715-690-1029, W: www.aileronit.com ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] obfs4 bridge stuck at 0% bootstrap
You can use "deb.torproject.org" in Raspbian: https://support.torproject.org/apt/tor-deb-repo/ > Volker Mink hat am 8. Oktober 2019 um 08:29 geschrieben: > > Could be, i am not so deep into this whole linux-magic. > Its raspian stretch with kernel 4.19.66 on a PI2B, which is -as far as i > know- from august 2019. > > apt install tor offers me tor version 2.9.6.xx, enabling the experimental > from debian-stack offers 0.3.4.x > > Any idea how to get a newer version? > > > > Gesendet: Dienstag, 08. Oktober 2019 um 01:09 Uhr > Von: "Roger Dingledine" > An: tor-relays@lists.torproject.org > Betreff: Re: [tor-relays] obfs4 bridge stuck at 0% bootstrap > > On Mon, Oct 07, 2019 at 11:09:53PM +0200, Volker Mink wrote: > > After a fresh installation syslog is full with entries like > this: > [...] > > Oct 7 23:05:09 pi-hole systemd[1]: Failed to start Anonymizing > overlay network for TCP. > > My next guess is that you have an old-style raspbian, with an old > arm-based cpu architecture that is not compatible with modern Debian, > but > you have installed the modern Debian tor deb. If that's what's > happening, > the binary won't run because it's for a different arch. > > Now your quest has simplified to "get Tor running at all, by figuring > out what operating system you're actually running, and finding an > up-to-date Tor package that is intended for that operating system." :) > > --Roger > > ___ > tor-relays mailing list > tor-relays@lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > > > ___ tor-relays mailing list > tor-relays@lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] obfs4 bridge stuck at 0% bootstrap
Could be, i am not so deep into this whole linux-magic. Its raspian stretch with kernel 4.19.66 on a PI2B, which is -as far as i know- from august 2019. apt install tor offers me tor version 2.9.6.xx, enabling the experimental from debian-stack offers 0.3.4.x Any idea how to get a newer version? Gesendet: Dienstag, 08. Oktober 2019 um 01:09 Uhr Von: "Roger Dingledine" An: tor-relays@lists.torproject.org Betreff: Re: [tor-relays] obfs4 bridge stuck at 0% bootstrap On Mon, Oct 07, 2019 at 11:09:53PM +0200, Volker Mink wrote: > After a fresh installation syslog is full with entries like this: [...] > Oct 7 23:05:09 pi-hole systemd[1]: Failed to start Anonymizing overlay network for TCP. My next guess is that you have an old-style raspbian, with an old arm-based cpu architecture that is not compatible with modern Debian, but you have installed the modern Debian tor deb. If that's what's happening, the binary won't run because it's for a different arch. Now your quest has simplified to "get Tor running at all, by figuring out what operating system you're actually running, and finding an up-to-date Tor package that is intended for that operating system." :) --Roger ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] Questions about Fallbacks
Hi, when i setted up my relays i choosed 443 as the ORPort. My thought behind it was that 443 is most likely not blocked and less likely observed because the ISP could expect to anyway only see encrypted data so a Tor connection will more likely slip through it. I let the DirPort on 9030 because i read that clients anyway only use the ORPort and i thought if a authority will connect to me it makes no difference because none of my ports is blocked. Now some of my relays are Fallbacks. Would it be a benefit for the network if i change the DirPort to 80 or is the DirPort still not used by clients? Is it necessary to opt-out the relay as a fallback if it was shut down by the provider and already is long gone from metrics? ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
