- tor-relays - lists.torproject.org

Outgoing Connections to middle nodes?
by balbea16 03 Dec '16

03 Dec '16

Hi There, I've got a quick question. I have been running a tor relay since 3 months. I don't have a guard flag, however many outgoing connections to non exit relays (i.e. that should be middles than). Does that mean I run an entry node (without having guard status)? How come?TNX Mike

4 3

Re: [tor-relays] Outgoing Connections to middle nodes?
by balbea16 03 Dec '16

03 Dec '16

TNX for the fast response. Unfortunately I can't open .asc files on my mobile phone. I've to try this later at home. Von meinem Samsung Gerät gesendet. -------- Ursprüngliche Nachricht -------- Von: nusenu <nusenu(a)openmailbox.org> Datum: 03.12.16 13:12 (GMT+01:00) An: tor-relays(a)lists.torproject.org Betreff: Re: [tor-relays] Outgoing Connections to middle nodes? _______________________________________________ tor-relays mailing list tor-relays(a)lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

1 0

Re: [tor-relays] [OrNetRadar] AS: "Choopa, LLC" - Linux (20), "GMO Internet, Inc" (10)
by nusenu 30 Nov '16

30 Nov '16

I hope you got them on your radar as well. Wondering for which HS they will become the hsdir +------------+----------+-------+----------------------+ | FP | nickname | hsdir | as_name | +------------+----------+-------+----------------------+ | 0759DB6F6C | schedule | 0 | GMO Internet,Inc | | 0759DB6F9F | dengue | 0 | GMO Internet,Inc | | 0759DB6FA6 | Almond | 0 | GMO Internet,Inc | | 09A54DB0F2 | epitome | 1 | Choopa, LLC | | 09A54DB35E | euler | 0 | GMO INTERNET PTE LTD | | 09A54DB3F5 | niche | 1 | GMO Internet,Inc | | 1F00D604D2 | Unnamed | 0 | Choopa, LLC | | 2FDDD920C8 | fufu | 0 | Choopa, LLC | | 32E71B90DA | zebra | 0 | GMO Internet,Inc | | 3968276F7A | pizza | 0 | Choopa, LLC | | 71363B816E | dessert | 0 | GMO Internet,Inc | | 71363B83B2 | bury | 0 | GMO Internet,Inc | | 905CC77C4B | sour | 0 | Choopa, LLC | | A0E83AA0E2 | bowl | 1 | GMO Internet,Inc | | A0E83AA191 | truth | 1 | GMO INTERNET PTE LTD | | A0E83AA283 | develop | 1 | Choopa, LLC | | DE2702F4E5 | genre | 1 | Choopa, LLC | | EBF154D8BB | quinoa | 1 | Choopa, LLC | | EBF154D9E2 | quote | 1 | Choopa, LLC | | EBF154DA21 | monk | 1 | Choopa, LLC | | F87AD9C6A1 | caker | 0 | Choopa, LLC | | FD1F34023C | Unnamed | 0 | Choopa, LLC | +------------+----------+-------+----------------------+ ornetradar(a)riseup.net: > 2016-11-23 > ----------------------------------------------------------------------------------------------------------------------- > Up|Ext|JoinTime| IP | CC | ORp | Dirp |Version | ContactInfo | Nickname | eFamlen > ----------------------------------------------------------------------------------------------------------------------- > 1 | 0 |03:34:42| 45.76.128.202 | us | 9001 | 9030 |0.2.8.9 | None | epitome | 1 > 1 | 0 |03:34:46| 45.76.128.202 | us | 9002 | 9031 |0.2.8.9 | None | develop | 1 > 0 | 0 |07:08:45| 45.32.48.248 | jp | 9001 | 9051 |0.2.8.9 | None | caker | 1 > 0 | 0 |07:13:14| 45.32.48.248 | jp | 9001 | 9051 |0.2.8.9 | None | caker | 1 > 0 | 0 |07:22:52| 45.32.48.248 | jp | 9002 | 9052 |0.2.8.9 | None | fufu | 1 > 0 | 0 |15:09:32| 104.238.165.134 | us | 9001 | 9030 |0.2.8.9 | None | pizza | 1 > 0 | 0 |15:09:44| 104.238.165.134 | us | 9002 | 9031 |0.2.8.9 | None | monk | 1 > 1 | 0 |17:20:05| 104.238.165.134 | us | 9001 | 9030 |0.2.8.9 | None | pizza | 1 > 1 | 0 |17:23:04| 104.238.165.134 | us | 9002 | 9031 |0.2.8.9 | None | monk | 1 > 1 | 0 |18:25:05| 107.191.47.191 | fr | 9001 | 9030 |0.2.8.9 | None | genre | 1 > 1 | 0 |18:27:05| 107.191.47.191 | fr | 9002 | 9031 |0.2.8.9 | None | quote | 1 > 1 | 0 |19:15:05| 45.63.20.92 | us | 9001 | 9030 |0.2.8.9 | None | sour | 1 > 1 | 0 |19:17:05| 45.63.20.92 | us | 9002 | 9031 |0.2.8.9 | None | quinoa | 1 > 1 | 0 |12:30:24| 150.95.143.40 | jp | 9001 | 9030 |0.2.8.9 | > 1 | 0 |12:30:29| 150.95.143.40 | jp | 9002 | 9031 |0.2.8.9 | > 1 | 0 |12:33:54| 133.130.122.105 | jp | 9001 | 9030 |0.2.8.9 | > 1 | 0 |12:34:02| 133.130.122.105 | jp | 9002 | 9031 |0.2.8.9 | > 0 | 0 |12:41:09| 150.95.142.186 | jp | 9001 | 9030 |0.2.8.9 | > 0 | 0 |12:41:14| 150.95.142.186 | jp | 9002 | 9031 |0.2.8.9 | > 1 | 0 |13:30:05| 163.44.113.116 | us | 9001 | 9030 |0.2.8.9 | > 1 | 0 |13:35:05| 163.44.113.116 | us | 9002 | 9031 |0.2.8.9 | > 1 | 0 |14:50:05| 150.95.142.186 | jp | 9001 | 9030 |0.2.8.9 | > 1 | 0 |14:55:05| 150.95.142.186 | jp | 9002 | 9031 |0.2.8.9 |

1 0

Assigning new IP adrees to current relay
by Sec INT 30 Nov '16

30 Nov '16

Hi I have more than one ip address in a server - I want to assign a new ip to a current relay that I am running. The new ip is correctly setup on my ubuntu server so i know thats ok In order to make the relay use the new ip I added Address <New IP Address> to the torrc file and restarted tor - this did seem to work and tor detectedthe new address and started to use it but then I got a number of warnings like 'Remote server sent bogus reason code' The relay does seem to be working but with these errors im not sure - is the method above how you should assign a particular IP address to a Tor relay? Thanks for any advice Snap

3 9

re
by dark side 29 Nov '16

29 Nov '16

re

1 0

(no subject)
by dark side 29 Nov '16

29 Nov '16

i need some relays bridges to use

3 2

i need some bridges
by dark side 29 Nov '16

29 Nov '16

1 0

Blocking PSN
by SuperSluether 29 Nov '16

29 Nov '16

I keep getting Account Takeover Attempt abuses on my Tor exit, and I'm not sure how to handle them: It is most likely the attack traffic is directed at one of the following endpoints: account.sonyentertainmentnetwork.com auth.np.ac.playstation.net auth.api.sonyentertainmentnetwork.com auth.api.np.ac.playstation.net These endpoints on our network are resolved by Geo DNS, so the IP addresses they resolve to will depend on the originating IP address. The destination port will be TCP 443. I used 'dig' and 'ping' to see what IP address the 4 endpoints resolved as, and blocked the resulting addresses, but I'm still getting the abuse. The Whois records show Sony and PSN owning 63.x.x.x, 64.x.x.x, 68.x.x.x, and 108.x.x.x addresses, but the websites above resolve to 23.x.x.x, so either the lists are incomplete or I'm doing something wrong. Any ideas?

2 1

Vodafone Italia blocking traffic from IPs that belong to Tor relays
by fr33d0m4all 27 Nov '16

27 Nov '16

Hi, I just want to share my recent time experience with Vodafone Italia (mobile carrier). Some days ago, for the first time, I was surfing Vodafone.it site from my home network where I run a Tor non-exit relay, and when I surfed "https://ricarica.vodafone.it/" I've got the following error page: Access denied (403) Active policy for this site prohibits access from TOR Network. For further information, do not hesitate to contact us. Contact us: support+vodafone(a)reblaze.com For a reference, please provide the following paragraph: [MyIPAddress]://vodafone-rbzr2313438303139323634335aee0f47488438e0 [1480192643] I wrote to reblaze.com, I've explained that I'm running a non-exit relay and that even if Vodafone is saying that traffic from Tor (they say TOR -__- ) Network, no traffic from Tor network can reach the public network (and so their site) from my own relay. This was my email: Hi, today I've received the attached error when trying to pay on Vodafone Italia site and I want to point out that it is a false positive. The error is "Active policy for this site prohibits access from Tor Network." and I was surfing the web directly from my public IP address X.X.X.X. As you can see on ExoneraTor this IP address also hosts a Tor <<middle>> relay: https://exonerator.torproject.org/?ip=X.X.X.X&timestamp=2016-11-24 If you gave a close look to that Tor Relay, you can see that it is DEFINITELY NOT A TOR EXIT RELAY, so you/Vodafone can't receive any traffic from Tor Network from my relay, since it is only a transit Tor relay: https://atlas.torproject.org/#details/xxxxxxx (Exit policy is reject, so it is not an Exit relay). So, I understand that you want to block sessions coming from Tor network, but you should definitely get a list of Tor exit relays only, not the full list of Tor relays that includes Tor relays that will NEVER send traffic from Tor network to public network. I'd like to understand why you're blocking sessions coming from an IP address that hosts a non-exit relay. And this is their reply: Hi currently this web site policy is to block any IP that is identified as TOR Relay: "Looking up IP address X.X.X.X on or within one day of 2016-11-24. Tor clients could have selected this or these Tor relays to build circuits." we are not checking the "Reject Policy" we will check the issue with the web site administrators Thanks Reblaze Support . I think I won't receive any further info from Vodafone, BTW if they reply, I'll share their answer with you. Have a nice weekend, Fr33d0m4all -- _____________________________________________________________ PGP Key: 0DA8 7293 D561 3AEE A3C0 7F63 101F 316A F30E ECB4 IRC Nick: fr33d0m4all (OFTC & Freenode) _____________________________________________________________

4 3

new (?) : Average packaged cell fullness: 96.772%. TLS write overhead: 96%
by Toralf Förster 27 Nov '16

27 Nov '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 I do wonder about a log message which seems not to appear before : ==> /tmp/notice.log <== Nov 26 20:10:45.000 [notice] Performing bandwidth self-test...done. Nov 26 20:19:44.000 [notice] New control connection opened from 127.0.0.1. Nov 26 20:31:13.000 [notice] Received reload signal (hup). Reloading config and resetting internal state. Nov 26 20:31:13.000 [notice] Read configuration file "/etc/tor/torrc". Nov 26 20:31:13.000 [notice] Tor 0.2.9.5-alpha opening log file. Nov 26 20:36:23.000 [notice] New control connection opened from 127.0.0.1. Nov 27 02:10:32.000 [notice] Heartbeat: Tor's uptime is 5:59 hours, with 41 circuits open. I've sent 406.63 MB and received 127.30 MB. Nov 27 02:10:32.000 [notice] Average packaged cell fullness: 96.772%. TLS write overhead: 96% Nov 27 02:10:32.000 [notice] Circuit handshake stats since last time: 0/0 TAP, 3640/3640 NTor. Nov 27 02:10:32.000 [notice] Since startup, we have initiated 0 v1 connections, 0 v2 connections, 0 v3 connections, and 16 v4 connections; and received 0 v1 connections, 1 v2 connections, 15 v3 connections, and 136434 v4 connections. - -- Toralf PGP: C4EACDDE 0076E94E -----BEGIN PGP SIGNATURE----- iHYEAREIAB4FAlg6otwXHHRvcmFsZi5mb2Vyc3RlckBnbXguZGUACgkQxOrN3gB2 6U617AEAh8aGU0wEv3x3OlAOCLBr1HlvVWMVi3ZThqVAvdUmDEAA/2Ruu29iGmO+ zoLs+JRpCno2YSDBfnDmW/vv5qjsmA14 =M7JX -----END PGP SIGNATURE-----

2 2