[warn] Tried to establish rendezvous on non-OR or non-edge circuit.

Hi people .. i yesterday started IPV6 but now i see in log following messages periodically part of my torrc below. I only add ipv6 lines. Any idea ? or its normal ? Thanks Cmar ORPort 37.157.192.208:443 ORPort [2a02:2b88:2:1::3a62:1]:9050 ## If you want to listen on a port other than the one advertised in ## ORPort (e.g. to advertise 443 but bind to 9090), you can do it as ## follows. You'll need to do ipchains or other port forwarding ## yourself to make this work. #ORPort 443 NoListen #ORPort 127.0.0.1:9090 NoAdvertise ## The IP address or full DNS name for incoming connections to your ## relay. Leave commented out and Tor will guess. Address 37.157.192.208 ## If you have multiple network interfaces, you can specify one for ## outgoing traffic to use. OutboundBindAddress 37.157.192.208 info from log: May 19 22:42:03.000 [notice] Average packaged cell fullness: 99.082% May 19 22:42:03.000 [notice] TLS write overhead: 3% May 19 22:42:03.000 [notice] Circuit handshake stats since last time: 118791/118793 TAP, 161141/161141 NTor. May 19 23:13:45.000 [warn] Tried to establish rendezvous on non-OR or non-edge circuit. May 20 03:08:03.000 [warn] Tried to establish rendezvous on non-OR or non-edge circuit. May 20 03:33:54.000 [warn] Tried to establish rendezvous on non-OR or non-edge circuit. May 20 04:42:03.000 [notice] Heartbeat: Tor's uptime is 18:00 hours, with 4375 circuits open. I've sent 211.07 GB and received 203.24 GB.

Any idea ? or its normal ?
I'm not sure, but I also saw this for the first time today after enabling ipv6 on a relay last week. A quick look at the relevant code doesn't shed any immediate light on what would be causing this (the triggering request is to establish a rendezvous point with a hidden service, but I'm not familiar with the semantics of the CIRCUIT_PURPOSE check that's failing). Relevant: https://trac.torproject.org/projects/tor/ticket/15618 Regards, Sharif -- PGP: 6FB7 ED25 BFCF 3E22 72AE 6E8C 47D4 CE7F 6B9F DF57

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 21.05.2015 13:23, Sharif Olorin wrote:
Any idea ? or its normal ?
I'm not sure, but I also saw this for the first time today after enabling ipv6 on a relay last week. A quick look at the relevant code doesn't shed any immediate light on what would be causing this (the triggering request is to establish a rendezvous point with a hidden service, but I'm not familiar with the semantics of the CIRCUIT_PURPOSE check that's failing).
I have been getting these warnings on both of my relays for a long time, whether with or without IPv6. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJVXcckAAoJEJe61A/xrcOQFboQAJFbwudTfJuQKvTQFxCQ7IAJ HWhBCCsMHRHGyRZdywJJXNx5LKx+GYnvjWqNZiYANeGKpCvAsL6oXF60s81smv1U baoXPdyA5z+GwVOTJVbC+URt1UzjMHV18Y5gdWM6w/IbBaiTUBu83KPhGrmE3z8V NFKRb8aqrfqZ+tUx6K2vIONup6/NaByFHMF6d6xJfOCC0xrYTR0a2HnFV0cDP4Ne vNYuTbLAoSkwyfQgJ0mvCLY0y+VDbW4RLgoLzBUchDIJSABghTnvfnH5U+cye8m+ fnFzY5WolIehtBwX9Y1vsJNpY9WGn9P5RO2OVKBn3s+u7IT6kIWcpVyv25MmkVUD 9c7ilxhsgdBjaEF29gAELZbAZiCPDXm2xMopwxZ67vVxBAOqc3PwbB4T4ly2idzZ dL/i9Kw4PgPWN5YIkaR6ksyz67fTwXmg14crSj63xYyZHGUY1h1gGphH/SG7HdSF +MLwJ+HKc2R9Qj0zVn3yCweybwMTgEh+d4MfkD42+dFvsebG5Kpy/vKse/IC/laM BpgPcWM3TBYkls4cq+/GzgX/qe9oeNCt8RB7H0Rq3nLdNvS7SBXZWCB+TWsq8XFr B9brTZWqzfUsqkxJARyDlUmkiygAQUliRq2ZR4I9ayWSaZw1LBKAfvX2XCg1+m9v uHVr3hEUDx5ocfUJPQ5g =QB5r -----END PGP SIGNATURE-----
participants (3)
-
Cmar433
-
Random Tor Node Operator
-
Sharif Olorin