Re: [tor-relays] Bridge clients don't *really* update dynamic bridge IPs from fingerprints?
Rick Huebner rhueb...@radiks.net writes: I run a bridge from a semi-static home internet account, where the address is dynamically assigned but only changes when either the ISP or my hardware router goes down and forces a reconnect, which only happens maybe once every several months. I've read in a few places that Tor bridges with dynamic IP addresses are just as useful as those with static addresses, even if their address changes pretty often, because the bridge user's client will use the bridge's fingerprint to look up its current address and port from the bridge authority if it fails to connect. Hello Rick, your intuition is correct. This feature does not work very well. Here are a few reasons why: a) As you said, UpdateBridgesFromAuthority is turned off by default. AFAIK, this is the case because the feature is not very useful atm: most places have already blocked all the Tor authorities including the bridge authority. The feature needs to be slightly reworked. For example, maybe Tor needs to ask any working bridges it has about the descriptor of its dead bridges. Then the working bridges would query the bridge authority themselves and relay the descriptors to the client. However, a Tor proposal is needed to implement the above feature and further analysis is required (for example, is it a good idea to reveal to a bridge what other bridges you are using). Feel free to help us out with this :) b) Also, Tor clients are amnesiac with regards to bridges information. That is, even if they learn the fingerprint or the new IP address of a bridge, they don't write it down on a file. So next time they start up, they have to do the whole thing again. Sebastian wrote a proposal for this a few years ago, but it's still unimplemented: https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/192-store-bridge-information.txt Feel free to help with this too :) The first step is probably to reread the proposal, and see if anything needs to be changed to reflect the current state of Tor. Also, check out this related blog post by Sebastian: https://blog.torproject.org/blog/different-ways-use-bridge Have a good day and sorry for the sad news :) ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Bridge still advertising removed pluggable transport?
Rick Huebner rhueb...@radiks.net writes: Hi. I removed the recently-deprecated obfs2 transport from my (0.2.4.22) bridge's torrc, but after restarting, it seems to still be advertising support for it. It correctly doesn't appear as a Registered server transport obfs2 line in the tor log file, and it's not listed in the TOR_PT_SERVER_TRANSPORTS or TOR_PT_SERVER_BINDADDR env vars fed to obfsproxy, nor is obfsproxy listening at the port that was formerly used for obfs2 any more. But... it's still listed in a TransportProxy obfs2 line in the tor state file after several hours, and is still showing up as a supported transport in my bridge's details page on globe.torproject.org. Greetings Rick, I wouldn't worry too much about the TransportProxy line in your state file. That line is there in case you ever decide to start up an obfs2 listener ever again: it has noted down the IP:PORT it used to use, so that it binds in the same address the next time you start it up (which in your case is 'never'). However, the fact that obfs2 still appears in your bridge's page in globe.torproject.org is more troubling. Is it still there? If yes, how did you deprecate obfs2? Did you restart Tor or did you do a SIGHUP? Feel free to send me a private mail with your IP:PORT and I can try to look into this (see if your bridge is still advertising obfs2 support to the bridge authority). Cheers! ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] BBC iPlayer blocked for UK middle relay operators?
Is anyone else running a relay in the UK having issues accessing BBC iPlayer from the same connection? For the last 6 weeks or so now I've been getting messages telling me I'm 'outside the UK' when I'm in London, and my IP address clearly resolves to show that. Just wondering if the provider BBC use for iPlayer might have started just blocking all Tor IPs recently - including middle relays. Chris ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Spam
On Thu, Jun 26, 2014 at 10:08:51PM +0600, Roman Mamedov wrote: One workaround is to obfuscate the E-Mail you use in your contact details as I mentioned, either lightly or not, I have seen some really creative ways people obfuscate their E-Mail to avoid spam-crawlers. Which is a great thing in case the torproject decides to mail the owners of all relays that are vulnerable to some attack. signature.asc Description: Digital signature ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] BBC iPlayer blocked for UK middle relay operators?
Chris I have had several issues that appeared whilst running a Tor network. This has happened to me too even though I switched mine (relay) off several weeks ago… I have notified BBC (via supplied contact forms 3 times) and have had no resolve Other services affected have been nhs.uk lovefilm.com although since switching my relay off these now work again. My supplier is Virgin Media and I have spent *hours* on tech help support. Nobody can answer this. My dynamic WAN IP (assigned via DHCP) never changes and I’ve been told it can’t won’t ever change…”. It’s been the same IP address for years... Therefore if anybody wants to monitor or divert my traffic they can. Who provides your service? Thanks, Paul On 28 Jun 2014, at 12:52, Chris Whittleston cs...@cam.ac.uk wrote: Is anyone else running a relay in the UK having issues accessing BBC iPlayer from the same connection? For the last 6 weeks or so now I've been getting messages telling me I'm 'outside the UK' when I'm in London, and my IP address clearly resolves to show that. Just wondering if the provider BBC use for iPlayer might have started just blocking all Tor IPs recently - including middle relays. Chris ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] BBC iPlayer blocked for UK middle relay operators?
On Sat, Jun 28, 2014 at 1:23 PM, Paul Blakeman blakey...@mac.com wrote: Chris I have had several issues that appeared whilst running a Tor network. This has happened to me too even though I switched mine (relay) off several weeks ago… I have notified BBC (via supplied contact forms 3 times) and have had no resolve Other services affected have been nhs.uk lovefilm.com although since switching my relay off these now work again. My supplier is Virgin Media and I have spent *hours* on tech help support. Nobody can answer this. My dynamic WAN IP (assigned via DHCP) never changes and I’ve been told it can’t won’t ever change…”. It’s been the same IP address for years... This isn't strictly true. If you are using a 'Super Hub' (Combined cable modem / router for those of you outside the UK) in modem mode with another router, if you change the MAC on the router and reboot the Super Hub, you will get a new IP. Obviously, this requires you swap your router, or have a router capable of changing it's MAC address... Therefore if anybody wants to monitor or divert my traffic they can. Who provides your service? Thanks, Paul On 28 Jun 2014, at 12:52, Chris Whittleston cs...@cam.ac.uk wrote: Is anyone else running a relay in the UK having issues accessing BBC iPlayer from the same connection? For the last 6 weeks or so now I've been getting messages telling me I'm 'outside the UK' when I'm in London, and my IP address clearly resolves to show that. Just wondering if the provider BBC use for iPlayer might have started just blocking all Tor IPs recently - including middle relays. Chris ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] BBC iPlayer blocked for UK middle relay operators?
Paul, I'm also with Virgin Media and have had a similar tech support conversation. I didn't mention I was running a Tor relay to them at the time (do you know anything about their policy regards Tor?), but they checked through all my 'Super Hub' settings including the port forwarding I have set up so I imagine they noticed. They couldn't explain it at all, and because it seems like a completely device agnostic issue (phones etc also don't work) - it is probably on the iPlayer provider's end. I also noticed that I was getting 'Forbidden' errors from the nhs.uk site a while ago and posted about it here - but right now I seem to be able to access everything there just fine so maybe they have reviewed their policy on Tor nodes. Matthew - that's an interesting point about switching out the router MAC address. I'm not currently using a separate router, but might consider it in the future. I guess though that if this is the result of a provider blacklisting all Tor relay IPs, the new IP will just get added to the list as soon as it's published and it'll be blocked again. I think I'm going to continue to harass BBC support about this under I get a response other than 'have you tried turning your router off and on' or 'check your IP is registered in the UK with your ISP' - ugh... Thanks for the info all On 28 June 2014 13:23, Paul Blakeman blakey...@mac.com wrote: Chris I have had several issues that appeared whilst running a Tor network. This has happened to me too even though I switched mine (relay) off several weeks ago… I have notified BBC (via supplied contact forms 3 times) and have had no resolve Other services affected have been nhs.uk lovefilm.com although since switching my relay off these now work again. My supplier is Virgin Media and I have spent *hours* on tech help support. Nobody can answer this. My dynamic WAN IP (assigned via DHCP) never changes and I’ve been told it can’t won’t ever change…”. It’s been the same IP address for years... Therefore if anybody wants to monitor or divert my traffic they can. Who provides your service? Thanks, Paul On 28 Jun 2014, at 12:52, Chris Whittleston cs...@cam.ac.uk wrote: Is anyone else running a relay in the UK having issues accessing BBC iPlayer from the same connection? For the last 6 weeks or so now I've been getting messages telling me I'm 'outside the UK' when I'm in London, and my IP address clearly resolves to show that. Just wondering if the provider BBC use for iPlayer might have started just blocking all Tor IPs recently - including middle relays. Chris ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays -- *Dr Chris Whittleston 栗主* Department of Chemistry University of Cambridge Lensfield Road, Cambridge, CB2 1EW Email: cs...@cam.ac.uk Tel: +44 (0)1223 336423 ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] BBC iPlayer blocked for UK middle relay operators?
Hi all Matthew’s advice is correct. Switching to “modem only” DOES achieve getting a dynamic IP assigned. Not too sure why the normal WAN connection is not like this… (even though assigned via DHCP) Chris - I have “harassed” the BBC 3 times but had NOTHING back from them… I’m going to ditch Virgin Media… Paul On 28 Jun 2014, at 15:46, Chris Whittleston cs...@cam.ac.uk wrote: Paul, I'm also with Virgin Media and have had a similar tech support conversation. I didn't mention I was running a Tor relay to them at the time (do you know anything about their policy regards Tor?), but they checked through all my 'Super Hub' settings including the port forwarding I have set up so I imagine they noticed. They couldn't explain it at all, and because it seems like a completely device agnostic issue (phones etc also don't work) - it is probably on the iPlayer provider's end. I also noticed that I was getting 'Forbidden' errors from the nhs.uk site a while ago and posted about it here - but right now I seem to be able to access everything there just fine so maybe they have reviewed their policy on Tor nodes. Matthew - that's an interesting point about switching out the router MAC address. I'm not currently using a separate router, but might consider it in the future. I guess though that if this is the result of a provider blacklisting all Tor relay IPs, the new IP will just get added to the list as soon as it's published and it'll be blocked again. I think I'm going to continue to harass BBC support about this under I get a response other than 'have you tried turning your router off and on' or 'check your IP is registered in the UK with your ISP' - ugh... Thanks for the info all On 28 June 2014 13:23, Paul Blakeman blakey...@mac.com wrote: Chris I have had several issues that appeared whilst running a Tor network. This has happened to me too even though I switched mine (relay) off several weeks ago… I have notified BBC (via supplied contact forms 3 times) and have had no resolve Other services affected have been nhs.uk lovefilm.com although since switching my relay off these now work again. My supplier is Virgin Media and I have spent *hours* on tech help support. Nobody can answer this. My dynamic WAN IP (assigned via DHCP) never changes and I’ve been told it can’t won’t ever change…”. It’s been the same IP address for years... Therefore if anybody wants to monitor or divert my traffic they can. Who provides your service? Thanks, Paul On 28 Jun 2014, at 12:52, Chris Whittleston cs...@cam.ac.uk wrote: Is anyone else running a relay in the UK having issues accessing BBC iPlayer from the same connection? For the last 6 weeks or so now I've been getting messages telling me I'm 'outside the UK' when I'm in London, and my IP address clearly resolves to show that. Just wondering if the provider BBC use for iPlayer might have started just blocking all Tor IPs recently - including middle relays. Chris ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays -- Dr Chris Whittleston 栗主 Department of Chemistry University of Cambridge Lensfield Road, Cambridge, CB2 1EW Email: cs...@cam.ac.uk Tel: +44 (0)1223 336423 ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] BBC iPlayer blocked for UK middle relay operators?
Paul From what I've read, Virgin issue WAN IPs based on the router MAC address, so for the super-hub which has two MAC addresses (one modem, one router) - it uses the router one. This is why you always get issued the same IP after rebooting or when the DHCP lease expires. The only way around that would be to disconnect the hub, wait for your IP lease to expire (7 days max), then wait an unknown time till it was assigned to someone else, and plug the hub back in to get a fresh IP. Not exactly practical... Did you mention that you were running a Tor relay in the messages you sent to the BBC via their web form? Just wondering if they might be unaware that this might be the issue. Also - I know they had an issue with their contact form not actually submitting data to them, so unless you got an email acknowledging the contact request - they definitely didn't receive it. Here are the last couple of responses I've had from them - both seem somewhat auto-generated: Latest: - Thank you for contacting BBC iPlayer support. We’ll update our help site with any new developments, including the latest programme issues that are currently under investigation, so please check back later. The latest programme issues currently under investigation are available at: http://iplayerhelp.external.bbc.co.uk/help/announcements/programme_latest_issues/ If we haven’t updated the website, it could be that we can’t replicate your problem. In such instances, we’ll monitor for further reports before we investigate. We will try to respond as quickly as possible, but due to the volume of enquiries we receive and the time required to look into technical matters, we’re not always able to reply as quickly as we’d like. - Previous: - Thanks for contacting the BBC iPlayer Support Team. I understand you were experiencing technical issues accessing iPlayer as you have been incorrectly identified as living outside the UK. You mentioned you received an email from our team stating the issue was being investigated by our service partner. If you’re in the UK but see a message saying you’re not, it’s because BBC iPlayer is recognising your IP address as being outside the UK. It could be because your computer is on a foreign-based network, or is being routed overseas. This sometimes happens if you’re at work and your employer isn’t based in the UK. Some programs, like web accelerators, can also make it look like your IP address is outside the UK. Sometimes your internet service provider will allocate you a new IP address, perhaps if they’re carrying out maintenance work. In some cases this new IP address won’t yet be registered as being in the UK, so iPlayer will recognise you as being overseas. It could also simply be a network error. The first thing to try is closing and reopening your web browser. If this doesn’t work, you can try restarting your Wi-Fi router. If you're using a public Wi-Fi network, this may route your connection overseas. Please try again later using a different network. If this still doesn’t work, your best bet is to contact your internet service provider and ask if your IP address is registered in the UK. We have also passed along the information you provided to our team who will investigate this fault. We do appreciate that technical faults affecting programmes on BBC iPlayer can be most frustrating and we try to correct these as quickly as possible. We'd like to assure you that your comments were fully registered. This was included on feedback reports that are available to personnel responsible for maintaining and improving the BBC iPlayer service. These reports are viewed as important documents that can help shape decisions on future aspects of BBC iPlayer across all platforms. Once again, thanks for taking the time to contact us. - Chris On 28 June 2014 15:52, Paul Blakeman blakey...@mac.com wrote: Hi all Matthew’s advice is correct. Switching to “modem only” DOES achieve getting a dynamic IP assigned. Not too sure why the normal WAN connection is not like this… (even though assigned via DHCP) Chris - I have “harassed” the BBC 3 times but had NOTHING back from them… I’m going to ditch Virgin Media… Paul On 28 Jun 2014, at 15:46, Chris Whittleston cs...@cam.ac.uk wrote: Paul, I'm also with Virgin Media and have had a similar tech support conversation. I didn't mention I was running a Tor relay to them at the time (do you know anything about their policy regards Tor?), but they checked through all my 'Super Hub' settings including the port forwarding I have set up so I imagine they noticed. They couldn't explain it at all, and because it seems like a completely device agnostic issue (phones etc also don't work) - it is probably on the iPlayer provider's end. I also noticed that I was
Re: [tor-relays] Directory Server and bandwidth accounting
So, no way to offer DS while setting AccountingMax? -kali- On Thursday, June 26, 2014 10:02 PM, Kali Tor kalito...@yahoo.com wrote: I had not read anything about this either, until I tried to enable it and got this in my log: 10:15:43 [NOTICE] Not advertising DirPort (Reason: AccountingMax enabled) Exactly what I experienced at my side and hence my assumption that enabling AccountingMax disables DirPort and the DS capability. -kali- ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] BBC iPlayer blocked for UK middle relay operators?
FYI - I've just sent another email/contact form to them asking if running a Tor relay could be an issue and explaining in detail the differences between middle and exit relays etc. We shall see if this yields any more useful response from them. I'll keep you posted. On 28 June 2014 16:54, Chris Whittleston cs...@cam.ac.uk wrote: Paul From what I've read, Virgin issue WAN IPs based on the router MAC address, so for the super-hub which has two MAC addresses (one modem, one router) - it uses the router one. This is why you always get issued the same IP after rebooting or when the DHCP lease expires. The only way around that would be to disconnect the hub, wait for your IP lease to expire (7 days max), then wait an unknown time till it was assigned to someone else, and plug the hub back in to get a fresh IP. Not exactly practical... Did you mention that you were running a Tor relay in the messages you sent to the BBC via their web form? Just wondering if they might be unaware that this might be the issue. Also - I know they had an issue with their contact form not actually submitting data to them, so unless you got an email acknowledging the contact request - they definitely didn't receive it. Here are the last couple of responses I've had from them - both seem somewhat auto-generated: Latest: - Thank you for contacting BBC iPlayer support. We’ll update our help site with any new developments, including the latest programme issues that are currently under investigation, so please check back later. The latest programme issues currently under investigation are available at: http://iplayerhelp.external.bbc.co.uk/help/announcements/programme_latest_issues/ If we haven’t updated the website, it could be that we can’t replicate your problem. In such instances, we’ll monitor for further reports before we investigate. We will try to respond as quickly as possible, but due to the volume of enquiries we receive and the time required to look into technical matters, we’re not always able to reply as quickly as we’d like. - Previous: - Thanks for contacting the BBC iPlayer Support Team. I understand you were experiencing technical issues accessing iPlayer as you have been incorrectly identified as living outside the UK. You mentioned you received an email from our team stating the issue was being investigated by our service partner. If you’re in the UK but see a message saying you’re not, it’s because BBC iPlayer is recognising your IP address as being outside the UK. It could be because your computer is on a foreign-based network, or is being routed overseas. This sometimes happens if you’re at work and your employer isn’t based in the UK. Some programs, like web accelerators, can also make it look like your IP address is outside the UK. Sometimes your internet service provider will allocate you a new IP address, perhaps if they’re carrying out maintenance work. In some cases this new IP address won’t yet be registered as being in the UK, so iPlayer will recognise you as being overseas. It could also simply be a network error. The first thing to try is closing and reopening your web browser. If this doesn’t work, you can try restarting your Wi-Fi router. If you're using a public Wi-Fi network, this may route your connection overseas. Please try again later using a different network. If this still doesn’t work, your best bet is to contact your internet service provider and ask if your IP address is registered in the UK. We have also passed along the information you provided to our team who will investigate this fault. We do appreciate that technical faults affecting programmes on BBC iPlayer can be most frustrating and we try to correct these as quickly as possible. We'd like to assure you that your comments were fully registered. This was included on feedback reports that are available to personnel responsible for maintaining and improving the BBC iPlayer service. These reports are viewed as important documents that can help shape decisions on future aspects of BBC iPlayer across all platforms. Once again, thanks for taking the time to contact us. - Chris On 28 June 2014 15:52, Paul Blakeman blakey...@mac.com wrote: Hi all Matthew’s advice is correct. Switching to “modem only” DOES achieve getting a dynamic IP assigned. Not too sure why the normal WAN connection is not like this… (even though assigned via DHCP) Chris - I have “harassed” the BBC 3 times but had NOTHING back from them… I’m going to ditch Virgin Media… Paul On 28 Jun 2014, at 15:46, Chris Whittleston cs...@cam.ac.uk wrote: Paul, I'm also with Virgin Media and have had a similar tech support conversation. I didn't mention I was running a Tor relay
Re: [tor-relays] Circuit purposes
Hi Joel. Where are you getting Purpose: Ags=is_internal,need_capacity, from? Those values are build flags rather than purposes... https://stem.torproject.org/api/control.html#stem.CircBuildFlag Stem should presently document all the values tor can give - all that notice is just letting you know tor reserves the right to add new ones. As for having circuits, tor constructs circuits on occasion for several purposes such as fetching descriptor data. When you first start tor it constructs some circuits optimistically in case you use it as a client, but those circuits eventually die off if unused. I'm not sure if setting SocksPort to zero prevents optimistic circuit construction (though seems it should since they're then unusable). Cheers! -Damian On Fri, Jun 27, 2014 at 9:50 PM, Joel Cretan jcre...@gmail.com wrote: I'm running a relay that I do not intend to use for anything else, so I set SocksPort to 0. I usually have two or three circuits established anyway, though, so I guess I haven't managed to disable creating those. I'm not sure what they are for. They are always labeled Purpose: Ags=is_internal,need_capacity,. Several of them seem to get created around the same time, stay open for a while, and then get closed around the same time. I see some other circuit purposes documented here: https://stem.torproject.org/api/control.html But that documentation indicates that Tor may provide purposes not in this enum, which is the case here. What are these circuits for, and do I need them? Here's my torrc: http://pastebin.com/fuQv8B2m Here's my ifconfig output: http://pastebin.com/mxMkhbMj I'm running tor 0.2.4.22 compiled from source (did not specify any options on make) on raspbian wheezy June 2014 with kernel version 3.12.20+. Thanks, Joel ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Directory Server and bandwidth accounting
On Sat, Jun 28, 2014 at 09:51:08AM -0700, Kali Tor wrote: So, no way to offer DS while setting AccountingMax? Correct. At least in the scenario in this thread, not advertising the dirport is a good choice by Tor, since it saves all your bandwidth for 'real' Tor traffic. The key thing to realize is that normal Tor traffic is bidirectional (that is, it's symmetric -- it comes in and then goes out again), but traffic you serve over your DirPort is only unidirectional. So you'll reach your accountingmax quicker while wasting (not using) half of that bandwidth. See also https://trac.torproject.org/projects/tor/ticket/871 --Roger ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Circuit purposes
Thanks for your answer Damian. That explains the circuits' existence somewhat, though I usually also see new circuits get created after the original ones are closed. For example, in my screenshot below, there are two circuits, but they were soon closed and about 10 minutes later, three new ones opened up. Here is an arm screenshot of where I'm seeing these purpose values: http://laserscorpion.com/images/temp/circuits.png I obscured my own IP since I'm running a bridge, and went ahead and obscured everyone else I was connected to as well. In this case, I've got two circuits constructed, with the unusual purposes shown. Any idea what it means in this context? On Sat, Jun 28, 2014 at 11:32 AM, Damian Johnson ata...@torproject.org wrote: Hi Joel. Where are you getting Purpose: Ags=is_internal,need_capacity, from? Those values are build flags rather than purposes... https://stem.torproject.org/api/control.html#stem.CircBuildFlag Stem should presently document all the values tor can give - all that notice is just letting you know tor reserves the right to add new ones. As for having circuits, tor constructs circuits on occasion for several purposes such as fetching descriptor data. When you first start tor it constructs some circuits optimistically in case you use it as a client, but those circuits eventually die off if unused. I'm not sure if setting SocksPort to zero prevents optimistic circuit construction (though seems it should since they're then unusable). Cheers! -Damian On Fri, Jun 27, 2014 at 9:50 PM, Joel Cretan jcre...@gmail.com wrote: I'm running a relay that I do not intend to use for anything else, so I set SocksPort to 0. I usually have two or three circuits established anyway, though, so I guess I haven't managed to disable creating those. I'm not sure what they are for. They are always labeled Purpose: Ags=is_internal,need_capacity,. Several of them seem to get created around the same time, stay open for a while, and then get closed around the same time. I see some other circuit purposes documented here: https://stem.torproject.org/api/control.html But that documentation indicates that Tor may provide purposes not in this enum, which is the case here. What are these circuits for, and do I need them? Here's my torrc: http://pastebin.com/fuQv8B2m Here's my ifconfig output: http://pastebin.com/mxMkhbMj I'm running tor 0.2.4.22 compiled from source (did not specify any options on make) on raspbian wheezy June 2014 with kernel version 3.12.20+. Thanks, Joel ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Circuit purposes
In this case, I've got two circuits constructed, with the unusual purposes shown. Any idea what it means in this context? Seems to be a parsing error. Arm's last release uses TorCtl which has been deprecated for quite some time and is probably getting confused by those entries. The next release will be Stem based instead so those errors will go away. ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
