Re: [tor-dev] Potential regression when binding sockets to interface without default route

2016-09-19 Thread René Mayrhofer
Wow, thanks for the quick and detailed answer! Am 2016-09-19 um 16:32 schrieb teor: > This isn't the default setup, but it's actually quite common, > particularly for Exit relays that want to segregate their outbound > traffic from their public relay address. Good to know that we aren't doing anyt

Re: [tor-dev] Potential regression when binding sockets to interface without default route

2016-09-19 Thread René Mayrhofer
Am 2016-09-19 um 20:01 schrieb grarpamp: > On Mon, Sep 19, 2016 at 9:14 AM, René Mayrhofer wrote: >> Sep 19 11:37:41.000 [warn] I have no descriptor for the router named >> "ins1" in my declared family; I'll use the nickname as is, but this may >> confuse clients. >> Sep 19 11:37:41.000 [warn] I h

Re: [tor-dev] Potential regression when binding sockets to interface without default route

2016-09-19 Thread René Mayrhofer
Am 2016-09-19 um 20:24 schrieb grarpamp: > On Mon, Sep 19, 2016 at 9:14 AM, René Mayrhofer wrote: >> Setup: Please note that our setup is a bit particular for reasons that >> we will explain in more detail in a later message (including a proposed >> patch to the current source which has been pendi

Re: [tor-dev] Potential regression when binding sockets to interface without default route

2016-09-19 Thread grarpamp
On Mon, Sep 19, 2016 at 9:14 AM, René Mayrhofer wrote: > Setup: Please note that our setup is a bit particular for reasons that > we will explain in more detail in a later message (including a proposed > patch to the current source which has been pending also because of the > holiday situation...)

Re: [tor-dev] Potential regression when binding sockets to interface without default route

2016-09-19 Thread grarpamp
On Mon, Sep 19, 2016 at 9:14 AM, René Mayrhofer wrote: > Sep 19 11:37:41.000 [warn] I have no descriptor for the router named > "ins1" in my declared family; I'll use the nickname as is, but this may > confuse clients. > Sep 19 11:37:41.000 [warn] I have no descriptor for the router named > "ins2"

Re: [tor-dev] Potential regression when binding sockets to interface without default route

2016-09-19 Thread s7r
Hello, On 9/19/2016 4:14 PM, René Mayrhofer wrote: [SNIP] > Problem: This worked nicely with Tor 0.2.5.12-1 on Debian Jessie. We > upgraded about two weeks ago to 0.2.8.7-1 from the Tor apt repositories > (mostly in response to > https://blog.torproject.org/blog/tor-0287-released-important-fixes a

[tor-dev] More changes to CollecTor's sanitized bridge descriptors: sanitized TCP ports, tarballs per descriptor type

2016-09-19 Thread Karsten Loesing
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi devs, lots of changes to CollecTor's sanitized bridge descriptors these weeks. A few weeks ago there was the switch from Tonga to Bifroest change: https://lists.torproject.org/pipermail/tor-dev/2016-August/011336.html This message is about two u

Re: [tor-dev] Potential regression when binding sockets to interface without default route

2016-09-19 Thread teor
Hi René, Sorry that the upgrade to 0.2.8 has caused problems for you. Thanks for analysing the issue, and for a very detailed bug report. I have tried to explain why this happened below - there have been a lot of changes since 0.2.5, and what you're seeing is due to at least two of those chang

Re: [tor-dev] Potential regression when binding sockets to interface without default route

2016-09-19 Thread Peter Palfrader
René Mayrhofer schrieb am Montag, dem 19. September 2016: > Update: After a hint by Peter Palfrader, I now set the Address option as > well: > > root@tor2 ~ # grep Address /etc/tor/torrc > Address 193.171.202.146 > OutboundBindAddress 193.171.202.150 > > This seems to work with 0.2.8.7-1, so we

Re: [tor-dev] Potential regression when binding sockets to interface without default route

2016-09-19 Thread René Mayrhofer
Update: After a hint by Peter Palfrader, I now set the Address option as well: root@tor2 ~ # grep Address /etc/tor/torrc Address 193.171.202.146 OutboundBindAddress 193.171.202.150 This seems to work with 0.2.8.7-1, so we should be up and running with a recent version now. However, we did not set

[tor-dev] Potential regression when binding sockets to interface without default route

2016-09-19 Thread René Mayrhofer
Dear Tor developers, [Please CC me in replies, I am not currently subscribed to tor-dev.] Context: At the Institute of Networks and Security at Johannes Kepler University Linz, we have been hosting Austria's fastest exit node for the last ca. 9 months. It used to be listed as https://atlas.torpro

Re: [tor-dev] Tor Browser downloads and updates graphs

2016-09-19 Thread Karsten Loesing
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 17/09/16 18:28, Aaron Johnson wrote: >>> Here's >>> >>> the same graph with more data, more request types, and of >>> course a lot more shininess: >>> >>> https://tor-metrics.shinyapps.io/webstats/ >>>

Re: [tor-dev] Tor Browser downloads and updates graphs

2016-09-19 Thread Karsten Loesing
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 17/09/16 17:52, Lunar wrote: > Karsten Loesing: >> On 11/09/16 18:13, Georg Koppen wrote: >>> Here are the graphs showing initial downloads, update pings and >>> update requests over time: >> >>> https://people.torproject.org/~karsten/volatile/tor