Re: [tor-dev] Request for comments: patch to mark exit traffic for routing and statistical analysis

2016-10-24 Thread René Mayrhofer
Am 20.10.2016 um 11:34 schrieb teor: > We generally track tor features using the Tor bug tracker: > https://trac.torproject.org/projects/tor/newticket > Use the Core Tor/Tor component. > > We have found that gitlab is useful for making comments on patches. > But I am also happy to use GitHub, or an

Re: [tor-dev] Request for comments: patch to mark exit traffic for routing and statistical analysis

2016-10-20 Thread René Mayrhofer
Hi everybody, Michael Sonntag has extended the patch below to make it configurable and tested it on a separate instance here in Linz. Seems to work for our use case. If that seems a good option, then we'd like to request review for upstream inclusion. -

Re: [tor-dev] Request for comments: patch to mark exit traffic for routing and statistical analysis

2016-09-26 Thread René Mayrhofer
>>> That is exactly what we have patched our local Tor node to do, although >>> with a different (slightly hacky, so the patch will be an RFC type) >>> approach by marking real exit traffic with a ToS flag to leave the >>> decision of what to do with it to the next layer (in our setup Linux >>> ke

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 clie

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

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

2016-09-19 Thread René Mayrhofer
explicitly setting Address? Thanks, Rene On 2016-09-19 15:14, René Mayrhofer wrote: > 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

[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