Re: Excessive scrubs
Upgrade Vidalia to 0.2.10 and the problem will go away. On 10/14/2010 6:20 PM, Jon wrote: Justin, The first of the scrubs have now showed for the past 4 hrs. Once an hour. It is now showing the address and it is the same address. It is a ' geoips vidalia ' address ( am not showing complete addy ). Apparently for some reason it is not resolving or connecting to address. I did attempt to try directly, with a couple of different ways and was not able to access the site. If you want the complete address, I will put in later. Will see if it is the only one that shows up over the next 12 hrs. Jon On Thu, Oct 14, 2010 at 9:44 AM, Justin Aplin wrote: On Oct 14, 2010, at 9:04 AM, Jon wrote: I had added the ' SafeLogging 0 ' to the file as per Tor-ops message/reply. Twenty four hours later when I saw that it had not removed the ' scrubbed ' and replaced it with the node/address, I checked the file again and it was not in the file where I put it. Was Vidalia running when you edited the torrc? Vidalia (on Windows, at least) has a bad habit of overwriting changes to the torrc that it isn't aware of. Personally I think there should be a "Confirm before modifying torrc" checkbox in Vidalia. I just checked it now, It is still in the file, but the logs still show the ' scubbed' and not the address as supposedly the ' SafeLogging 0 ' was to replace. Time wise it appears to be at a minimum of once an hour. Which makes me believe it is the same address that is being scrubbed. Try shutting down both Tor and Vidalia, making your edits, restarting both, and rechecking your torrc/logs. If you've done all this, please let us know. ~Justin Aplin *** To unsubscribe, send an e-mail to majord...@torproject.org with unsubscribe or-talkin the body. http://archives.seul.org/or/talk/
Re: AdvTor
On 10/9/2010 11:14 AM, Anon Mus wrote: Fabian Keil wrote: And Tor says: Oct 09 14:00:19.571 [notice] Have tried resolving or connecting to address 'www.cobblers.za' at 3 different places. Giving up. Fabian Ahh, I have those but they only say, "Oct 09 15:31:32.109 [Notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up." "[scrubbed]" what is this url? What places did it try in? Add the below line to your torrc and the scrubbed will be replaced by the domain in question. SafeLogging 0 *** To unsubscribe, send an e-mail to majord...@torproject.org with unsubscribe or-talkin the body. http://archives.seul.org/or/talk/
Re: What causes this error?
On 3/6/2010 4:07 PM, and...@torproject.org wrote: On Sat, Mar 06, 2010 at 03:00:19PM -0500, to...@optonline.net wrote 0.4K bytes in 7 lines about: Mar 06 14:27:37.436 [Warning] We just marked ourself as down. Are your external addresses reachable? Well, is your IP address reachable from the Internet? Yes, and I am still getting some light traffic now. Mar 06 11:46:54.200 [Notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor. *** To unsubscribe, send an e-mail to majord...@torproject.org with unsubscribe or-talkin the body. http://archives.seul.org/or/talk/
What causes this error?
I noticed there's not much traffic coming through my relay and found this in the log. Any ideas? Mar 06 14:27:37.436 [Warning] We just marked ourself as down. Are your external addresses reachable? *** To unsubscribe, send an e-mail to majord...@torproject.org with unsubscribe or-talkin the body. http://archives.seul.org/or/talk/
Re: Problems with setting up a private Tor network and setting up your own Tor relay(s)
I am having the same problem. When I put my nickname in EntryNodes, Tor starts fine, but when I add StrictEntryNodes 1 I get this same error. I tried putting in my IP instead of my nickname, but Tor then says that using an IP is not yet supported, using 0.2.1.20. Sambuddho Chakravarty wrote: --When our OR is being used as an Entry Node -- Dec 07 17:03:09.414 [notice] Bootstrapped 80%: Connecting to the Tor network. Dec 07 17:03:09.421 [warn] Failed to find node for hop 0 of our path. Discarding this circuit. Dec 07 17:03:10.426 [warn] Failed to find node for hop 0 of our path. Discarding this circuit. Dec 07 17:03:11.430 [warn] Failed to find node for hop 0 of our path. Discarding this circuit. Dec 07 17:03:12.434 [warn] Failed to find node for hop 0 of our path. Discarding this circuit. Dec 07 17:03:13.438 [warn] Failed to find node for hop 0 of our path. Discarding this circuit. Dec 07 17:03:14.442 [warn] Failed to find node for hop 0 of our path. Discarding this circuit. Dec 07 17:03:15.446 [warn] Failed to find node for hop 0 of our path. Discarding this circuit. --- Thanks Sambuddho *** To unsubscribe, send an e-mail to majord...@torproject.org with unsubscribe or-talkin the body. http://archives.seul.org/or/talk/
Re: Bug?
Roger Dingledine wrote:
On Sat, Oct 10, 2009 at 06:37:46PM -0400, TorOp wrote:
On my Tor network map, every relay has a ? next to it instead of the
country icon.
Is this a bug or is there a file I can remove to get it to show properly?
Platform: Tor 0.2.1.19 on Windows Server 2003 Service Pack 2 [server]
{enterprise} {terminal services, single user} {terminal services}
When you open the network map in Vidalia, that tells Vidalia to go find
out what country and city each relay is in. You'll probably notice an
attempt to some-IP-address port 443 appear in the "connection" part of
the network map window.
Once Vidalia finishes doing those fetches (anonymously, via Tor), it
will replace the question marks with flags.
So if your Tor isn't working, that could be one reason why Vidalia hasn't
figured out the country and city yet. Another reason could be that you
haven't let it try enough yet.
--Roger
Tor has been up and running fine for ~8 hours now, both as client and
server. I've also noticed this behavior when running Tor as a client
only on a different computer, although that one shows ~10% of the
countries. This seems to have started when I went to the 2.1.19 release,
but I'm not 100% sure about that. And yes, I have noticed the occasional
connection to port 443.
***
To unsubscribe, send an e-mail to majord...@torproject.org with
unsubscribe or-talkin the body. http://archives.seul.org/or/talk/
Bug?
On my Tor network map, every relay has a ? next to it instead of the
country icon.
Is this a bug or is there a file I can remove to get it to show properly?
Platform: Tor 0.2.1.19 on Windows Server 2003 Service Pack 2 [server]
{enterprise} {terminal services, single user} {terminal services}
Thanks.
***
To unsubscribe, send an e-mail to majord...@torproject.org with
unsubscribe or-talkin the body. http://archives.seul.org/or/talk/
Re: Comcast throws down gauntlet to residential accounts
Ted Smith wrote: On Mon, 2009-08-10 at 13:39 -0500, Scott Bennett wrote: Verizon residential service is only available at my location if I also buy their telephone service, the combination of which would cost ~ $80/mo. and also require a 12-month contract. I have yet to get the details on Verizon business-class service, but it seems unlikely to be any cheaper. Verizon's residential service does not currently have a cap, but I don't know whether they prohibit listening on ports accessable from the Internet. I believe they do, under the same guise of prohibiting "servers" on consumer-level accounts. I haven't read the AUP, just something I've heard. That being said, I've been running sshd+vpnd+other assorted gunk on my "FIOS" connection for a while, so I would presume that they don't actively enforce that policy. Are there any non-business ISP's in the US that are positive towards using your connection at all? It seems like everything is capped or AUP'd up the wazoo, to the point where you will *not* get what you paid for. I've run various servers for years on my Cablevision/Optimum account without any problems or complaints whatsoever. They do block ports 25 and 80 on the basic account level, however the next level eliminates that and you get 30Mbps down and 5Mbps up with it.
Re: Problem with Tor - Followup
I started it just now and everything is fine. Must have been some weird glitch. TorOp wrote: I started up my Tor node just now and noticed some strange behavior. First, the node CPU utilization went to and stayed at 100%. Second, the bandwidth graph lines moved so fast that I could barely see them go by. I'm running the latest 2.0.21 version and made no changes to anything since it was running fine yesterday. I also noticed that the time on the bandwidth graph was one hour ahead of the actual time although the machine had the correct time. Maybe it has to do with the daylight savings that kicked in today?
Re: Problem with Tor
Windows Server 2003, with all the latest patches, running under MS Virtual PC. Ringo Kamens wrote: Are you on Windows? Linux? Comrade Ringo Kamens On 3/9/08, *TorOp* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote: I started up my Tor node just now and noticed some strange behavior. First, the node CPU utilization went to and stayed at 100%. Second, the bandwidth graph lines moved so fast that I could barely see them go by. I'm running the latest 2.0.21 version and made no changes to anything since it was running fine yesterday. I also noticed that the time on the bandwidth graph was one hour ahead of the actual time although the machine had the correct time. Maybe it has to do with the daylight savings that kicked in today?
Problem with Tor
I started up my Tor node just now and noticed some strange behavior. First, the node CPU utilization went to and stayed at 100%. Second, the bandwidth graph lines moved so fast that I could barely see them go by. I'm running the latest 2.0.21 version and made no changes to anything since it was running fine yesterday. I also noticed that the time on the bandwidth graph was one hour ahead of the actual time although the machine had the correct time. Maybe it has to do with the daylight savings that kicked in today?
Re: Huh?
Andrew wrote: TorOp schrieb: And what's this about? Jan 27 10:08:00.373 [Notice] Our IP Address has changed from 69.119.206.101 to 212.112.242.159; rebuilding descriptor. Jan 27 10:08:01.595 [Notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor. Jan 27 10:08:46.068 [Notice] Our IP Address has changed from 212.112.242.159 to 69.119.206.101; rebuilding descriptor. Jan 27 10:08:51.206 [Notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor. That seems to be a (rare) issue with the new alpha versions. A similar log has been posted to this list not too long ago (john smith: unusual connection activity?). Note that *both* IPs point to a tor-node: Zippy (MybKsCAd5bQuzF48aFY3JyuOjxs IGJmo96Yu7liu1Y9xM8jSEV82Jk) and maximator (+pyyTwuDM1sEKAOFYKJM2GYdF2c /zMSZTixMZpKvzJjBa0siBJ8O1U), both of which were set up today according to the directory http://moria.seul.org:9032/tor/status/authority You were/are not by any chance running a second tor server by the name of maximator? If not, developement must be made aware of this issue. Regards, Andrew No, I'm only running one node, and the name has always been Zippy. I am running on a part-time basis, about 14 hours a day, but that's the way I've always run it.
Huh?
I just upgraded to 0.2.0.17 and didn't see an announcement of 0.2.0.18, which I guess I'll install tonight. Jan 27 10:07:38.882 [Warning] Please upgrade! This version of Tor (0.2.0.17-alpha) is not recommended, according to the directory authorities. Recommended versions are: 0.1.2.19,0.2.0.11-alpha,0.2.0.12-alpha,0.2.0.15-alpha,0.2.0.18-alpha Jan 27 10:07:47.034 [Notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor. Jan 27 10:07:52.652 [Notice] Performing bandwidth self-test...done. And what's this about? Jan 27 10:08:00.373 [Notice] Our IP Address has changed from 69.119.206.101 to 212.112.242.159; rebuilding descriptor. Jan 27 10:08:01.595 [Notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor. Jan 27 10:08:46.068 [Notice] Our IP Address has changed from 212.112.242.159 to 69.119.206.101; rebuilding descriptor. Jan 27 10:08:51.206 [Notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Error fetching keys
Been getting these all day today.
Jan 10 19:33:14.675 [Warning] Received http status code 404 ("Not
found") from server '221.126.240.32:8080' while fetching
"/tor/keys/fp/0D95B91896E6089AB9A3C6CB56E724CAF898C43F".
Jan 10 19:42:22.933 [Warning] Received http status code 404 ("Not
found") from server '128.197.11.30:80' while fetching
"/tor/keys/fp/0D95B91896E6089AB9A3C6CB56E724CAF898C43F".
