The Tor Project issueshttps://gitlab.torproject.org/groups/tpo/-/issues2020-06-27T14:10:43Zhttps://gitlab.torproject.org/tpo/core/tor/-/issues/4030.1.2.x warns about non-named servers out of the blue2020-06-27T14:10:43ZRoger Dingledine0.1.2.x warns about non-named servers out of the blueMar 11 18:19:50.085 [warn] You specified a server "BlueStar88b" by name, but thi
s name is not registered, so it could be used by any server, not just the one yo
u meant. To make sure you get the same server in the future, refer to it by...Mar 11 18:19:50.085 [warn] You specified a server "BlueStar88b" by name, but thi
s name is not registered, so it could be used by any server, not just the one yo
u meant. To make sure you get the same server in the future, refer to it by key,
as "$F5B9ABFAB2C44E790AAFC5344B9F00FBDF6DC36E".
Problem is, I didn't ever mention it by name. I only have info level logs, but
they don't help at all. I was probably browsing at the time.
I guess something still refers to something by nickname, internally. I'll try
to collect more info as time goes by.
[Automatically added by flyspray2trac: Operating System: All]https://gitlab.torproject.org/tpo/core/tor/-/issues/5530.2.0.11-alpha fails to compile in osx 10.32020-06-27T14:10:30ZAndrew Lewman0.2.0.11-alpha fails to compile in osx 10.3cc -DHAVE_CONFIG_H -I. -I../.. -I../common -g -O2 -Wall -g -O2 -MT log.o -MD -MP -MF .deps/log.Tpo -c -o log.o log.c
mv -f .deps/log.Tpo .deps/log.Po
gcc -DHAVE_CONFIG_H -I. -I../.. -I../common -g -O2 -Wall -g -O2 -MT util.o ...cc -DHAVE_CONFIG_H -I. -I../.. -I../common -g -O2 -Wall -g -O2 -MT log.o -MD -MP -MF .deps/log.Tpo -c -o log.o log.c
mv -f .deps/log.Tpo .deps/log.Po
gcc -DHAVE_CONFIG_H -I. -I../.. -I../common -g -O2 -Wall -g -O2 -MT util.o -MD -MP -MF .deps/util.Tpo -c -o util.o util.c
mv -f .deps/util.Tpo .deps/util.Po
gcc -DHAVE_CONFIG_H -I. -I../.. -I../common -g -O2 -Wall -g -O2 -MT compat.o -MD -MP -MF .deps/compat.Tpo -c -o compat.o compat.c
compat.c:670: error: conflicting types for `rlim_t'
/usr/include/sys/types.h:103: error: previous declaration of `rlim_t'
make[4]: *** [compat.o] Error 1
make[3]: *** [all-recursive] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all] Error 2
make: *** [dist-osx] Error 2
[Automatically added by flyspray2trac: Operating System: OSX 10.3 Panther]0.2.0.10-alphahttps://gitlab.torproject.org/tpo/core/tor/-/issues/5990.2.0.18-alpha can't create a server behind NAT automatically2020-06-27T14:10:26ZAndrew Lewman0.2.0.18-alpha can't create a server behind NAT automaticallyIt appears 0.2.0.18-alpha can't detect my external IP address while behind NAT. Exact same torrc works in 0.2.0.16-alpha.
Feb 04 22:05:17.479 [Info] resolve_my_address(): Guessed local hostname 'mini.local' resolves to a private IP add...It appears 0.2.0.18-alpha can't detect my external IP address while behind NAT. Exact same torrc works in 0.2.0.16-alpha.
Feb 04 22:05:17.479 [Info] resolve_my_address(): Guessed local hostname 'mini.local' resolves to a private IP address (172.16.31.3). Trying something else.
Feb 04 22:05:17.483 [Info] get_interface_address6(): connect() failed: Invalid argument
Feb 04 22:05:17.486 [Info] resolve_my_address(): Could not get local interface IP address. Too bad.
Feb 04 22:05:17.490 [Info] resolve_my_address(): Address 'mini.local' resolves to private IP address '172.16.31.3'. Tor servers that use the default DirServers must have public IP addresses.
Feb 04 22:05:17.494 [Info] router_pick_published_address(): Could not determine our address locally. Checking if directory headers provide any hints.
Feb 04 22:05:17.500 [Info] router_pick_published_address(): No hints from directory headers either. Will try again later.
Feb 04 22:05:29.379 [Notice] Opening OR listener on 0.0.0.0:8443
Feb 04 22:05:29.383 [Notice] Opening Directory listener on 0.0.0.0:8080
I configured everything via Vidalia only. I know I can put in the external IP, but as the external IP is on DHCP, it changes every few days.
[Automatically added by flyspray2trac: Operating System: OSX 10.4 Tiger]0.2.0.x-rchttps://gitlab.torproject.org/tpo/core/tor/-/issues/9160.2.0.33 doesn't compile on FC8 64-bit2020-06-27T14:10:02ZRoger Dingledine0.2.0.33 doesn't compile on FC8 64-bitReported by John Thompson:
It won't compile for me here (Fedora8 64bit). tor-0.2.32 compiled fine,
however, and 0.2.0.33 built fine on my NetBSD box. See attached log.
In file included from buffers.c:17:
or.h: In function 'TO_OR_CONN'...Reported by John Thompson:
It won't compile for me here (Fedora8 64bit). tor-0.2.32 compiled fine,
however, and 0.2.0.33 built fine on my NetBSD box. See attached log.
In file included from buffers.c:17:
or.h: In function 'TO_OR_CONN':
or.h:1102: warning: implicit declaration of function 'log'
or.h:1102: warning: incompatible implicit declaration of built-in function 'log'
or.h:1102: error: 'LOG_ERR' undeclared (first use in this function)
or.h:1102: error: (Each undeclared identifier is reported only once
or.h:1102: error: for each function it appears in.)
or.h:1102: error: 'LD_BUG' undeclared (first use in this function)
or.h:1102: error: too many arguments to function 'log'
or.h: In function 'TO_DIR_CONN':
or.h:1107: warning: incompatible implicit declaration of built-in function 'log'
or.h:1107: error: 'LOG_ERR' undeclared (first use in this function)
or.h:1107: error: 'LD_BUG' undeclared (first use in this function)
or.h:1107: error: too many arguments to function 'log'
or.h: In function 'TO_EDGE_CONN':
or.h:1112: warning: incompatible implicit declaration of built-in function 'log'
or.h:1112: error: 'LOG_ERR' undeclared (first use in this function)
or.h:1112: error: 'LD_BUG' undeclared (first use in this function)
or.h:1112: error: too many arguments to function 'log'
or.h: In function 'TO_CONTROL_CONN':
or.h:1117: warning: incompatible implicit declaration of built-in function 'log'
or.h:1117: error: 'LOG_ERR' undeclared (first use in this function)
or.h:1117: error: 'LD_BUG' undeclared (first use in this function)
or.h:1117: error: too many arguments to function 'log'
or.h: In function 'TO_OR_CIRCUIT':
or.h:1945: warning: incompatible implicit declaration of built-in function 'log'
or.h:1945: error: 'LOG_ERR' undeclared (first use in this function)
or.h:1945: error: 'LD_BUG' undeclared (first use in this function)
or.h:1945: error: too many arguments to function 'log'
or.h: In function 'TO_ORIGIN_CIRCUIT':
or.h:1950: warning: incompatible implicit declaration of built-in function 'log'
or.h:1950: error: 'LOG_ERR' undeclared (first use in this function)
or.h:1950: error: 'LD_BUG' undeclared (first use in this function)
or.h:1950: error: too many arguments to function 'log'
buffers.c: In function 'chunk_new_with_alloc_size':
buffers.c:174: warning: incompatible implicit declaration of built-in function '
log'
buffers.c:174: error: 'LOG_ERR' undeclared (first use in this function)
buffers.c:174: error: 'LD_BUG' undeclared (first use in this function)
buffers.c:174: error: too many arguments to function 'log'
buffers.c: In function 'chunk_grow':
buffers.c:226: warning: incompatible implicit declaration of built-in function '
log'
buffers.c:226: error: 'LOG_ERR' undeclared (first use in this function)
buffers.c:226: error: 'LD_BUG' undeclared (first use in this function)
buffers.c:226: error: too many arguments to function 'log'
buffers.c: In function 'buf_shrink_freelists':
buffers.c:271: warning: implicit declaration of function 'log_info'
buffers.c:271: error: 'LD_MM' undeclared (first use in this function)
buffers.c:275: warning: incompatible implicit declaration of built-in function '
log'
buffers.c:275: error: 'LOG_ERR' undeclared (first use in this function)
buffers.c:275: error: 'LD_BUG' undeclared (first use in this function)
buffers.c:275: error: too many arguments to function 'log'
buffers.c:288: warning: incompatible implicit declaration of built-in function '
log'
buffers.c:288: error: too many arguments to function 'log'
buffers.c: In function 'buf_dump_freelist_sizes':
buffers.c:306: warning: incompatible implicit declaration of built-in function '
log'
buffers.c:306: error: 'LD_MM' undeclared (first use in this function)
buffers.c:306: error: too many arguments to function 'log'
buffers.c:317: error: too many arguments to function 'log'
buffers.c:320: error: too many arguments to function 'log'
buffers.c: In function 'buf_pullup':
buffers.c:373: warning: incompatible implicit declaration of built-in function '
log'
buffers.c:373: error: 'LOG_ERR' undeclared (first use in this function)
buffers.c:373: error: 'LD_BUG' undeclared (first use in this function)
buffers.c:373: error: too many arguments to function 'log'
buffers.c:381: warning: incompatible implicit declaration of built-in function '
log'
buffers.c:381: error: too many arguments to function 'log'
buffers.c:393: warning: incompatible implicit declaration of built-in function '
log'
buffers.c:393: error: too many arguments to function 'log'
buffers.c:406: warning: incompatible implicit declaration of built-in function '
log'
buffers.c:406: error: too many arguments to function 'log'
buffers.c:411: warning: incompatible implicit declaration of built-in function '
log'
buffers.c:411: error: too many arguments to function 'log'
buffers.c: In function 'buf_remove_from_front':
buffers.c:431: warning: incompatible implicit declaration of built-in function '
log'
buffers.c:431: error: 'LOG_ERR' undeclared (first use in this function)
buffers.c:431: error: 'LD_BUG' undeclared (first use in this function)
buffers.c:431: error: too many arguments to function 'log'
buffers.c:433: warning: incompatible implicit declaration of built-in function '
log'
buffers.c:433: error: too many arguments to function 'log'
...
[Automatically added by flyspray2trac: Operating System: Fedora Core Linux]0.2.1.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/tor/-/issues/5430.2.0.9-alpha servers don't update enough dir info2022-10-12T22:01:51ZRoger Dingledine0.2.0.9-alpha servers don't update enough dir infoNov 03 22:38:08.163 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 0/1170 usable descriptors.
Nov 03 22:38:08.299 [notice] I learned some more directory information, but not
enough t...Nov 03 22:38:08.163 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 0/1170 usable descriptors.
Nov 03 22:38:08.299 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 7/1170 usable descriptors.
Nov 03 22:38:08.357 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 56/1170 usable descriptors.
Nov 03 22:38:08.403 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 102/1170 usable descriptors.
Nov 03 22:38:08.445 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 152/1170 usable descriptors.
Nov 03 22:38:08.494 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 201/1170 usable descriptors.
Nov 03 22:38:08.534 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 254/1170 usable descriptors.
Nov 03 22:38:08.589 [notice] We now have enough directory information to build c
ircuits.
Nov 03 22:38:14.721 [notice] Tor has successfully opened a circuit. Looks like c
lient functionality is working.
So far so good.
Nov 05 17:01:51.001 [notice] Our directory information is no longer up-to-date e
nough to build circuits.
Nov 05 17:05:54.709 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 301/1230 usable descriptors.
Nov 05 17:05:54.793 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 301/1230 usable descriptors.
Nov 05 17:05:54.833 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 301/1230 usable descriptors.
Nov 05 17:05:55.141 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 301/1230 usable descriptors.
Nov 05 17:06:55.449 [notice] We now have enough directory information to build c
ircuits.
Nov 05 17:15:03.960 [notice] Our directory information is no longer up-to-date e
nough to build circuits.
Nov 05 17:21:09.975 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 293/1197 usable descriptors.
Nov 05 17:21:10.005 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 293/1197 usable descriptors.
Nov 05 17:21:10.030 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 293/1197 usable descriptors.
Nov 05 17:21:10.372 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 293/1197 usable descriptors.
Nov 05 17:36:25.179 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 281/1197 usable descriptors.
Nov 05 17:36:25.206 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 281/1197 usable descriptors.
Nov 05 17:36:25.230 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 281/1197 usable descriptors.
Nov 05 17:36:25.675 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 281/1197 usable descriptors.
Nov 05 17:51:40.348 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 265/1197 usable descriptors.
Nov 05 17:51:40.389 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 265/1197 usable descriptors.
Nov 05 17:51:40.413 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 265/1197 usable descriptors.
Nov 05 17:51:40.755 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 265/1197 usable descriptors.
Nov 05 18:06:54.579 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 255/1198 usable descriptors.
Nov 05 18:06:54.622 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 255/1198 usable descriptors.
Nov 05 18:06:54.768 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 255/1198 usable descriptors.
Nov 05 18:06:54.981 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 255/1198 usable descriptors.
Nov 05 18:14:01.845 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 226/1153 usable descriptors.
Nov 05 18:14:01.862 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 227/1153 usable descriptors.
Nov 05 18:14:01.877 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 229/1153 usable descriptors.
Nov 05 18:22:09.761 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 223/1154 usable descriptors.
Nov 05 18:22:09.795 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 223/1154 usable descriptors.
Nov 05 18:22:09.822 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 223/1154 usable descriptors.
Nov 05 18:22:10.294 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 223/1154 usable descriptors.
Nov 05 18:37:25.011 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 196/1155 usable descriptors.
Nov 05 18:37:25.055 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 196/1155 usable descriptors.
Nov 05 18:37:25.084 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 196/1155 usable descriptors.
Nov 05 18:37:25.592 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 196/1155 usable descriptors.
Nov 05 18:52:40.170 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 187/1155 usable descriptors.
Nov 05 18:52:40.196 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 187/1155 usable descriptors.
Nov 05 18:52:40.217 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 187/1155 usable descriptors.
Nov 05 18:52:40.696 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 187/1155 usable descriptors.
Nov 05 19:07:57.288 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 173/1156 usable descriptors.
Nov 05 19:07:57.316 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 173/1156 usable descriptors.
Nov 05 19:07:57.339 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 173/1156 usable descriptors.
Nov 05 19:07:57.775 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 173/1156 usable descriptors.
Nov 05 19:19:05.298 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 169/1169 usable descriptors.
Nov 05 19:19:05.315 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 170/1169 usable descriptors.
Nov 05 19:19:05.332 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 171/1169 usable descriptors.
Nov 05 19:19:05.347 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 171/1169 usable descriptors.
Nov 05 19:23:12.044 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 168/1169 usable descriptors.
Nov 05 19:23:12.076 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 168/1169 usable descriptors.
Nov 05 19:23:12.096 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 168/1169 usable descriptors.
Nov 05 19:23:12.437 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 168/1169 usable descriptors.
Nov 05 19:38:24.736 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 155/1170 usable descriptors.
...
Nov 05 22:10:57.386 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 55/1160 usable descriptors.
Nov 05 22:15:59.274 [warn] I have no descriptor for the router named "moria1" in
my declared family; I'll use the nickname as is, but this may confuse clients.
Nov 05 22:15:59.274 [warn] I have no descriptor for the router named "moria2" in
my declared family; I'll use the nickname as is, but this may confuse clients.
Nov 05 22:15:59.278 [notice] Application request when we're believed to be offli
ne. Optimistically trying directory fetches again.
Nov 05 22:25:09.857 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 55/1172 usable descriptors.
Nov 05 22:25:09.875 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 57/1172 usable descriptors.
Nov 05 22:25:10.060 [notice] I learned some more directory information, but not
enough to build a circuit: We have only 58/1172 usable descriptors.
it's slowly gone up to 95/1300 usable descriptors.
Something is clearly wrong here. :)
[Automatically added by flyspray2trac: Operating System: All]0.2.0.10-alphahttps://gitlab.torproject.org/tpo/core/tor/-/issues/6310.2.0.x svn fails two unit tests2020-06-27T14:10:23ZRoger Dingledine0.2.0.x svn fails two unit testsTry running src/or/test
File test.c: line 2280 (test_dir_format): assertion failed: (router_dump_router_to_string(buf, 2048, r1, pk2)>0)
(we make a test descriptor without any policy lines in it)
File test.c: line 3000 (test_policies):...Try running src/or/test
File test.c: line 2280 (test_dir_format): assertion failed: (router_dump_router_to_string(buf, 2048, r1, pk2)>0)
(we make a test descriptor without any policy lines in it)
File test.c: line 3000 (test_policies): assertion failed: (ADDR_POLICY_REJECTED == compare_addr_to_addr_policy(0x01020304u, 2, NULL))
[Automatically added by flyspray2trac: Operating System: All]0.2.0.22-rchttps://gitlab.torproject.org/tpo/core/tor/-/issues/6160.2.1.0-alpha-dev does not compile on Dapper amd642020-06-27T14:10:24ZKarsten Loesing0.2.1.0-alpha-dev does not compile on Dapper amd64Compiling 0.2.1.0-alpha-dev (r13786) exits with the following error:
tortls.c: In function ‘tor_tls_new’:
tortls.c:738: error: ‘TLS1_TXT_ECDHE_ECDSA_WITH_AES_256_CBC_SHA’ undeclared (first use in this function)
This happens only on Dap...Compiling 0.2.1.0-alpha-dev (r13786) exits with the following error:
tortls.c: In function ‘tor_tls_new’:
tortls.c:738: error: ‘TLS1_TXT_ECDHE_ECDSA_WITH_AES_256_CBC_SHA’ undeclared (first use in this function)
This happens only on Dapper amd64 while compiling on Dapper x86 and Gutsy x86 works fine.
On both machines, openssl version and ciphers are as follows:
/usr/local/ssl/bin/openssl version
OpenSSL 0.9.8g 19 Oct 2007
/usr/local/ssl/bin/openssl ciphers (manually inserted line breaks)
DHE-RSA-AES256-SHA:DHE-DSS-AES256-SHA:AES256-SHA:EDH-RSA-DES-CBC3-SHA:
EDH-DSS-DES-CBC3-SHA:DES-CBC3-SHA:DES-CBC3-MD5:DHE-RSA-AES128-SHA:
DHE-DSS-AES128-SHA:AES128-SHA:IDEA-CBC-SHA:IDEA-CBC-MD5:RC2-CBC-MD5:
RC4-SHA:RC4-MD5:RC4-MD5:EDH-RSA-DES-CBC-SHA:EDH-DSS-DES-CBC-SHA:
DES-CBC-SHA:DES-CBC-MD5:EXP-EDH-RSA-DES-CBC-SHA:EXP-EDH-DSS-DES-CBC-SHA:
EXP-DES-CBC-SHA:EXP-RC2-CBC-MD5:EXP-RC2-CBC-MD5:EXP-RC4-MD5:EXP-RC4-MD5
The libevent version is in both cases 1.3e.
Configuration is done with:
./configure --with-libevent-dir=/usr/local/lib/ --with-openssl-dir=/usr/local/ssl/lib/
After commenting out the following ciphers from CLIENT_CIPHER_LIST in tortls.c, compilation works again:
TLS1_TXT_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
TLS1_TXT_ECDHE_RSA_WITH_AES_256_CBC_SHA
TLS1_TXT_ECDHE_ECDSA_WITH_RC4_128_SHA
TLS1_TXT_ECDHE_RSA_WITH_RC4_128_SHA
TLS1_TXT_ECDHE_ECDSA_WITH_DES_192_CBC3_SHA
TLS1_TXT_ECDHE_RSA_WITH_DES_192_CBC3_SHA
[Automatically added by flyspray2trac: Operating System: Other Linux]Nick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/tor/-/issues/15690.2.1.20: "ORPort found reachable, but I have no routerinfo yet"2020-06-27T14:09:25ZTrac0.2.1.20: "ORPort found reachable, but I have no routerinfo yet"unsure, simply reporting error as per message log. see attached file, copies of basic and advanced message log.
**Trac**:
**Username**: charliemaxwell89104unsure, simply reporting error as per message log. see attached file, copies of basic and advanced message log.
**Trac**:
**Username**: charliemaxwell89104https://gitlab.torproject.org/tpo/core/tor/-/issues/12520.2.1.23 deb can't do tls renegotiation2020-06-27T14:09:37ZRoger Dingledine0.2.1.23 deb can't do tls renegotiationzzz_> Hello, I am using Debian Sid with Tor 0.2.1.23 and Vidalia 0.2.7. When
I try to connect to the Tor network, Vidalia shows this error: [Warning] TLS
error: unexpected close while renegotiating. Is this is a known problem?
> zzz_: a...zzz_> Hello, I am using Debian Sid with Tor 0.2.1.23 and Vidalia 0.2.7. When
I try to connect to the Tor network, Vidalia shows this error: [Warning] TLS
error: unexpected close while renegotiating. Is this is a known problem?
> zzz_: are you using tor as a client, and it's failing?
zzz_> arma: Yes, I am running as a client only. It has started to give this
error very recently.
zzz_> arma: Actually the Debian changelog might give us a hint:
http://packages.debian.org/changelogs/pool/main/t/tor/tor_0.2.1.23-1/changelog
See also http://archives.seul.org/or/talk/Feb-2010/msg00159.html which is another
person reporting this problem.
[Automatically added by flyspray2trac: Operating System: All]weasel (Peter Palfrader)weasel (Peter Palfrader)https://gitlab.torproject.org/tpo/core/tor/-/issues/43400.2.2 relays crash without geoip files2020-06-27T14:07:32ZNick Mathewson0.2.2 relays crash without geoip filesFound via chutney:
```
#0 0x00078878 in geoip_note_client_seen (action=GEOIP_CLIENT_NETWORKSTATUS, addr=2130706433, now=1319812719) at geoip.c:439
#1 0x00057cd6 in directory_handle_command (conn=0x21a3d0) at directory.c:2703
#2 0x0005...Found via chutney:
```
#0 0x00078878 in geoip_note_client_seen (action=GEOIP_CLIENT_NETWORKSTATUS, addr=2130706433, now=1319812719) at geoip.c:439
#1 0x00057cd6 in directory_handle_command (conn=0x21a3d0) at directory.c:2703
#2 0x000590e7 in connection_dir_process_inbuf (conn=0x21a3d0) at directory.c:2162
#3 0x0002deb4 in connection_process_inbuf (conn=0x21a3d0, package_partial=<value temporarily unavailable, due to optimizations>) at connection.c:3363
#4 0x000328ae in connection_handle_read (conn=0x21a3d0) at connection.c:2524
#5 0x000806bf in conn_read_callback (fd=15, event=2, _conn=0x21a3d0) at main.c:514
warning: .o file "/Users/nickm/src/libevent-1.4/.libs/event.o" more recent than executable timestamp
#6 0x001a8911 in event_base_loop (base=0x806400, flags=0) at event.c:401
#7 0x0007df52 in do_main_loop () at main.c:1566
#8 0x0007f73b in tor_main (argc=0, argv=0x0) at main.c:2228
#9 0x00002426 in start ()
```
For some reason, I haven't seen this in master yet.
What shall we do? The easiest option is to make geoip_note_client_seen() return early if geoip_countries is NULL. But perhaps we should go over the whole file to look for other places where we might be saying "smartlist_len(geoip_countries)" without first making sure geoip_countries is set. And perhaps also we should disallow being an authority without a geoip file.Tor: 0.2.2.x-finalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/50310.2.2.35 doesn't cache microdescriptors2020-06-27T14:06:54ZSebastian Hahn0.2.2.35 doesn't cache microdescriptorsLooks like we broke something in maint so that we don't cache microdescriptors anymore, at least on fluxe3 I see 0-byte files in its datadir. Hrm.Looks like we broke something in maint so that we don't cache microdescriptors anymore, at least on fluxe3 I see 0-byte files in its datadir. Hrm.Tor: 0.2.2.x-finalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/11180.2.2.4 fails to compile on osx x862020-06-27T14:09:47ZAndrew Lewman0.2.2.4 fails to compile on osx x86gcc -DHAVE_CONFIG_H -I. -I../.. -DSHARE_DATADIR="\"/Library/Tor/share\"" -DLOCALSTATEDIR="\"/Library/Tor/var\"" -DBINDIR="\"/Library/Tor\"" -I../../src/common -I/usr/local/include -I../or -O -g -mmacosx-version-min=10.4 -isysroot /Dev...gcc -DHAVE_CONFIG_H -I. -I../.. -DSHARE_DATADIR="\"/Library/Tor/share\"" -DLOCALSTATEDIR="\"/Library/Tor/var\"" -DBINDIR="\"/Library/Tor\"" -I../../src/common -I/usr/local/include -I../or -O -g -mmacosx-version-min=10.4 -isysroot /Developer/SDKs/MacOSX10.4u.sdk -arch i386 -Wall -g -O2 -fno-strict-aliasing -c test.c
test.c:46:18: error: test.h: No such file or directory
test.c: In function ‘test_buffers’:
test.c:181: warning: implicit declaration of function ‘test_fail’
test.c:184: warning: implicit declaration of function ‘test_eq’
test.c:196: warning: implicit declaration of function ‘test_memeq’
test.c:400: warning: label ‘done’ defined but not used
test.c: In function ‘test_onion_handshake’:
test.c:427: warning: implicit declaration of function ‘test_assert’
test.c:445: warning: implicit declaration of function ‘test_memneq’
test.c:447: warning: label ‘done’ defined but not used
test.c: In function ‘test_circuit_timeout’:
test.c:612: warning: label ‘done’ defined but not used
test.c: In function ‘test_policy_summary_helper’:
test.c:637: warning: implicit declaration of function ‘test_streq’
test.c:639: warning: label ‘done’ defined but not used
test.c: In function ‘test_policies’:
test.c:792: warning: label ‘done’ defined but not used
test.c: In function ‘test_rend_fns’:
test.c:998: warning: label ‘done’ defined but not used
test.c: In function ‘test_geoip’:
test.c:1071: warning: label ‘done’ defined but not used
test.c: At top level:
test.c:1076: warning: ‘struct testcase_t’ declared inside parameter list
test.c:1076: warning: its scope is only this definition or declaration, which is probably not what you want
test.c: In function ‘legacy_test_setup’:
test.c:1078: error: dereferencing pointer to incomplete type
test.c: At top level:
test.c:1089: warning: ‘struct testcase_t’ declared inside parameter list
test.c:1096: error: variable ‘legacy_setup’ has initializer but incomplete type
test.c:1097: warning: excess elements in struct initializer
test.c:1097: warning: (near initialization for ‘legacy_setup’)
test.c:1098: warning: excess elements in struct initializer
test.c:1098: warning: (near initialization for ‘legacy_setup’)
test.c:1108: error: array type has incomplete element type
test.c:1116: error: ‘TT_SKIP’ undeclared here (not in a function)
test.c:1119: error: ‘END_OF_TESTCASES’ undeclared here (not in a function)
test.c:1121: error: array type has incomplete element type
test.c:1122: error: array type has incomplete element type
test.c:1123: error: array type has incomplete element type
test.c:1124: error: array type has incomplete element type
test.c:1125: error: array type has incomplete element type
test.c:1127: error: array type has incomplete element type
test.c:1135: error: ‘END_OF_GROUPS’ undeclared here (not in a function)
test.c: In function ‘main’:
test.c:1199: warning: implicit declaration of function ‘tinytest_main’
make[4]: *** [test.o] Error 1
make[3]: *** [all-recursive] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all] Error 2
make: *** [dist-osx] Error 2
[Automatically added by flyspray2trac: Operating System: OSX 10.5 Leopard]https://gitlab.torproject.org/tpo/core/tor/-/issues/58600.2.2.x -> 0.2.3.x upgrade breaks tor relay (failed: Function not implemented)2020-06-27T14:06:22Zcypherpunks0.2.2.x -> 0.2.3.x upgrade breaks tor relay (failed: Function not implemented)hi,
today I tried to upgrade from Tor v0.2.2.35 to v0.2.3.15 using your debian package repo, but since running 0.2.3.15 the relay is no longer working. (very simple config ORPort, DirPort, ExitPolicy)
The node is running Debian Squeeze....hi,
today I tried to upgrade from Tor v0.2.2.35 to v0.2.3.15 using your debian package repo, but since running 0.2.3.15 the relay is no longer working. (very simple config ORPort, DirPort, ExitPolicy)
The node is running Debian Squeeze.
```
[notice] Tor 0.2.3.15-alpha (git-d2fd67f30991cbc4) opening log file.
[notice] Parsing GEOIP file /usr/share/tor/geoip.
[notice] Configured to measure statistics. Look for the *-stats files that will first be written to the data directory in 24 hours from now.
[notice] No AES engine found; using AES_* functions.
[notice] This version of OpenSSL has a slow implementation of counter mode; not using it.
[notice] OpenSSL OpenSSL 0.9.8o 01 Jun 2010 looks like version 0.9.8m or later; I will try SSL_OP to enable renegotiation
[notice] Your Tor server's identity key fingerprint is [scrubbed]
[notice] Reloaded microdescriptor cache. Found 3544 descriptors.
[notice] We now have enough directory information to build circuits.
[notice] Bootstrapped 80%: Connecting to the Tor network.
[warn] accept() failed: Function not implemented. Closing listener.
[notice] Guessed our IP address as [scrubbed] (source: [scrubbed]).
[notice] Opening OR listener on [scrubbed]
[notice] Heartbeat: It seems like we are not in the cached consensus.
[notice] Heartbeat: Tor's uptime is 0:00 hours, with 1 circuits open. I've sent 14 kB and received 168 kB.
[notice] Bootstrapped 85%: Finishing handshake with first hop.
[notice] Bootstrapped 90%: Establishing a Tor circuit.
[notice] Tor has successfully opened a circuit. Looks like client functionality is working.
[notice] Bootstrapped 100%: Done.
[notice] Now checking whether ORPort [scrubbed] and DirPort [scrubbed] are reachable... (this may take up to 20 minutes -- look for log messages indicating success)
[warn] accept() failed: Function not implemented. Closing listener.
[warn] accept() failed: Function not implemented. Closing listener.
[notice] Opening Directory listener on [scrubbed]
[notice] Opening OR listener on [scrubbed]
[warn] accept() failed: Function not implemented. Closing listener.
[warn] accept() failed: Function not implemented. Closing listener.
[notice] Opening Directory listener on [scrubbed]
[notice] Opening OR listener on [scrubbed]
[warn] accept() failed: Function not implemented. Closing listener.
[notice] Opening OR listener on [scrubbed]
[warn] accept() failed: Function not implemented. Closing listener.
[notice] Opening OR listener on [scrubbed]
[warn] accept() failed: Function not implemented. Closing listener.
[notice] Opening OR listener on [scrubbed]
[warn] accept() failed: Function not implemented. Closing listener.
[notice] Opening OR listener on [scrubbed]
[warn] accept() failed: Function not implemented. Closing listener.
[notice] Opening OR listener on [scrubbed]
[warn] accept() failed: Function not implemented. Closing listener.
[warn] accept() failed: Function not implemented. Closing listener.
[notice] Opening Directory listener on [scrubbed]
[notice] Opening OR listener on [scrubbed]
[warn] accept() failed: Function not implemented. Closing listener.
```https://gitlab.torproject.org/tpo/core/tor/-/issues/24500.2.2.x manpage mentions country codes for 0.2.2.x EntryNodes option2020-06-27T14:08:44ZSebastian Hahn0.2.2.x manpage mentions country codes for 0.2.2.x EntryNodes option... which isn't supported until 0.2.3.x.... which isn't supported until 0.2.3.x.Tor: 0.2.2.x-finalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/33890.2.3.1 tarball doesn't contain tor-fw-helper manpage2020-06-27T14:08:10ZSebastian Hahn0.2.3.1 tarball doesn't contain tor-fw-helper manpageStephen Walker reports that building from the 0.2.3.1 tarball fails when the --enable-upnp option is passed during configure. Because we didn't want to build the manpage when it isn't needed, we also didn't include it in the tarball if -...Stephen Walker reports that building from the 0.2.3.1 tarball fails when the --enable-upnp option is passed during configure. Because we didn't want to build the manpage when it isn't needed, we also didn't include it in the tarball if --enable-upnp or --enable-nat-pmp didn't get passed during configure.Tor: 0.2.3.x-finalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/40110.2.3.3 relay won't fetch microdesc consensus on startup if it already has a ...2020-06-27T14:07:44ZRoger Dingledine0.2.3.3 relay won't fetch microdesc consensus on startup if it already has a normal consensusIn networkstatus.c we have:
```
/** A time before which we shouldn't try to replace the current consensus:
* this will be at some point after the next consensus becomes valid, but
* before the current consensus becomes invalid. */
stat...In networkstatus.c we have:
```
/** A time before which we shouldn't try to replace the current consensus:
* this will be at some point after the next consensus becomes valid, but
* before the current consensus becomes invalid. */
static time_t time_to_download_next_consensus = 0;
```
which we use in update_consensus_networkstatus_downloads() to decide whether to break out:
```
if (time_to_download_next_consensus > now)
return; /* Wait until the current consensus is older. */
```
The result is that we don't even try to fetch a microdesc consensus if the ns consensus we have is recent enough.Tor: 0.2.3.x-finalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/45750.2.3.8-alpha fails to bootstrap2020-06-27T14:07:18ZTrac0.2.3.8-alpha fails to bootstrapSo, after removing ~/.tor I became unable to bootstrap the latest Tor unstable.
The stable version works fine (with the exact same torrc) so I am using it right now.
I compiled both from source.
ORport = 2077
DirPort = 2078
Server OS...So, after removing ~/.tor I became unable to bootstrap the latest Tor unstable.
The stable version works fine (with the exact same torrc) so I am using it right now.
I compiled both from source.
ORport = 2077
DirPort = 2078
Server OS: CentOS 5 x86_64
That's all the info I can think of to give right now. Just ask if there's something else you need to know.
```
Nov 24 23:37:02.000 [notice] Tor 0.2.3.8-alpha (git-68475fc5c5a806eb) opening new log file.
Nov 24 23:37:02.000 [notice] Parsing GEOIP file /usr/share/tor/geoip.
Nov 24 23:37:02.000 [notice] Configured to measure statistics. Look for the *-stats files that will first be written to the data directory in 24 hours from now.
Nov 24 23:37:02.000 [notice] OpenSSL OpenSSL 1.0.0e 6 Sep 2011 looks like version 0.9.8m or later; I will try SSL_OP to enable renegotiation
Nov 24 23:37:02.000 [notice] Your Tor server's identity key fingerprint is 'killertor 08701863085C27749F4443D05C1755AB6953642A'
Nov 24 23:37:02.000 [notice] Reloaded microdescriptor cache. Found 0 descriptors.
Nov 24 23:37:02.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
Nov 24 23:37:04.000 [notice] Bootstrapped 5%: Connecting to directory server.
Nov 24 23:37:04.000 [notice] Heartbeat: It seems like we are not in the cached consensus.
Nov 24 23:37:04.000 [notice] Heartbeat: Tor's uptime is 0:00 hours, with 2 circuits open. I've sent 0 kB and received 0 kB.
Nov 24 23:37:04.000 [notice] Bootstrapped 10%: Finishing handshake with directory server.
Nov 24 23:37:08.000 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Nov 24 23:37:19.000 [notice] Bootstrapped 15%: Establishing an encrypted directory connection.
Nov 24 23:37:20.000 [notice] Bootstrapped 20%: Asking for networkstatus consensus.
Nov 24 23:37:21.000 [notice] Bootstrapped 25%: Loading networkstatus consensus.
Nov 24 23:37:26.000 [warn] update_router_descriptor_cache_downloads_v2(): Bug: Called update_router_descriptor_cache_downloads_v2() on a non-dir-mirror?
Nov 24 23:37:34.000 [notice] We're missing a certificate from authority with signing key 3509BA5A624403A905C74DA5C8A0CEC9E0D3AF86: launching request.
Nov 24 23:37:34.000 [notice] We're missing a certificate from authority with signing key 8936BDA972B6C9A5C9DEC71A18134749F903A6AA: launching request.
Nov 24 23:37:34.000 [notice] We're missing a certificate from authority with signing key EEB9299D295C1C815E289FBF2F2BBEA5F52FDD19: launching request.
Nov 24 23:37:34.000 [notice] We're missing a certificate from authority with signing key 2B83C6BE3EC75E91270444DAE41F80A9EFD38912: launching request.
Nov 24 23:37:34.000 [notice] We're missing a certificate from authority with signing key 845CF1D0B370CA443A8579D18E7987E7E532F639: launching request.
Nov 24 23:37:35.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
Nov 24 23:37:45.000 [notice] Catching signal TERM, exiting cleanly.
Nov 24 23:38:49.000 [notice] Tor 0.2.3.8-alpha (git-68475fc5c5a806eb) opening log file.
Nov 24 23:38:49.000 [notice] Parsing GEOIP file /usr/share/tor/geoip.
Nov 24 23:38:49.000 [notice] Configured to measure statistics. Look for the *-stats files that will first be written to the data directory in 24 hours from now.
Nov 24 23:38:50.000 [notice] OpenSSL OpenSSL 1.0.0e 6 Sep 2011 looks like version 0.9.8m or later; I will try SSL_OP to enable renegotiation
Nov 24 23:38:50.000 [notice] Your Tor server's identity key fingerprint is 'killertor 2B207CDAAAB9EC7F0F7D343A419D8D83DDB8649E'
Nov 24 23:38:50.000 [notice] Reloaded microdescriptor cache. Found 0 descriptors.
Nov 24 23:38:50.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
Nov 24 23:38:52.000 [notice] Bootstrapped 5%: Connecting to directory server.
Nov 24 23:38:52.000 [notice] Heartbeat: It seems like we are not in the cached consensus.
Nov 24 23:38:52.000 [notice] Heartbeat: Tor's uptime is 0:00 hours, with 1 circuits open. I've sent 0 kB and received 0 kB.
Nov 24 23:38:52.000 [notice] Bootstrapped 10%: Finishing handshake with directory server.
Nov 24 23:39:24.000 [warn] update_router_descriptor_cache_downloads_v2(): Bug: Called update_router_descriptor_cache_downloads_v2() on a non-dir-mirror?
Nov 24 23:39:24.000 [notice] Bootstrapped 15%: Establishing an encrypted directory connection.
Nov 24 23:39:35.000 [warn] update_router_descriptor_cache_downloads_v2(): Bug: Called update_router_descriptor_cache_downloads_v2() on a non-dir-mirror?
Nov 24 23:40:19.000 [warn] update_router_descriptor_cache_downloads_v2(): Bug: Called update_router_descriptor_cache_downloads_v2() on a non-dir-mirror?
Nov 24 23:42:20.000 [warn] update_router_descriptor_cache_downloads_v2(): Bug: Called update_router_descriptor_cache_downloads_v2() on a non-dir-mirror?
Nov 24 23:42:42.000 [warn] update_router_descriptor_cache_downloads_v2(): Bug: Called update_router_descriptor_cache_downloads_v2() on a non-dir-mirror?
Nov 24 23:45:16.000 [warn] update_router_descriptor_cache_downloads_v2(): Bug: Called update_router_descriptor_cache_downloads_v2() on a non-dir-mirror?
Nov 24 23:46:44.000 [warn] update_router_descriptor_cache_downloads_v2(): Bug: Called update_router_descriptor_cache_downloads_v2() on a non-dir-mirror?
Nov 24 23:46:55.000 [warn] update_router_descriptor_cache_downloads_v2(): Bug: Called update_router_descriptor_cache_downloads_v2() on a non-dir-mirror?
Nov 24 23:47:50.000 [warn] update_router_descriptor_cache_downloads_v2(): Bug: Called update_router_descriptor_cache_downloads_v2() on a non-dir-mirror?
Nov 24 23:50:24.000 [warn] update_router_descriptor_cache_downloads_v2(): Bug: Called update_router_descriptor_cache_downloads_v2() on a non-dir-mirror?
Nov 24 23:51:08.000 [warn] update_router_descriptor_cache_downloads_v2(): Bug: Called update_router_descriptor_cache_downloads_v2() on a non-dir-mirror?
Nov 24 23:51:41.000 [warn] update_router_descriptor_cache_downloads_v2(): Bug: Called update_router_descriptor_cache_downloads_v2() on a non-dir-mirror?
Nov 24 23:52:47.000 [warn] update_router_descriptor_cache_downloads_v2(): Bug: Called update_router_descriptor_cache_downloads_v2() on a non-dir-mirror?
Nov 24 23:55:10.000 [warn] update_router_descriptor_cache_downloads_v2(): Bug: Called update_router_descriptor_cache_downloads_v2() on a non-dir-mirror?
Nov 24 23:56:27.000 [warn] update_router_descriptor_cache_downloads_v2(): Bug: Called update_router_descriptor_cache_downloads_v2() on a non-dir-mirror?
Nov 24 23:56:38.000 [warn] update_router_descriptor_cache_downloads_v2(): Bug: Called update_router_descriptor_cache_downloads_v2() on a non-dir-mirror?
Nov 24 23:57:22.000 [warn] update_router_descriptor_cache_downloads_v2(): Bug: Called update_router_descriptor_cache_downloads_v2() on a non-dir-mirror?
Nov 24 23:59:01.000 [warn] update_router_descriptor_cache_downloads_v2(): Bug: Called update_router_descriptor_cache_downloads_v2() on a non-dir-mirror?
Nov 24 23:59:34.000 [warn] update_router_descriptor_cache_downloads_v2(): Bug: Called update_router_descriptor_cache_downloads_v2() on a non-dir-mirror?
Nov 25 00:01:46.000 [warn] update_router_descriptor_cache_downloads_v2(): Bug: Called update_router_descriptor_cache_downloads_v2() on a non-dir-mirror?
Nov 25 00:03:36.000 [warn] update_router_descriptor_cache_downloads_v2(): Bug: Called update_router_descriptor_cache_downloads_v2() on a non-dir-mirror?
Nov 25 00:03:58.000 [warn] update_router_descriptor_cache_downloads_v2(): Bug: Called update_router_descriptor_cache_downloads_v2() on a non-dir-mirror?
Nov 25 00:05:04.000 [warn] update_router_descriptor_cache_downloads_v2(): Bug: Called update_router_descriptor_cache_downloads_v2() on a non-dir-mirror?
Nov 25 00:05:40.000 [notice] Catching signal TERM, exiting cleanly.
```
**Trac**:
**Username**: chk1nTor: 0.2.3.x-finalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/139500.2.6.1-alpha Fails to Compile from Source on FreeBSD 9.3-STABLE2020-06-27T14:02:06ZTrac0.2.6.1-alpha Fails to Compile from Source on FreeBSD 9.3-STABLE
CC src/or/src_or_libtor_testing_a-routerlist.o
CC src/or/src_or_libtor_testing_a-routerparse.o
CC src/or/src_or_libtor_testing_a-routerset.o
CC src/or/src_or_libtor_testing_a-statefile.o
CC src/or...
CC src/or/src_or_libtor_testing_a-routerlist.o
CC src/or/src_or_libtor_testing_a-routerparse.o
CC src/or/src_or_libtor_testing_a-routerset.o
CC src/or/src_or_libtor_testing_a-statefile.o
CC src/or/src_or_libtor_testing_a-status.o
CC src/or/src_or_libtor_testing_a-onion_ntor.o
CC src/or/src_or_libtor_testing_a-config_codedigest.o
AR src/or/libtor-testing.a
CC src/or/tor_main.o
CCLD src/or/tor
CC src/tools/tor-resolve.o
CCLD src/tools/tor-resolve
CC src/tools/tor-gencert.o
CCLD src/tools/tor-gencert
src/common/libor-crypto.a(aes.o): In function `aes_new_cipher':
aes.c:(.text+0x3a): undefined reference to `EVP_aes_128_ctr'
*** [src/tools/tor-gencert] Error code 1
The Tor 2.5.10 STABLE source tar-ball had the same problem.
**Trac**:
**Username**: onionworm77https://gitlab.torproject.org/tpo/core/tor/-/issues/171840.2.7.3-rc: no IPv6 Tor connections2020-06-27T14:00:33Ztoralf0.2.7.3-rc: no IPv6 Tor connections0.2.6.10 works fine, with that I have > 200 IPv6 inbound connections from relays. With 0.2.7.3-rc I do just have 1 IPv6 from tor.noreply.org
From my mails :
```
My exit relay F1BE15429B3CE696D6807F4D4A58B1BFEC45C822 has an overall traf...0.2.6.10 works fine, with that I have > 200 IPv6 inbound connections from relays. With 0.2.7.3-rc I do just have 1 IPv6 from tor.noreply.org
From my mails :
```
My exit relay F1BE15429B3CE696D6807F4D4A58B1BFEC45C822 has an overall traffic of about 150 GB/day.
Few weeks ago I added IPv6 to the exit policy too. Since that time I observed the mentioned IPv6 traffic.
With the new Tor version I realized the decrease.
I verified that switching back to 0.2.6.10 gives about 200 IPv6 connections to other relays, whereas w/ 0.2.7.3-rc I do just have 1 IPv6 connection to tor.noreply.org.
```Tor: 0.2.8.x-finalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/177540.2.7.5 cannot work inside lxc container2020-07-27T18:18:59ZTrac0.2.7.5 cannot work inside lxc containerI am running tor inside a lxc container running ubuntu/vivid and Tor don't run since system tor status show it running
Tor version 0.2.7.5 (git-6184c873e90d93b2)
before upgrading to this version, everything work well inside the contai...I am running tor inside a lxc container running ubuntu/vivid and Tor don't run since system tor status show it running
Tor version 0.2.7.5 (git-6184c873e90d93b2)
before upgrading to this version, everything work well inside the container. Outside of the container, in a host running ubuntu/vivid, everything work.
output of journalctl :
```
déc. 04 22:50:29 torouter systemd[1]: Starting Anonymizing overlay network for TCP (multi-instance-master)..
déc. 04 22:50:29 torouter systemd[1]: Started Anonymizing overlay network for TCP (multi-instance-master).
déc. 04 22:54:09 torouter systemd[1]: tor.service: Failed to kill control group: Invalid argument
déc. 04 22:54:09 torouter systemd[1]: tor.service: Failed to kill control group: Invalid argument
déc. 04 22:54:09 torouter systemd[1]: tor.service: Failed to kill control group: Invalid argument
déc. 04 22:54:09 torouter systemd[1]: tor.service: Failed to kill control group: Invalid argument
déc. 04 22:54:09 torouter systemd[1]: Stopped Anonymizing overlay network for TCP (multi-instance-master).
déc. 04 22:59:32 torouter systemd[1]: Starting Anonymizing overlay network for TCP (multi-instance-master)..
déc. 04 22:59:32 torouter systemd[1]: Started Anonymizing overlay network for TCP (multi-instance-master).
```
output of systemctl status tor@default.service
```
● tor@default.service - Anonymizing overlay network for TCP
Loaded: loaded (/lib/systemd/system/tor@default.service; static; vendor preset: enabled)
Active: failed (Result: start-limit) since ven. 2015-12-04 23:51:04 CET; 36s ago
Process: 4478 ExecStart=/usr/bin/tor --defaults-torrc /usr/share/tor/tor-service-defaults-torrc -f /etc/tor/torrc --RunAsDaemon 0 (code=exited, status=231/APPARMOR)
Process: 4464 ExecStartPre=/usr/bin/tor --defaults-torrc /usr/share/tor/tor-service-defaults-torrc -f /etc/tor/torrc --RunAsDaemon 0 --verify-config (code=exited, status=0/SUCCESS)
Process: 4450 ExecStartPre=/usr/bin/install -Z -m 02750 -o debian-tor -g debian-tor -d /var/run/tor (code=exited, status=0/SUCCESS)
Main PID: 4478 (code=exited, status=231/APPARMOR)
déc. 04 23:51:04 torouter systemd[1]: Failed to start Anonymizing overlay network for TCP.
déc. 04 23:51:04 torouter systemd[1]: tor@default.service: Unit entered failed state.
déc. 04 23:51:04 torouter systemd[1]: tor@default.service: Failed with result 'exit-code'.
déc. 04 23:51:04 torouter systemd[1]: tor@default.service: Service hold-off time over, scheduling restart.
déc. 04 23:51:04 torouter systemd[1]: Stopped Anonymizing overlay network for TCP.
déc. 04 23:51:04 torouter systemd[1]: tor@default.service: Start request repeated too quickly.
déc. 04 23:51:04 torouter systemd[1]: Failed to start Anonymizing overlay network for TCP.
déc. 04 23:51:04 torouter systemd[1]: tor@default.service: Unit entered failed state.
déc. 04 23:51:04 torouter systemd[1]: tor@default.service: Failed with result 'start-limit'.
```
in /var/log/tor/log =>
`Interrupt: exiting cleanly`
{{{
find /etc/systemd/ | grep /tor
/etc/systemd/system/multi-user.target.wants/tor.service
}}}
I have try to use the patch in this issue :
https://trac.torproject.org/projects/tor/ticket/17693
Don't work
**Trac**:
**Username**: kibbaTor: unspecified