[Fwd: (Probably) a known problem?] - cant run a relay node
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, A few days ago I posted the message below asking for help to resolve a problem that prevents me from running a Tor relay node. I have not received any responses. I would like to continue to run a Tor relay node but am unable to do so until I resolve the problem described below, and I need help in order to do that. Any help would be greatly appreciated. thanks. Alex Donnini Alessandro Donnini wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, I just upgraded to versions 0.1.10 of Vidalia and 0.2.1.7 of Tor Vidalia is able to run Tor as a client without any problems. However, when I try to configure and run it as a relay node Vidalia is not able to run Tor and reports the warnings and error you will find below. Please note that up until I upgraded the software, Tor was running as a relay node. I made no configuration changes either before or after the upgrade. The only two attempts at trying to fix the problems were: 1) Rename the Tor configuration file 2) Re-start the system Nov 30 22:02:52.906 [Error] set_options(): Bug: Acting on config options left us in a broken state. Dying. Nov 30 22:02:52.906 [Warning] eventdns: Didn't find any nameservers. Nov 30 22:02:52.906 [Warning] Could not config nameservers. Nov 30 22:02:52.906 [Error] set_options(): Bug: Acting on config options left us in a broken state. Dying. I would appreciate any help and advice for the resolution of this problem. Thanks. Alex Donnini -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkkzWBwACgkQ3ju7mowpX9XvPgCfcKA9whVSZ3Uyc+XBoMXW+pFz jKkAn3AMffP08tl++uMcSg5HZ5p5rMQA =IS2P -END PGP SIGNATURE- -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkk2mQAACgkQ3ju7mowpX9X3ZQCff5sXGocu3uTapnLSdsG3vtRk Or4AoI6zkpdMyK6w/QY+JLVefBbb7PZl =t486 -END PGP SIGNATURE-
Re: [Fwd: (Probably) a known problem?] - cant run a relay node
On Wed, Dec 03, 2008 at 09:34:40AM -0500, [EMAIL PROTECTED] wrote 2.1K bytes in 74 lines about: : I would like to continue to run a Tor relay node but am unable to do so until I : resolve the problem described below, and I need help in order to do that. : I just upgraded to versions : : 0.1.10 of Vidalia : and : 0.2.1.7 of Tor : : Vidalia is able to run Tor as a client without any problems. : : Nov 30 22:02:52.906 [Error] set_options(): Bug: Acting on config options left us : in a broken state. Dying. : Nov 30 22:02:52.906 [Warning] eventdns: Didn't find any nameservers. : Nov 30 22:02:52.906 [Warning] Could not config nameservers. : Nov 30 22:02:52.906 [Error] set_options(): Bug: Acting on config options left us : in a broken state. Dying. A few things, you probably haven't received a response because no one has a good idea how to fix it. You may have 2 issues, one is that libevent can't find nameservers, and the other is that the config options are broken. As for the dns issues: https://bugs.torproject.org/flyspray/index.php?do=detailsid=813 or https://bugs.torproject.org/flyspray/index.php?do=detailsid=868 Are you running Windows? For the config issues, which may be related to the dns issues, do you have a copy of the torrc that's generated by Vidalia? -- Andrew
Re: [Fwd: (Probably) a known problem?] - cant run a relay node
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thanks for the response. I understand. Below, you will find the copy of the Vidalia generated torrc. The problem is occurring on a system running MS Windows XP SP2. Note that prior to the upgrade from 0.2.0.31 to 0.2.1.7 I had no problems. The problems started occurring as soon as I started Tor again via Vidalia after the upgrade. Also note that I do not have any problems running the Tor client. Thanks torrc from Document and Settings\user name\Application Data\Vidalia == # This file was generated by Tor; if you edit it, comments will not be preserved # The old torrc file was renamed to torrc.orig.1 or similar, and Tor will ignore it # If set, Tor will accept connections from the same machine (localhost only) # on this port, and allow those connections to control the Tor process using # the Tor Control Protocol (described in control-spec.txt). ControlPort 9051 # Where to send logging messages. Format is minSeverity[-maxSeverity] # (stderr|stdout|syslog|file FILENAME). Log notice stdout [EMAIL PROTECTED] wrote: On Wed, Dec 03, 2008 at 09:34:40AM -0500, [EMAIL PROTECTED] wrote 2.1K bytes in 74 lines about: : I would like to continue to run a Tor relay node but am unable to do so until I : resolve the problem described below, and I need help in order to do that. : I just upgraded to versions : : 0.1.10 of Vidalia : and : 0.2.1.7 of Tor : : Vidalia is able to run Tor as a client without any problems. : : Nov 30 22:02:52.906 [Error] set_options(): Bug: Acting on config options left us : in a broken state. Dying. : Nov 30 22:02:52.906 [Warning] eventdns: Didn't find any nameservers. : Nov 30 22:02:52.906 [Warning] Could not config nameservers. : Nov 30 22:02:52.906 [Error] set_options(): Bug: Acting on config options left us : in a broken state. Dying. A few things, you probably haven't received a response because no one has a good idea how to fix it. You may have 2 issues, one is that libevent can't find nameservers, and the other is that the config options are broken. As for the dns issues: https://bugs.torproject.org/flyspray/index.php?do=detailsid=813 or https://bugs.torproject.org/flyspray/index.php?do=detailsid=868 Are you running Windows? For the config issues, which may be related to the dns issues, do you have a copy of the torrc that's generated by Vidalia? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkk2vsYACgkQ3ju7mowpX9VyXwCfXEdV2r6N+q9YE9FcQysb+h+F uEkAoNTgor2oNzLXyY0sND1qeBINyHqn =dp76 -END PGP SIGNATURE-
2 - Re: [Fwd: (Probably) a known problem?] - cant run a relay node
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I replaced the current ttorrc with the one labeled old. Tor still cannot run
as a relay node but the error messages have changed. Here they are:
Dec 03 12:05:09.746 [Notice] Tor v0.2.1.7-alpha (r17216). This is experimental
software. Do not rely on it for strong anonymity. (Running on Windows XP Service
Pack 2 [workstation] {terminal services, single user})
Dec 03 12:05:09.746 [Notice] Initialized libevent version 1.4.7-stable using
method win32. Good.
Dec 03 12:05:09.746 [Notice] Opening Socks listener on 127.0.0.1:9050
Dec 03 12:05:09.746 [Notice] Opening Control listener on 127.0.0.1:9051
Dec 03 12:05:09.746 [Notice] Parsing GEOIP file.
Dec 03 12:15:34.902 [Notice] Tor v0.2.1.7-alpha (r17216). This is experimental
software. Do not rely on it for strong anonymity. (Running on Windows XP Service
Pack 2 [workstation] {terminal services, single user})
Dec 03 12:15:34.902 [Notice] Initialized libevent version 1.4.7-stable using
method win32. Good.
Dec 03 12:15:34.902 [Notice] Opening Socks listener on 127.0.0.1:9050
Dec 03 12:15:34.902 [Notice] Opening Control listener on 127.0.0.1:9051
Dec 03 12:15:34.902 [Notice] Parsing GEOIP file.
Dec 03 12:18:01.808 [Notice] Tor v0.2.1.7-alpha (r17216). This is experimental
software. Do not rely on it for strong anonymity. (Running on Windows XP Service
Pack 2 [workstation] {terminal services, single user})
Dec 03 12:18:01.808 [Notice] Initialized libevent version 1.4.7-stable using
method win32. Good.
Dec 03 12:18:01.808 [Notice] Opening OR listener on 0.0.0.0:443
Dec 03 12:18:01.808 [Notice] Opening Directory listener on 0.0.0.0:9030
Dec 03 12:18:01.808 [Notice] Opening Socks listener on 127.0.0.1:9050
Dec 03 12:18:01.808 [Notice] Opening Control listener on 127.0.0.1:9051
Dec 03 12:18:01.808 [Notice] Parsing GEOIP file.
Dec 03 12:18:03.121 [Warning] eventdns: Didn't find any nameservers.
Dec 03 12:18:03.121 [Warning] Could not config nameservers.
Dec 03 12:18:03.121 [Error] Error initializing dns subsystem; exiting
[EMAIL PROTECTED] wrote:
On Wed, Dec 03, 2008 at 09:34:40AM -0500, [EMAIL PROTECTED] wrote 2.1K bytes
in 74 lines about:
: I would like to continue to run a Tor relay node but am unable to do so
until I
: resolve the problem described below, and I need help in order to do that.
: I just upgraded to versions
:
: 0.1.10 of Vidalia
: and
: 0.2.1.7 of Tor
:
: Vidalia is able to run Tor as a client without any problems.
:
: Nov 30 22:02:52.906 [Error] set_options(): Bug: Acting on config options
left us
: in a broken state. Dying.
: Nov 30 22:02:52.906 [Warning] eventdns: Didn't find any nameservers.
: Nov 30 22:02:52.906 [Warning] Could not config nameservers.
: Nov 30 22:02:52.906 [Error] set_options(): Bug: Acting on config options
left us
: in a broken state. Dying.
A few things, you probably haven't received a response because no one
has a good idea how to fix it. You may have 2 issues, one is that
libevent can't find nameservers, and the other is that the config
options are broken.
As for the dns issues:
https://bugs.torproject.org/flyspray/index.php?do=detailsid=813
or
https://bugs.torproject.org/flyspray/index.php?do=detailsid=868
Are you running Windows?
For the config issues, which may be related to the dns issues, do you
have a copy of the torrc that's generated by Vidalia?
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkk2wI8ACgkQ3ju7mowpX9UchACfQDiYtnb3iWusL1ka4U31BvJy
6fsAn1UdqWl4mWVuoN1K+bmApXAbV2tM
=SBt0
-END PGP SIGNATURE-
Re: [Fwd: (Probably) a known problem?] - cant run a relay node
I had horrible troubles getting the latest tor 0.2.1.7 working after upgrading. I use Tork, not Vidalia, but I suspect the problem is likely the same. I deleted my existing tor directory (in linux, that is in /home/your home directory/.tor - I have no idea if there is an equivalent windows setup to this - the directory that contains your tor configuration file) and started tor up again and it worked fine. I then had to manually edit the config file to add my server name, contact info, etc. Since then, it has worked. praedor On Wednesday 03 December 2008 12:15:50 Alessandro Donnini wrote: Thanks for the response. I understand. Below, you will find the copy of the Vidalia generated torrc. The problem is occurring on a system running MS Windows XP SP2. Note that prior to the upgrade from 0.2.0.31 to 0.2.1.7 I had no problems. The problems started occurring as soon as I started Tor again via Vidalia after the upgrade. Also note that I do not have any problems running the Tor client. Thanks torrc from Document and Settings\user name\Application Data\Vidalia == # This file was generated by Tor; if you edit it, comments will not be preserved # The old torrc file was renamed to torrc.orig.1 or similar, and Tor will ignore it # If set, Tor will accept connections from the same machine (localhost only) # on this port, and allow those connections to control the Tor process using # the Tor Control Protocol (described in control-spec.txt). ControlPort 9051 # Where to send logging messages. Format is minSeverity[-maxSeverity] # (stderr|stdout|syslog|file FILENAME). Log notice stdout [EMAIL PROTECTED] wrote: On Wed, Dec 03, 2008 at 09:34:40AM -0500, [EMAIL PROTECTED] wrote 2.1K bytes in 74 lines about: : I would like to continue to run a Tor relay node but am unable to do so : until I resolve the problem described below, and I need help in order : to do that. : : I just upgraded to versions : : 0.1.10 of Vidalia : and : 0.2.1.7 of Tor : : Vidalia is able to run Tor as a client without any problems. : : Nov 30 22:02:52.906 [Error] set_options(): Bug: Acting on config : options left us in a broken state. Dying. : Nov 30 22:02:52.906 [Warning] eventdns: Didn't find any nameservers. : Nov 30 22:02:52.906 [Warning] Could not config nameservers. : Nov 30 22:02:52.906 [Error] set_options(): Bug: Acting on config : options left us in a broken state. Dying. A few things, you probably haven't received a response because no one has a good idea how to fix it. You may have 2 issues, one is that libevent can't find nameservers, and the other is that the config options are broken. As for the dns issues: https://bugs.torproject.org/flyspray/index.php?do=detailsid=813 or https://bugs.torproject.org/flyspray/index.php?do=detailsid=868 Are you running Windows? For the config issues, which may be related to the dns issues, do you have a copy of the torrc that's generated by Vidalia? gpgkeys: key DE3BBB9A8C295FD5 not found on keyserver
Re: [Fwd: (Probably) a known problem?] - cant run a relay node
[EMAIL PROTECTED] wrote: On Wed, Dec 03, 2008 at 09:34:40AM -0500, [EMAIL PROTECTED] wrote 2.1K bytes in 74 lines about: : Nov 30 22:02:52.906 [Error] set_options(): Bug: Acting on config options left us : in a broken state. Dying. : Nov 30 22:02:52.906 [Warning] eventdns: Didn't find any nameservers. : Nov 30 22:02:52.906 [Warning] Could not config nameservers. : Nov 30 22:02:52.906 [Error] set_options(): Bug: Acting on config options left us : in a broken state. Dying. A few things, you probably haven't received a response because no one has a good idea how to fix it. You may have 2 issues, one is that libevent can't find nameservers, and the other is that the config options are broken. While we're talking about DNS issues, I recently got: Nov 30 06:25:02.803 [notice] Tor 0.2.1.6-alpha (r17011) opening new log file. Nov 30 06:25:02.818 [warn] eventdns: Unable to add nameserver 164.148.169.81: error 2 Nov 30 06:25:02.818 [warn] eventdns: Unable to add nameserver 34.148.169.81: error 2 Nov 30 06:25:02.818 [warn] Unable to parse '/etc/resolv.conf', or no nameservers in '/etc/resolv.conf' (6) Nov 30 06:25:02.819 [err] set_options(): Bug: Acting on config options left us in a broken state. Dying. The nameservers were indeed unreachable at that time (the traffic limit was reached and the system offline), but earlier Tor versions continued to run and started working again once the system was back on the net. Fabian signature.asc Description: PGP signature
Firefox,Torbutton leaks real IP Address.
The combination Firefox-3.0.3(in fact,Iceweasel-3.0.3),Torbutton-1.2.0 leaks my real IPaddress.This happens BETWEEN when I initiate Tor-0.2.0.31 with the bash command /usr/local/tor/bin/tor and the moment when Tor effectively establishes a connection-circuit.This can be 60 seconds or more,and if in between we connect to the Internet withFirefox-Torbutton the real IP address is used(even with torbutton running-green)I tested with www.showmyip.com and others.My fear is if the same could happen when Tor changes circuit by ten-ten minutes or so,when leaves the previous circuit to the next one.(what happens in the transition moments).I did not test that situation. Thanks.
Re: Exceeding connection limit
On Wed, Dec 03, 2008 at 03:49:08PM -0500, Praedor Atrebates wrote: On Wednesday 03 December 2008 15:47:17 Praedor Atrebates wrote: I don't understand this message. My tor log (in tork) is full of repetitive messages: 2008-12-03 15:42:38 WARN(1 of 1) Failing because we have 1004 connections already. Please raise your ulimit -n. Over and over (with variable numbers of connections around 1000. Forgot: using tor-0.2.1.7 as a relay server. See #16 at https://www.torproject.org/docs/tor-doc-relay#after Basically your Tor relay has over 1000 connections open. Given that there are 1500 other relays, and 10+ Tor clients running right now, that's not hard to reach. If you were using the Tor deb, it would solve this step for you. :) https://wiki.torproject.org/noreply/TheOnionRouter/TorOnDebian --Roger
Re: Exceeding connection limit
[Forwarding because John isn't subscribed at this address. Here's a more
detailed version of what I said in my other post. -RD]
- Forwarded message from [EMAIL PROTECTED] -
Date: Wed, 3 Dec 2008 13:59:41 -0700
From: John Brooks [EMAIL PROTECTED]
To: or-talk@freehaven.net
Subject: Re: Exceeding connection limit
This happens because the user tor is running as has a system-imposed limit
on the number of open file descriptors - one file descriptor corresponds to
one open file or socket. Many linux systems use '1024' as the default value
here - which is probably what yours is.
The solution to this problem is to raise that limit for tor's user; first by
figuring out what user tor is running as ('ps aux' will show this alongside
the process). Then, you or your sysadmin should raise the FD limit for that
user to something more reasonable for a socket-hungry application like tor.
I use 4096.
On many linux systems, this can be changed in /etc/security/limits.conf with
lines like:
toruserhard nofile4096
torusersoftnofile4096
I would recommend setting both the hard and soft limits (as shown), for
simplicity. There are other methods for other situations or systems, but
that should work on most forms of linux. Note that after changing this, you
will need to shut down tor, open a new terminal (important), and start tor
again for the new limit to take effect.
Also note that some VPS/VDS systems severely limit open sockets, so if
you're using one of those, you may not be able to use as many as tor would
want.
Hope that helps.
- John Brooks
On Wed, Dec 3, 2008 at 1:49 PM, Praedor Atrebates [EMAIL PROTECTED] wrote:
On Wednesday 03 December 2008 15:47:17 Praedor Atrebates wrote:
I don't understand this message. My tor log (in tork) is full of
repetitive messages:
2008-12-03 15:42:38 WARN (1 of 1) Failing because we have 1004
connections
already. Please raise your ulimit -n.
Over and over (with variable numbers of connections around 1000.
Forgot: using tor-0.2.1.7 as a relay server.
praedor
- End forwarded message -
Re: [Fwd: (Probably) a known problem?] - cant run a relay node
I erred. I am no longer using 0.2.1.7. I had to give up because I could not get it working properly. Doing what I mention below allowed me to run tor via Vidalia but not via Tork (my preferred tor manager). There was an issue with the config file that I could never figure out so I went back to a previous version of tor that worked (currently that is 0.2.0.31. Don't think I will mess with 0.2.1.7 again. Since you use Vidalia, you might manage to get it working more than temporarily. praedor On Wednesday 03 December 2008 12:26:51 Praedor Atrebates wrote: I had horrible troubles getting the latest tor 0.2.1.7 working after upgrading. I use Tork, not Vidalia, but I suspect the problem is likely the same. I deleted my existing tor directory (in linux, that is in /home/your home directory/.tor - I have no idea if there is an equivalent windows setup to this - the directory that contains your tor configuration file) and started tor up again and it worked fine. I then had to manually edit the config file to add my server name, contact info, etc. Since then, it has worked. praedor On Wednesday 03 December 2008 12:15:50 Alessandro Donnini wrote: Thanks for the response. I understand. Below, you will find the copy of the Vidalia generated torrc. The problem is occurring on a system running MS Windows XP SP2. Note that prior to the upgrade from 0.2.0.31 to 0.2.1.7 I had no problems. The problems started occurring as soon as I started Tor again via Vidalia after the upgrade. Also note that I do not have any problems running the Tor client. Thanks torrc from Document and Settings\user name\Application Data\Vidalia == # This file was generated by Tor; if you edit it, comments will not be preserved # The old torrc file was renamed to torrc.orig.1 or similar, and Tor will ignore it # If set, Tor will accept connections from the same machine (localhost only) # on this port, and allow those connections to control the Tor process using # the Tor Control Protocol (described in control-spec.txt). ControlPort 9051 # Where to send logging messages. Format is minSeverity[-maxSeverity] # (stderr|stdout|syslog|file FILENAME). Log notice stdout [EMAIL PROTECTED] wrote: On Wed, Dec 03, 2008 at 09:34:40AM -0500, [EMAIL PROTECTED] wrote 2.1K bytes in 74 lines about: : I would like to continue to run a Tor relay node but am unable to do : so until I resolve the problem described below, and I need help in : order to do that. : : I just upgraded to versions : : 0.1.10 of Vidalia : and : 0.2.1.7 of Tor : : Vidalia is able to run Tor as a client without any problems. : : Nov 30 22:02:52.906 [Error] set_options(): Bug: Acting on config : options left us in a broken state. Dying. : Nov 30 22:02:52.906 [Warning] eventdns: Didn't find any : nameservers. Nov 30 22:02:52.906 [Warning] Could not config : nameservers. Nov 30 22:02:52.906 [Error] set_options(): Bug: Acting : on config options left us in a broken state. Dying. A few things, you probably haven't received a response because no one has a good idea how to fix it. You may have 2 issues, one is that libevent can't find nameservers, and the other is that the config options are broken. As for the dns issues: https://bugs.torproject.org/flyspray/index.php?do=detailsid=813 or https://bugs.torproject.org/flyspray/index.php?do=detailsid=868 Are you running Windows? For the config issues, which may be related to the dns issues, do you have a copy of the torrc that's generated by Vidalia? gpgkeys: key DE3BBB9A8C295FD5 not found on keyserver
Re: [Fwd: (Probably) a known problem?] - cant run a relay node
I was not online for fiew days but i think i might have a solution for Your problem (worked for me) 1) in torrc add following line ServerDNSResolvConfFile c:\resolv.conf and inside of resolv.conf put following 3 lines nameserver xxx.xxx.xxx.xxx nameserver yyy.yyy.yyy.yyy search your.primary.domain where xxx.xxx.xxx.xxx and yyy.yyy.yyy.yyy are ip adresses of Your DNS servers the third line is optional and is used to instruct linux computers for what domain above DNS servers are authoritative (not sure if its needed but i added it) after those changes everything started to work (im not using vidalia to run Tor i configured it as a service so its running whenewer my mashine is up Hope this will be helpfull for You 2008/12/3 Praedor Atrebates [EMAIL PROTECTED]: I erred. I am no longer using 0.2.1.7. I had to give up because I could not get it working properly. Doing what I mention below allowed me to run tor via Vidalia but not via Tork (my preferred tor manager). There was an issue with the config file that I could never figure out so I went back to a previous version of tor that worked (currently that is 0.2.0.31. Don't think I will mess with 0.2.1.7 again. Since you use Vidalia, you might manage to get it working more than temporarily. praedor On Wednesday 03 December 2008 12:26:51 Praedor Atrebates wrote: I had horrible troubles getting the latest tor 0.2.1.7 working after upgrading. I use Tork, not Vidalia, but I suspect the problem is likely the same. I deleted my existing tor directory (in linux, that is in /home/your home directory/.tor - I have no idea if there is an equivalent windows setup to this - the directory that contains your tor configuration file) and started tor up again and it worked fine. I then had to manually edit the config file to add my server name, contact info, etc. Since then, it has worked. praedor On Wednesday 03 December 2008 12:15:50 Alessandro Donnini wrote: Thanks for the response. I understand. Below, you will find the copy of the Vidalia generated torrc. The problem is occurring on a system running MS Windows XP SP2. Note that prior to the upgrade from 0.2.0.31 to 0.2.1.7 I had no problems. The problems started occurring as soon as I started Tor again via Vidalia after the upgrade. Also note that I do not have any problems running the Tor client. Thanks torrc from Document and Settings\user name\Application Data\Vidalia == # This file was generated by Tor; if you edit it, comments will not be preserved # The old torrc file was renamed to torrc.orig.1 or similar, and Tor will ignore it # If set, Tor will accept connections from the same machine (localhost only) # on this port, and allow those connections to control the Tor process using # the Tor Control Protocol (described in control-spec.txt). ControlPort 9051 # Where to send logging messages. Format is minSeverity[-maxSeverity] # (stderr|stdout|syslog|file FILENAME). Log notice stdout [EMAIL PROTECTED] wrote: On Wed, Dec 03, 2008 at 09:34:40AM -0500, [EMAIL PROTECTED] wrote 2.1K bytes in 74 lines about: : I would like to continue to run a Tor relay node but am unable to do : so until I resolve the problem described below, and I need help in : order to do that. : : I just upgraded to versions : : 0.1.10 of Vidalia : and : 0.2.1.7 of Tor : : Vidalia is able to run Tor as a client without any problems. : : Nov 30 22:02:52.906 [Error] set_options(): Bug: Acting on config : options left us in a broken state. Dying. : Nov 30 22:02:52.906 [Warning] eventdns: Didn't find any : nameservers. Nov 30 22:02:52.906 [Warning] Could not config : nameservers. Nov 30 22:02:52.906 [Error] set_options(): Bug: Acting : on config options left us in a broken state. Dying. A few things, you probably haven't received a response because no one has a good idea how to fix it. You may have 2 issues, one is that libevent can't find nameservers, and the other is that the config options are broken. As for the dns issues: https://bugs.torproject.org/flyspray/index.php?do=detailsid=813 or https://bugs.torproject.org/flyspray/index.php?do=detailsid=868 Are you running Windows? For the config issues, which may be related to the dns issues, do you have a copy of the torrc that's generated by Vidalia? gpgkeys: key DE3BBB9A8C295FD5 not found on keyserver
Tried one last time, giving up on 0.2.1.7-alpha
I went ahead and tried to use tor-0.2.1.7 again and again it has failed without any debug information or error messages or anything else to explain why it refuses to run. If I totally delete my ~/.tor directory and start tor from the CLI, it will start and run for a little while (say less than a minute) and then just quit. If I then try to start it again, it is an IMMEDIATE fail without any messages to explain why. Using Tork, I use the First Run Wizard to try to get tor and tork setup and then hit the start tor button. It starts out as if it is going to work, usually doing the bootstrapping thing until about 90%, then POOF, no more tor and any attempt to start it again immediately fails. Can someone please supply me with a torrc file that actually works with 0.2.1.7-alpha (with your own personal settings altered) so I can try that? The torrc.sample that comes with the 0.2.1.7 install doesn't work when I try to manually edit it instead of using Tork. praedor
Re: Firefox,Torbutton leaks real IP Address.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Luis Maceira wrote: The combination Firefox-3.0.3(in fact,Iceweasel-3.0.3),Torbutton-1.2.0 leaks my real IPaddress.This happens BETWEEN when I initiate Tor-0.2.0.31 with the bash command /usr/local/tor/bin/tor and the moment when Tor effectively establishes a connection-circuit.This can be 60 seconds or more,and if in between we connect to the Internet withFirefox-Torbutton the real IP address is used(even with torbutton running-green)I tested with www.showmyip.com and others.My fear is if the same could happen when Tor changes circuit by ten-ten minutes or so,when leaves the previous circuit to the next one.(what happens in the transition moments).I did not test that situation. Thanks. Whenever tor is switching circuits, I just get a proxy error and I'm never actually able to get to a page. Did you install Tor from source? If not, where did you get it? Ringo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFJNwGU6pWcWSc5BE4RApFwAJ4whn5J4knfxgpdYX6GDq97Pi8JCQCgl4Mu c4ycKWr6yEUj/We28V6SFss= =zD1O -END PGP SIGNATURE-
Re: Firefox,Torbutton leaks real IP Address.
Hi, i think the main problem is that via java/javacript the browser can do direct connections, bypassing your proxy and only using your default gateway! You can see this bypassing with test sites like https://www.jondos.de/de/anontest . That's why i am not using a default gateway on the PC i am using and usually you only need proxy and no default gateway (behind the Router with the firewall and proxy). For some situations like updating my homepage via ssh/rsync i'm using a default gateway but only for a short time (approx. 1 minute) and at that time i'm using no browser. Regards, Rolf The combination Firefox-3.0.3(in fact,Iceweasel-3.0.3),Torbutton-1.2. 0 leaks my real IP address.This happens BETWEEN when I initiate Tor-0.2.0.31 with the bash command /usr/local/tor/bin/tor and the moment when Tor effectively establishes a connection-circuit. This can be 60 seconds or more,and if in between we connect to the Internet with Firefox-Torbutton the real IP address is used(even with torbutton running-green) I tested with www.showmyip.com and others.My fear is if the same could happen when Tor changes circuit by ten-ten minutes or so,when leaves the previous circuit to the next one.(what happens in the transition moments).I did not test that situation. Thanks.
Re: Tried one last time, giving up on 0.2.1.7-alpha
I thought you could run tor without a torrc file and it will default to client mode with default settings.Also, I did a build with 0.2.1.7-alpha about two weeks ago with no problems. Are you building from source? Are you using a pre-packaged version? Where did you get it from? - Kyle On Wed, Dec 3, 2008 at 2:00 PM, Praedor Atrebates [EMAIL PROTECTED] wrote: I went ahead and tried to use tor-0.2.1.7 again and again it has failed without any debug information or error messages or anything else to explain why it refuses to run. If I totally delete my ~/.tor directory and start tor from the CLI, it will start and run for a little while (say less than a minute) and then just quit. If I then try to start it again, it is an IMMEDIATE fail without any messages to explain why. Using Tork, I use the First Run Wizard to try to get tor and tork setup and then hit the start tor button. It starts out as if it is going to work, usually doing the bootstrapping thing until about 90%, then POOF, no more tor and any attempt to start it again immediately fails. Can someone please supply me with a torrc file that actually works with 0.2.1.7-alpha (with your own personal settings altered) so I can try that? The torrc.sample that comes with the 0.2.1.7 install doesn't work when I try to manually edit it instead of using Tork. praedor
Re: Exceeding connection limit
On Wed, Dec 03, 2008 at 11:44:13PM +0100, [EMAIL PROTECTED] wrote 2.4K bytes in 54 lines about: : is there any easy way, how to limit connections for Tor? Thousands of : connections often breaks my lowcost ADSL router at home and I have to : restart it. This is a FAQ answer, https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#CablemodemCrashes : I think it should be similar option like Bandwidth rate. Or is there any : reason, why there must be thousands of connection from point of Tor network : design? In the manual page, there is: ConnLimit NUM The minimum number of file descriptors that must be available to the Tor process before it will start. Tor will ask the OS for as many file descriptors as the OS will allow (you can find this by ulimit -H -n). If this number is less than ConnLimit, then Tor will refuse to start. You probably don't need to adjust this. It has no effect on Windows since that platform lacks getrlimit(). (Default: 1000) This may or may not work to fix the problems with a poorly designed ADSL router. As for the design questions, I'll let someone else answer that as I can't find the details as to why right now. -- Andrew
Re: Tried one last time, giving up on 0.2.1.7-alpha
On Wed, Dec 03, 2008 at 05:00:52PM -0500, [EMAIL PROTECTED] wrote 1.0K bytes in 20 lines about: : I went ahead and tried to use tor-0.2.1.7 again and again it has failed : without any debug information or error messages or anything else to explain : why it refuses to run. Try running without any config file, only letting Vidalia configure it. TorK may or may not be invoking a new bug. -- Andrew
Re: Firefox,Torbutton leaks real IP Address.
On Wed, Dec 03, 2008 at 11:15:27AM -0800, [EMAIL PROTECTED] wrote 2.0K bytes in 34 lines about: : The combination Firefox-3.0.3(in fact,Iceweasel-3.0.3),Torbutton-1.2.0 leaks my real IPaddress.This happens BETWEEN when I initiate Tor-0.2.0.31 with the bash command /usr/local/tor/bin/tor and the moment when Tor effectively establishes a connection-circuit.This can be 60 seconds or more,and if in between we connect to the Internet withFirefox-Torbutton the real IP address is used(even with torbutton running-green)I tested with www.showmyip.com and others.My fear is if the same could happen when Tor changes circuit by ten-ten minutes or so,when leaves the previous circuit to the next one.(what happens in the transition moments).I did not test that situation. Thanks. Is torbutton enabled in Firefox the entire time? When I try to replicate this, Firefox reports the socks proxy isn't available. Are you using Firefox directly with Tor? Or do you have privoxy/polipo in between Firefox and Tor? -- Andrew
Re: [Fwd: (Probably) a known problem?] - cant run a relay node
On Wed, Dec 03, 2008 at 06:35:19PM +0100, [EMAIL PROTECTED] wrote 2.0K bytes in 56 lines about: For those experiencing issues with nameservers and win32, I've built a Tor package based on r17477. This is just Tor, not vidalia, not privoxy. The goal is to try to fix the issues, currently bugs 868 and 813. Nick made some changes to try to figure out what's going on. This I signed it with the same key I sign the real tor packages. It's available at: http://moria.seul.org/~phobos/tor-0.2.1.7-alpha-dev-win32.exe and http://moria.seul.org/~phobos/tor-0.2.1.7-alpha-dev-win32.exe.asc -- Andrew
Resolving 0.2.1.7 issue
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, I installed tor-0.2.1.7-alpha-dev-win32.exe, deleted torrc from the Vidalia Application Data directory, and started Vidalia. So far, so good, Tor is configured to run as a relay node (nessuno), and seems to be running normally. The logs appear to be normal (no warnings or errors). Please let me know if you need any information or you would like me to do something to verify that the problem I reported on 11/30 (sorry I deleted the messages related to the posting) was resolved by tor-0.2.1.7-alpha-dev-win32.exe Thanks. Alex Donnini -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkk3UFcACgkQ3ju7mowpX9UqKwCgx+sGyQdKUOeSeSwDviC4Nff0 waYAoJlXwXW+xgkOw4XguN2Z+uxDBK0p =+509 -END PGP SIGNATURE-
Re: Exceeding connection limit
On Wed, Dec 03, 2008 at 07:40:54PM -0500, [EMAIL PROTECTED] wrote: In the manual page, there is: ConnLimit NUM The minimum number of file descriptors that must be available to the Tor process before it will start. Note that this is the *minimum* number. Basically the config option is not useful in this case. (Or most other cases.) As for the design questions, I'll let someone else answer that as I can't find the details as to why right now. Alas, right now the Tor design assumes that all relays can reach all other relays. Since clients choose paths randomly, and there are roughly 100 times more clients than there are relays, then pretty much every link is going to be in use. There are some research directions for restricted route topologies, but they still have some hard challenges. One of the little ones is how to grow the topology such that it maintains small-worlds properties as new relays join and old relays disappear. One of the big ones is communicating the topology to the clients in an efficient way, so they can know which links they're allowed to use. Another big one is analyzing how much anonymity we lose by making route selection more predictable -- done right we shouldn't lose much, but I'd need to work out a lot more details before really believing it. The more long-term solution for this is to switch to UDP transport between relays. Done right, that basically means a few sockets would handle all the TLS connections (well, DTLS then), and Tor would get a lot smarter about handling the multiplexing between conversations internally. The proposals you've seen on here from Joel Reardon and from Camilo Viecco would move us in that direction. --Roger
Re: Resolving 0.2.1.7 issue
On Wed, Dec 03, 2008 at 10:36:55PM -0500, [EMAIL PROTECTED] wrote 0.8K bytes in 26 lines about: : So far, so good, Tor is configured to run as a relay node (nessuno), and seems : to be running normally. The logs appear to be normal (no warnings or errors). Great. If you see errors relating to nameservers, please keep us informed. -- Andrew
Re: [Fwd: (Probably) a known problem?] - cant run a relay node
Fabian Keil [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] wrote: On Wed, Dec 03, 2008 at 09:34:40AM -0500, [EMAIL PROTECTED] wrote 2.1K bytes in 74 lines about: : Nov 30 22:02:52.906 [Error] set_options(): Bug: Acting on config options left us : in a broken state. Dying. : Nov 30 22:02:52.906 [Warning] eventdns: Didn't find any nameservers. : Nov 30 22:02:52.906 [Warning] Could not config nameservers. : Nov 30 22:02:52.906 [Error] set_options(): Bug: Acting on config options left us : in a broken state. Dying. A few things, you probably haven't received a response because no one has a good idea how to fix it. You may have 2 issues, one is that libevent can't find nameservers, and the other is that the config options are broken. While we're talking about DNS issues, I recently got: Nov 30 06:25:02.803 [notice] Tor 0.2.1.6-alpha (r17011) opening new log file. Nov 30 06:25:02.818 [warn] eventdns: Unable to add nameserver 164.148.169.81: error 2 Nov 30 06:25:02.818 [warn] eventdns: Unable to add nameserver 34.148.169.81: error 2 Nov 30 06:25:02.818 [warn] Unable to parse '/etc/resolv.conf', or no nameservers in '/etc/resolv.conf' (6) Nov 30 06:25:02.819 [err] set_options(): Bug: Acting on config options left us in a broken state. Dying. The nameservers were indeed unreachable at that time (the traffic limit was reached and the system offline), but earlier Tor versions continued to run and started working again once the system was back on the net. It's probably worth mentioning that this is a relay server running on a GNU/Linux system. Fabian signature.asc Description: PGP signature
