- tor-relays - lists.torproject.org

35C3 Tor Relay Operators Meetup
by 35C3 35C3 23 Dec '18

23 Dec '18

Hi nicoo, since you organized the tor relay operators meetups during the last few years at the CCC I was wondering if you will continue with that this year as well? If so, it would be great if we could get - a slightly bigger room than we had last year - a room with a beamer (Roger will not be there this year as he previously mentioned) The 35C3 wiki is not available yet. thank you!

2 2

Extreme Exit Policy
by John Ricketts 21 Dec '18

21 Dec '18

All, I am considering only allowing ports 53, 80, and 443 only. Discussion? John Ricketts Quintex Alliance Consulting

8 13

Re: [tor-relays] consensus-health.html and fallback dirs
by starlight.2018q2＠binnacle.cx 21 Dec '18

21 Dec '18

Ran the script: output is attached to this message for anyone interested. Live-network test results will vary by time and by the location of tester. Attached run was made over Tor itself using 'torsocks'. I was bit by having disabled the unencrypted DIR port for one day recently as an experiment. >Felix zwiebel at quantentunnel.de >Sun Dec 16 10:03:33 UTC 2018 > >>> I wonder how we can come from 116 running fallbacks to 155 within >>> one week (without a new release) > >Am 16.12.2018 um 08:01 schrieb starlight.2018q2 at binnacle.cx: >> The cause is >> >> https://gitweb.torproject.org/tor.git/commit/?id=78e177d622f5f3b24023d04458… > >Ah, great! This makes sense. It's a transient to the list update. > > > >> https://trac.torproject.org/projects/tor/ticket/24803 > >The upcoming one seems to be: >https://trac.torproject.org/projects/tor/ticket/28795 > >-- >Cheers, Felix >

2 1

Advice for new exit relay
by dns1983＠riseup.net 20 Dec '18

20 Dec '18

Hi, excuse my bad english. I would run an exit relay on a virtual server. For now i run just a non exit relay on my own mini server. I don't like too much do not have full control on the server, but, for me, it is the only way to run an exit relay. How do I know which service allow me to customize WHOIS records, so I can put my email address on report abuse section? Could you suggest me some providers that offer unlimited monthly data too? Regards Gigi

2 4

How to use a bridge configured with "ORport auto" within Tails?
by Toralf Förster 20 Dec '18

20 Dec '18

The Tails installer asked me for the bridge line (a bridge maintained by myself), but didn't accepted the ":auto" behind the ip address. I do wonder how to proceed? -- Toralf PGP C4EACDDE 0076E94E

2 3

Why are my relays flagged?
by Langrehr, Jan Christian 20 Dec '18

20 Dec '18

Hello everyone, I'm wondering why both of my Tor relays are flagged for running an unstable or outdated version or Tor. I'm running my relays on Ubuntu 18.04 and I get Tor from the deb https://deb.torproject.org/torproject.org bionic main repository. Both of my relays run Tor version 0.3.4.8. My relays are https://metrics.torproject.org/rs.html#details/9EDA50493B537837E72D83090BE4… and https://metrics.torproject.org/rs.html#details/8E57A56487EEA341965B77AE132E… I'm looking forward for an anwser. Thank you all very much

3 2

Re: [tor-relays] consensus-health.html and fallback dirs
by starlight.2018q2＠binnacle.cx 16 Dec '18

16 Dec '18

The cause is https://gitweb.torproject.org/tor.git/commit/?id=78e177d622f5f3b24023d04458… https://trac.torproject.org/projects/tor/ticket/24803 Would be appreciated if the Tor project published outputs of UpdateFallbackDirs.py job runs used when rebuilding the list. Thus operators who have expended effort to keep their relays eligible will know why when dropped. >Felix zwiebel at quantentunnel.de >Sat Dec 15 23:59:03 UTC 2018 > >Hi everybody > >Reading [1] shows the following statistics about the fallback dirs: > >Dec 5: >Running 116 >Not Running 0 >Missing 34 > >Dec 13: >Running 155 >Not Running 0 >Missing 2 > >Today (Dec 16) shows: >Running 151 >Not Running 0 >Missing 6 > >I wonder how we can come from 116 running fallbacks to 155 within one >week (without a new release): > > >Then I checked for some fallbacks and found: > >The relay with the fp F9246DEF2B653807236DA134F2AEAB103D58ABFE was a >fallback acc. fallback_dirs.inc until around 3.2.8rc, then it changed >ip. It is still in 2.9.x lts but with the old ip, recommended but >actually useless. > >Since around Dec 13 it is listed again [1] where it wasn't through 2018. > >The same with 8FA37B93397015B2BC5A525C908485260BE9F422. > >Are the two relays newly counted as running in [1], where they are >useless because of the changed ips? The new ips aren't in any >fallback_dirs.inc's and [2] shows no fallback flag. >Would thereby [1] look better than it is? > > >[1] https://consensus-health.torproject.org/consensus-health.html >[2] https://metrics.torproject.org/rs.html#details/F9246DEF2B653807236DA134F2AE… > >-- >Cheers, Felix

2 1

Re: [tor-relays] [OrNetRadar] NickPrefix: "AYAYA" (9)
by nusenu 16 Dec '18

16 Dec '18

Hello "AYAYA" relays > 2018-12-15 > > | Up | Ext | JoinTime | Nickname | Version | IP | AS | CC | ORp | Dirp | OS | Contact | eFamMembers | FP | > |------+-------+------------+------------+-----------+---------------+---------------+------+-------+--------+-------+-----------+---------------+------------------------------------------| > | 1 | 0 | 11:23:45 | AYAYA43 | 0.2.9.14 | 51.15.88.206 | Online S.a.s. | fr | 9001 | 9030 | Linux | None | 1 | D0BADF4222F4CE7DF6D91A772E391E29FDEA82FB | > | 1 | 0 | 11:24:20 | AYAYA46 | 0.2.9.14 | 51.15.113.238 | Online S.a.s. | fr | 9001 | 9030 | Linux | None | 1 | A4D98EE5916240F1AC6348174C40848B4C7F7C0C | > | 1 | 0 | 11:23:45 | AYAYA52 | 0.2.9.14 | 51.15.71.128 | Online S.a.s. | fr | 9001 | 9030 | Linux | None | 1 | 25C3DEAE9AA786559DBB072D0470D1A6FC408846 | > | 1 | 0 | 11:23:45 | AYAYA6 | 0.2.9.14 | 51.15.78.215 | Online S.a.s. | fr | 9001 | 9030 | Linux | None | 1 | BED1681C0DDEF5DE7B8A65E2603D262FE3B1DB59 | > | 1 | 0 | 11:23:45 | AYAYA64 | 0.2.9.14 | 51.15.43.15 | Online S.a.s. | nl | 9001 | 9030 | Linux | None | 1 | F6F70FEB215929701E027B9A436A38347D377367 | > | 1 | 0 | 11:23:44 | AYAYA70 | 0.2.9.14 | 51.15.85.153 | Online S.a.s. | fr | 9001 | 9030 | Linux | None | 1 | 64FDE6159C134C606A24ADBA7A3E9A66F3810465 | > | 1 | 0 | 11:23:45 | AYAYA8 | 0.2.9.14 | 51.15.35.170 | Online S.a.s. | nl | 9001 | 9030 | Linux | None | 1 | B9A1E0C135464554ACCE036A9B5AB6F9469A9703 | > | 1 | 0 | 11:23:45 | AYAYA90 | 0.2.9.14 | 51.15.83.14 | Online S.a.s. | fr | 9001 | 9030 | Linux | None | 1 | CCD5C2E7FABACCF8CD84BCDC8E689584881545B8 | > | 1 | 0 | 11:23:46 | AYAYA98 | 0.2.9.14 | 51.15.116.94 | Online S.a.s. | fr | 9001 | 9030 | Linux | None | 1 | 706A24208BE86E84B850ECAF42EC293CECE1ECC1 | > > https://nusenu.github.io/OrNetRadar/2018/12/15/a1 -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu

1 0

consensus-health.html and fallback dirs
by Felix 15 Dec '18

15 Dec '18

Hi everybody Reading [1] shows the following statistics about the fallback dirs: Dec 5: Running 116 Not Running 0 Missing 34 Dec 13: Running 155 Not Running 0 Missing 2 Today (Dec 16) shows: Running 151 Not Running 0 Missing 6 I wonder how we can come from 116 running fallbacks to 155 within one week (without a new release): Then I checked for some fallbacks and found: The relay with the fp F9246DEF2B653807236DA134F2AEAB103D58ABFE was a fallback acc. fallback_dirs.inc until around 3.2.8rc, then it changed ip. It is still in 2.9.x lts but with the old ip, recommended but actually useless. Since around Dec 13 it is listed again [1] where it wasn't through 2018. The same with 8FA37B93397015B2BC5A525C908485260BE9F422. Are the two relays newly counted as running in [1], where they are useless because of the changed ips? The new ips aren't in any fallback_dirs.inc's and [2] shows no fallback flag. Would thereby [1] look better than it is? [1] https://consensus-health.torproject.org/consensus-health.html [2] https://metrics.torproject.org/rs.html#details/F9246DEF2B653807236DA134F2AE… -- Cheers, Felix

1 0

17 new relays at OVH (2018-10-24)
by nusenu 13 Dec '18

13 Dec '18

Hi, if you are the operator that added 17 new relays at OVH on 2018-10-24 (full list bellow), please set a ContactInfo and especially the MyFamily in your torrc to avoid putting tor clients at risk. kind regards, nusenu > added on 2018-10-24 > > | Up | Ext | JoinTime | IP | CC | ORp | Dirp | Version | Contact | Nickname | eFamMembers | FP | > |------+-------+------------+---------------+------+-------+--------+-----------+---------------------------+--------------------+---------------+------------------------------------------| > | 1 | 0 | 13:43:16 | 145.239.0.204 | de | 443 | 0 | 0.3.4.8 | None | Chief | 1 | 5EF464D06322614A3B8B6C2652C3C616F098EE8A | > | 1 | 0 | 13:43:17 | 54.37.200.155 | fr | 443 | 0 | 0.3.4.8 | None | Dash | 1 | B55F8445569407FBE6BAF205799A9EF8AC8CC256 | > | 1 | 0 | 13:43:18 | 51.68.170.247 | fr | 443 | 0 | 0.3.4.8 | None | Rebel | 1 | E7B036D933D6E0A68983E8E3F664EAA54ACDEA37 | > | 1 | 0 | 13:43:20 | 51.75.82.166 | fr | 443 | 0 | 0.3.4.8 | None | Butch | 1 | 4809E3F9A73F5373734A4D23E7E7807A4743DD8A | > | 1 | 0 | 13:43:21 | 51.75.153.17 | fr | 443 | 0 | 0.3.4.8 | None | Beauty | 1 | B66FBE3B2D9CE257AF75DEA760C69E379F7CDB80 | > | 1 | 0 | 13:43:22 | 51.68.170.74 | fr | 443 | 0 | 0.3.4.8 | None | Killer | 1 | E4CB0C293588C3E5FA7DB94485FF2686E128267F | > | 1 | 0 | 13:43:23 | 51.68.185.141 | fr | 443 | 0 | 0.3.4.8 | None | Arrow | 1 | 707F51E232E0CDAF64EC446609E7112CD3AD11F8 | > | 1 | 0 | 13:43:24 | 54.37.207.82 | fr | 443 | 0 | 0.3.4.8 | None | Dazzle | 1 | B80142DDCF8D6B72929541EFCC643ECCD99BEE36 | > | 1 | 0 | 13:50:41 | 145.239.1.97 | de | 443 | 0 | 0.3.4.8 | None | Memo | 1 | 1C514FA1A4F8A464E1853B70AA5D2F16FF087AD2 | > | 1 | 0 | 13:50:42 | 51.38.107.122 | fr | 443 | 0 | 0.3.4.8 | None | Pitch | 1 | 91B026FA459AE0DA15673AB07A9C6DFF8B41782B | > | 1 | 0 | 13:50:43 | 51.68.186.59 | fr | 443 | 0 | 0.3.4.8 | None | Smasher | 1 | 3B0EFDE689693CFDEC2305F7B99D5B2FA4A77D91 | > | 1 | 0 | 13:50:44 | 51.75.85.114 | fr | 443 | 0 | 0.3.4.8 | None | Landslide | 1 | C953A4C8DF0E233CB0D190C2A71B71F634AB4A14 | > | 1 | 0 | 13:50:45 | 51.68.182.30 | fr | 443 | 0 | 0.3.4.8 | None | Shade | 1 | EBE58DDCC51A9D23EE9DD39791695B608A1DFB29 | > | 1 | 0 | 13:50:46 | 54.37.207.37 | fr | 443 | 0 | 0.3.4.8 | None | Buster | 1 | D10C82E275A2B0121CF4075C92687F0786A72892 | > | 1 | 0 | 13:50:47 | 54.37.200.157 | fr | 443 | 0 | 0.3.4.8 | None | Digger | 1 | 6B29A78EEB42D318290DB60C6A2EDC714F1BAD42 | > | 1 | 0 | 13:50:48 | 54.37.207.84 | fr | 443 | 0 | 0.3.4.8 | None | Pipi | 1 | 150F7C9F4814C4918F4D2DEAA0C7A2255DC8C0E0 | > | 1 | 0 | 13:50:49 | 51.75.153.19 | fr | 443 | 0 | 0.3.4.8 | None | Shrimp | 1 | 51429A0F427A8DCB5B9DE64E35ECBBB76DAB0F7F | -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu

2 1