nnections, or the new connection
rate, from an entire address block.
T
--
teor
--
signature.asc
Description: Message signed with OpenPGP
___
tor-relays mailing list
tor-relays@lists
Hi,
> On 17 Aug 2019, at 18:11, Toralf Förster wrote:
>
> Signed PGP part
> On 7/26/19 4:18 PM, Rob Jansen wrote:
>> I am planning on performing an experiment on the Tor network to try to gauge
>> the accuracy of the advertised bandwidths that relays report in their server
>> descriptors.
>
Hi,
> On 14 Aug 2019, at 22:50, contact-tor-tur...@g0b.eu wrote:
>
> hello, I managed until now the relay tor-turing -
> 8456DFA94161CDD99E480C2A2992C366C6564410 - ip 62.210.254.132 for four years
> and it was in the list of Fallback Directory. However he did not answer for 2
> weeks, the
Hi,
We didn't clear the moderation queue last week, and this message was
dropped from the queue.
We'll make sure someone is looking at the queue every 1-3 days in
future.
T
Begin forwarded message:
>> On Mon, Aug 12, 2019 at 09:02:58PM +0200, li...@for-privacy.net wrote:
>>> On 12.08.2019
Hi,
> On 14 Aug 2019, at 03:42, NOC wrote:
>
>> On 12.08.2019 23:39, teor wrote:
>>
>> On 13 Aug 2019, at 05:08, Roman Mamedov wrote:
>>
>>> On Mon, 12 Aug 2019 00:46:50 +
>>> Christopher Sheats wrote:
>>>
>>>> Tor
Hi,
> On 9 Aug 2019, at 23:25, Rob Jansen wrote:
>
>> On Aug 6, 2019, at 5:31 PM, Rob Jansen wrote:
>>
>> Over the last 2 days I tested my speedtest on 4 test relays and verified
>> that it does in fact increase relays' advertised bandwidth on Tor metrics.
>>
>> Today, I started running the
But we're
working on a grant application right now:
On 12 Aug 2019, at 11:54, teor wrote:
>> It is discouraging to see so many small and large network operators not
>> using IPv6. Why is this such a problem?
>
> Tor relays don't automatically detect IPv6 addresses, and th
Hi,
> On 12 Aug 2019, at 07:55, Augusto Cezar Amaral wrote:
>
> I'll need to shut down relay KrigHaBandolo
> (46791D156C9B6C255C2665D4D8393EC7DBAA7798).
>
> Can someone here help me with removing it from the fallback directory
> mirror list?
Thanks for letting us know.
We'll do a rebuild
Hi Rob,
> On 8 Aug 2019, at 22:15, Rob Jansen wrote:
>
>> On Aug 6, 2019, at 5:48 PM, Roger Dingledine wrote:
>>
>> On Tue, Aug 06, 2019 at 05:31:39PM -0400, Rob Jansen wrote:
>>> Today, I started running the speedtest on all relays in the network. So
>>> far, I have finished about 100
Hi niftybunny, Mitar,
> On 7 Aug 2019, at 17:37, niftybunny
> wrote:
>
> Thats complete and utter bullshit.
After thinking about it for a while, I have allowed this email through
moderation.
I considered rejecting it, because this thread is getting repetitive.
And it seems like you're
Hi,
> On 6 Aug 2019, at 20:12, Mitar wrote:
>
> Hi!
>
> I have deployed it:
>
> https://metrics.torproject.org/rs.html#details/567E9785458C605E59202755C74898E3C96FB1CC
>
> On gigabit fiber, using this NUC:
>
>
> On 5 Aug 2019, at 09:10, potlatch wrote:
>
> I have not installed a Tor relay since the gpg server change. I started a
> new relay today and found that the instructions for ubuntu Bionic did not
> work for me. Specifically,
>
> url
>
> On 5 Aug 2019, at 03:28, Toralf Förster wrote:
>
>> On 7/2/19 1:33 PM, teor wrote:
>> Dear Relay Operators,
>>
>> The FallbackDir flags on Consensus Health [2] and Relay Search [3]
>> might take a week or two to update.
>>
>> [3]: For example,
Hi,
We get this question a lot.
> On 4 Aug 2019, at 00:38, Piers wrote:
>
> Hi, i have been running a tor relay (link:
> https://metrics.torproject.org/rs.html#details/858BEC79D7355EC0631E98D47CF14B576BFD6D0F)
> on a raspberry pi 2 for 15 days, however i think there might be a problem
>
Hi,
You must not forward your control port to the internet.
If you accidentally disable control authentication, then
anyone on the internet can control your relay.
> On 3 Aug 2019, at 21:10, Fabio De Sicot wrote:
>
> Hello everyone
> I have a problem I wasn't able to fix until now. Could you
Hi again,
> On 2 Aug 2019, at 08:18, Rob Jansen wrote:
>
>> On Jul 31, 2019, at 7:34 PM, teor wrote:
>>
>> Can you define "goodput"?
>
> Application-level throughput, i.e., bytes transferred in packet payloads but
> not counting packet hea
Hi Matt,
> On 30 Jul 2019, at 21:18, Matt Westfall wrote:
>
> You're right, it went offline for around 2 days due to a power outage and a
> Bios error that needed continue pressed.
>
> That's what the stable flag is for, lol.
>
> I lost guard probability for 2 more weeks.
>
> If a relay has
Hi Rob,
> On 27 Jul 2019, at 00:18, Rob Jansen wrote:
>
> I am planning on performing an experiment on the Tor network to try to gauge
> the accuracy of the advertised bandwidths that relays report in their server
> descriptors. Briefly, the experiment involves running a speed test on every
orrc options:
DoSConnectionEnabled 1
DoSConnectionMaxConcurrentCount 1
DoSConnectionDefenseType 2
If that works, try adjusting DoSConnectionMaxConcurrentCount a bit
higher: 10 or 25 are good values.
T
--
teor
--
signature.asc
le?
T
--
teor
--
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Dear Relay Operators,
Thanks to everyone who opted-in their relays as fallback directory
mirrors.
We rebuilt the list of fallbacks in June 2019. [0] The new list
will be released in Tor 0.4.1.4-alpha/rc. It was backported to all
supported Tor releases. [1]
The FallbackDir flags on Consensus
> On 1 Jul 2019, at 21:41, Tyler Durden wrote:
>
> I can't really understand why our relays should fail so often because
> the logs of our DNS daemon don't show anything and I haven't seen the
> warning about nameservers that failed for a long time...
>
> Maybe the script that checks about DNS
Hi,
> On 1 Jul 2019, at 04:12, tor wrote:
>
> Hi
>
> I've been running an obfs4 bridge for about a month.
>
> My hashed fingerprint is:
> E120A0492F789F5367EAD84C64F92EE279018F98
>
> I recently lost the stable flag. Not sure why.
>
> Any thoughts?
The Stable flag isn't relevant for
Hi,
> On 27 Jun 2019, at 13:56, TorGate wrote:
>
> Hi to all, i have issues with my 3 relays, there is no bandwith ?! i have not
> changed the config only updatet the tor software. In nyx can i see there are
> smal bandwith connections 1-100 kbs.
> All 3 relays have a 5mbit up/down
Hi,
> On 25 Jun 2019, at 18:03, dns1...@riseup.net wrote:
>
> I'm trying to build tor
What version of tor?
> for from source on a x86 Debian stretch machine. I first installed all
> dependencies, but when I launch the "./configure" command I see the following
> error:
>
> configure:
Hi,
> On 25 Jun 2019, at 09:32, Gunnar Wolf wrote:
>
> Signed PGP part
> teor dijo [Sun, Jun 23, 2019 at 02:54:51PM +1000]:
>>> https://metrics.torproject.org/userstats-relay-country.html?start=2017-06-22=2019-06-22=all=off
>>
>> It seems to be a significan
Hi,
> On 24 Jun 2019, at 02:49, tscha...@posteo.de wrote:
>
> On 2019-06-23 14:32, teor wrote:
>
>> But your relay needs a DirPort to be a fallback directory mirror.
>> Here are some instructions for different platforms:
>> https://trac.torproject.org/p
Hi,
> On 23 Jun 2019, at 23:52, Toralf Förster wrote:
>
> Signed PGP part
> On 5/21/19 3:32 PM, gus wrote:
>> [1]
>> https://trac.torproject.org/projects/tor/wiki/doc/FallbackDirectoryMirrors
>
> contgains outdated links
>
>> [3]
>>
Hi jajtor,
> On 16 Jun 2019, at 03:07, TOR wrote:
>
> On 21/05/19, gus wrote:
>> Dear Relay Operators,
>>
>> Do you want your relay to be a Tor fallback directory mirror?
>> Will it have the same address and port for the next 2 years?
>> Just reply to this email with your relay's fingerprint.
Hi Nikos,
> On 7 Jun 2019, at 20:05, Nikos Roussos wrote:
>
> On 21/05/19, gus wrote:
>> Dear Relay Operators,
>>
>> Do you want your relay to be a Tor fallback directory mirror?
>> Will it have the same address and port for the next 2 years?
>> Just reply to this email with your relay's
Hi Marek,
> On 23 Jun 2019, at 22:28, teor wrote:
>
>>> Il 21 maggio 2019 15:32:57 CEST, gus ha scritto:
>>> Dear Relay Operators,
>>>
>>> Do you want your relay to be a Tor fallback directory mirror?
>>> Will it have the same ad
Hi Kushal,
> On 7 Jun 2019, at 00:31, Kushal Das wrote:
>
> On 21/05/19, gus wrote:
>> Dear Relay Operators,
>>
>> Do you want your relay to be a Tor fallback directory mirror?
>> Will it have the same address and port for the next 2 years?
>> Just reply to this email with your relay's
Hi,
>> Il 21 maggio 2019 15:32:57 CEST, gus ha scritto:
>> Dear Relay Operators,
>>
>> Do you want your relay to be a Tor fallback directory mirror?
>> Will it have the same address and port for the next 2 years?
>> Just reply to this email with your relay's fingerprint.
> On 7 Jun 2019, at
Hi,
>> Il 21 maggio 2019 15:32:57 CEST, gus ha scritto:
>> Dear Relay Operators,
>>
>> Do you want your relay to be a Tor fallback directory mirror?
>> Will it have the same address and port for the next 2 years?
>> Just reply to this email with your relay's fingerprint.
>
> On 22 May 2019, at
Hi,
> On 22 Jun 2019, at 17:23, starlight.201...@binnacle.cx wrote:
>
> https://metrics.torproject.org/userstats-relay-country.html?start=2017-06-22=2019-06-22=all=off
It seems to be a significant increase in users all over Iran:
https://trac.torproject.org/projects/tor/ticket/30636#comment:8
Hi,
> On 20 Jun 2019, at 07:28, Yggdrasil Admin wrote:
>
> Hi at all.
> Yesterday i was kicked by my hosting provider urdn (https://urdn.com.ua)
> kicked me because "someone we can't name here, wasn't happy" about what i did
> on a non urdn server. That's why they nullrouted my ipv4 and made
Hi,
> On 20 Jun 2019, at 01:20, Peter Ludikovsky wrote:
>
> Does the official Tor Project repo provide upgrades to the new 0.4.0.5
> stable for anyone? I can see the new packages in pool/main/t/tor/, but
> the package index in dists/stretch/main/binary-amd64/Packages still
> points to 0.3.5.8.
Hi,
> On 19 Jun 2019, at 05:56, tscha...@posteo.de wrote:
>
> I have enabled IPv6 on my Relay [1] and setup a new one [2].
> Both got the additional Flag 'ReachableIPv6' - fine.
>
> In the 'IPv6 HOWTO' [3] I found:
>
> "Since clients only use the ORPort (because it's more anonymous2), and
>
Hi,
> On 15 Jun 2019, at 02:14, to...@protonmail.com wrote:
>
> Would tor show something in its log if I were hitting my router's limit?
> Seeing nothing there or in my router's gui log interface, but not sure what I
> should expect to see.
It's hard for tor to work out the difference
Hi,
> On 2 Jun 2019, at 16:57, Matt Westfall wrote:
>
> Hey toer, I actually removed the Bandwidth Rates per another suggestion.
You might need to wait a week or two for the new setting to increase your
bandwidth. It takes a few days for the bandwidth authorities to measure
the whole network.
Hi,
> On 2 Jun 2019, at 15:14, Conrad Rockenhaus wrote:
>
> Onionoo returns “unknown” for my ASN for some reason (should return 63080)
> and returns “unknown” for AS Name (Should be GreyPony Consultants - as named
> in ARIN). I’m trying to find out where things might be potentially breaking
Hi,
> On 1 Jun 2019, at 14:57, Matt Westfall wrote:
>
> Hello thanks for the comments, I might do that, remove the limits, because
> it's self limiting by the 1 Gbps network port, so it can't use more than that
> anyway.
Following the instructions here:
> On 31 May 2019, at 10:34, Keifer Bly wrote:
>
> Upon trying to open that folder, I got this.
>
> var/log/unattended-upgrades: No such file or directory
Try a leading slash:
/var/log/unattended-upgrades
T
___
tor-relays mailing list
Hi,
> On 25 May 2019, at 01:13, Matt Westfall wrote:
>
> My tor node:
> https://metrics.torproject.org/rs.html#details/B1B10104EB72A1FBBF6687B05F1915D87D00DBDE
>
> Doesn't ever go up above 8800 or so.
>
> One thing I notice in Nyx is that my connections never go above about 2000 in
> and
Hi,
> On 28 May 2019, at 06:18, Keifer Bly wrote:
>
> So I am now auto upgrading tor using the method at
> https://trac.torproject.org/projects/tor/wiki/TorRelayGuide/DebianUbuntuUpdates
>
>
> Upon testing, this is what I got.
>
> …
>
> No packages found that can be upgraded unattended
Hi,
> On 24 May 2019, at 11:41, Keifer Bly wrote:
>
> Hi all, so I believe I found the problem. In my torrc file, there was a rogue
> line which read "PublishServerDescriptor" with nothing after it. I removed
> this line and restarted the relay, now it is saying "May 24 01:38:16.000
>
Hi,
> On 24 May 2019, at 14:08, Conrad Rockenhaus wrote:
>
> In April 2018 Google released an update that caused VPNs and Tor services to
> stop working on GCE and App Engine. It was a long planned network update.
>
> The following ticket refers:
>
or Ubuntu, please follow these instructions
to update:
https://2019.www.torproject.org/docs/debian.html.en
> The relay has an assigned static ip and port which are both allowed by the
> firewall. It seems strange that
> Dmitrii Tcvetkov was able to reach the relay though teor cannot,
We
Hi,
> On 23 May 2019, at 18:41, Dmitrii Tcvetkov wrote:
>
> On Tue, 21 May 2019 23:36:28 -0700
> Keifer Bly wrote:
>
>> Hi, so the relay in question does indeed have a reserved Static IP
>> (104.154.93.253), and the traffic is allowed by the firewall, but the
>> relay is still not appearing
Hi,
> On 22 May 2019, at 16:24, tor-re...@riseup.net wrote:
>
> Do you think would be feasible to use SSH to forward all connections, except
> DNS queries, between my Lime2 and the remote VM in order to use an additional
> VM's IP?
I just wanted to highlight the DNS queries from your home
Hi,
> On 21 May 2019, at 16:11, Keifer Bly wrote:
>
> Hi all, something very strange is going on with my relay called torworld.
This looks like the same question as your previous thread:
https://lists.torproject.org/pipermail/tor-relays/2019-May/017317.html
Did you assign a static address to
Hi,
> On 19 Apr 2019, at 07:41, Charly Ghislain wrote:
>
> I feel there is an issue in case the operator advertises an unreachable ip6
> address in the config. This seems like a configuration error that should be
> spotted by a self-reachability mechanism that is yet to come, like for ipv4.
>> On 8 Apr 2019, at 07:57, teor wrote:
>>
>>> The reason I ask is that I wonder if I should run a second Tor instance or
>>> if the current one will be able to make use a a reasonable part of the
>>> 500Mps.
>>
>> It looks like your relay
One more thing:
> On 8 Apr 2019, at 07:57, teor wrote:
>
> Hi,
>
>> On 7 Apr 2019, at 05:19, Logforme wrote:
>>
>> I run the non-exit relay:
>> https://metrics.torproject.org/rs.html#details/855BC2DABE24C861CD887DB9B2E950424B49FC34
>> The relay
Hi,
> On 7 Apr 2019, at 05:19, Logforme wrote:
>
> I run the non-exit relay:
> https://metrics.torproject.org/rs.html#details/855BC2DABE24C861CD887DB9B2E950424B49FC34
> The relay run on a debian stretch machine with an i5-4670 at 3.8GHz with 4GB
> memory. CPU usage at 250Mbps traffic is
Hi Ben,
> On 4 Apr 2019, at 10:58, Ben Riley wrote:
>
> I've read over a couple of other threads regarding relays being slow,
> however, I can't figure out why mine is running as slow as it is.
Have you read our wiki page about slow relays?
Hi,
> On 12 Mar 2019, at 05:34, ylms wrote:
>
>> On 3/9/19 5:07 AM, teor wrote:
>> ORPort [IPv6]:Port
>>
>> For example:
>>
>> ORPort [2001:db8::1]:9001
>>
>> Tor doesn't guess IPv6 addresses yet.
>
> That was very helpful to fin
Hi,
> On 10 Mar 2019, at 08:56, digitalist00 wrote:
>
> Sorry, germin because of your torrc-example:
> I added MaxMemInQueues 1024 MB
> LimitNOFile 5000 doesn't work, neither does LimitNOFILE = 5000 and I deleted
> it.
> Nyx didn't start anymore and then I first had to "chown ".
> Tor is
Hi,
> On 9 Mar 2019, at 14:04, teor wrote:
>
> It's probably a bug in the scaling in the dev version of sbws
It is a kilobyte-to-byte scaling bug:
https://trac.torproject.org/projects/tor/ticket/29707
> No need to stress. Medians are designed to ignore outlying values like this.
Hi,
> On 9 Mar 2019, at 13:08, Roger Dingledine wrote:
>
>> I also have some questions.
>>
>> Atlas does not show any IPv6 address, is this normal?
>
> I see that you have an ipv6 exit policy set, but I don't see any
> ipv6 address in your relay descriptor.
>
> (You can see your relay
> On 9 Mar 2019, at 13:36, starlight.201...@binnacle.cx wrote:
>
> Anyone know what caused bastet's loss of grip on reality?
>
>
> 600 IPredator
> 440 xenoidRelay
> 300 PrivacyRepublic0001
> 270 ExitNinja
> 260 DipulseIT2
> 240 hyacinthinus
> 230 PIAzrhexit
> 230 Unnamed
> 220 volatile
> 210
> On 1 Mar 2019, at 10:26, s7r wrote:
>
> teor wrote:
>>
>>
>> Cc'ing Linus, because he is also interested in IPv6.
>>
>> On 28 Feb 2019, at 19:01, s7r mailto:s...@sky-ip.org>>
>> wrote:
>>>
>>> However, shouldn't the line
Hi,
Cc'ing Linus, because he is also interested in IPv6.
> On 28 Feb 2019, at 19:01, s7r wrote:
>
> However, shouldn't the line:
> ORPort 9050
>
> bind to all v4 and v6 available interfaces / IP addresses? If it does
> not, we should fix it to do so. As in:
>
> ORPort 9050 - bind to all
Hi,
> On 28 Feb 2019, at 09:57, technon...@fea.st wrote:
>
> I run one relay and another tor instance for hidden services and socksport.
> Haven't had a problem until 0.4.0.2_alpha. Ive had it crash twice so far.
> Maybe my configs aren't sane?
>
> [err] descriptor at 0x8a0acdb0830 begins
you mean: is xx the wrong address?
If you're still having trouble, please send us your latest config, and address
and reachability check logs. Unredacted logs are best (relay info is public),
but if you must redact, please
s don't vote for the Named flag any more, because relying on
names to identify relays is fragile.
I'm not sure if we have removed the special handling code for Named yet.
T
--
teor
--
___
lf if you search Microsoft's website for
the format reference.
Here is our downloads page with our available downloads:
https://www.torproject.org/download/download.html
T
--
teor
--
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
u work out how to do it, please write back to the list with the scripts
you used.
T
--
teor
--
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
s.
If you can't get it to work, write back to us with a link to the steps you
tried, and links to a paste of your Tor logs and controller session.
Or just restart the bridge.
T
--
teor
--
ency?
Try
MaxMemInQueues 4 GB
If that doesn't work, try
NumCPUs 2
and please let us know, because we'd like to fix these kinds of bugs.
T
--
teor
--
___
tor-relays mailing list
tor-relay
quot; or
>something similar.
You have 3 ContactInfo lines. You can delete 2 of them.
Bridge contact info is not shown on relay search for privacy reasons. The IP
addresses and ports are also hidden.
T
--
teor
--
or clients so
they work even when most of the fallbacks are down. We regularly monitor the
list of fallbacks, and start a rebuild when 25% go down.
T
Hi Michael,
--
teor
--
___
upported connections in Netgear's documentation:
https://www.netgear.com/Orbi/CBR40.aspx
T
--
teor
--
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> On 15 Jan 2019, at 13:09, Isaac Grover, Aileron I.T.
> wrote:
>
> I haven’t ever taken the time to configure bandwidth limits in torrc, always
> preferring to manage it at the firewall as we have other bandwidth limits set
> there as well. However, I’m curious - what do other relay
Hi,
> On 14 Jan 2019, at 11:37, Vasilis wrote:
>
> Signed PGP part
> teor:
>> Colin also asked relay operators to opt-in as fallback directory mirrors
>> (in the last half of 2018). In December, he helped rebuild the fallback
>> directory mirror li
:
https://metrics.torproject.org/rs.html#details/0C039F35C2E40DCB71CD8A07E97C7FD7787D42D6
[4]:
https://trac.torproject.org/projects/tor/ticket/28794
T
--
teor
--
signature.asc
Description: Message signed with OpenPGP
> On 14 Jan 2019, at 09:32, ronqtorrel...@risley.net wrote:
>
> Thanks. I'm curious what, in the consensus, suggests that I'm too far from
> the Authority Servers? I don't know how to read that page; I can't even
> figure out what units they're using to report bandwidth.
It's a unitless
Hi,
> On 12 Jan 2019, at 01:44, Ilka Schulz wrote:
>
> Is there actually any detailed documentation on how consensus weight is
> calculated?
Consensus weight is calculated using a relay's self-reported peak bandwidth
usage, and measurements from ~6 bandwidth authorities around the world.
The
> On 12 Jan 2019, at 21:54, nusenu wrote:
>
> Forwarded Message
> Subject: [tor-project] community team highlights -- November and December
> Date: Wed, 09 Jan 2019 18:15:00 +
> From: Alison Macrina
> To: tor-proj...@lists.torproject.org
>
> Relay Advocacy
>
> On 26 Dec 2018, at 07:11, Darek Kramin wrote:
>
> Looks problem is solved. Online now
>
> On Tue, Dec 25, 2018, 21:13 Darek Kramin hi,
>
> I did started 2 days ago tor relay. when I set daily accounting was ok and
> now with weekly set of GB relay is listed down. It is a glitch or my
>
Hi,
> On 31 Dec 2018, at 20:52, Viktor Nikolov wrote:
>
> Hi!
>
> My Fallback Directory Mirror B6904ADD4C0D10CDA7179E051962350A69A63243 at
> 81.2.209.10 is going down permanently because my provider decommissioned the
> data center where I had my HW. :-(
>
> I will likely host my HW at a
> On 16 Dec 2018, at 17:01, starlight.201...@binnacle.cx wrote:
>
> The cause is
>
> https://gitweb.torproject.org/tor.git/commit/?id=78e177d622f5f3b24023d04458f5948275a44766
>
> https://trac.torproject.org/projects/tor/ticket/24803
>
> Would be appreciated if the Tor project published
Hi,
> On 4 Dec 2018, at 21:27, tscha...@posteo.de wrote:
>
> Hi all!
>
> I wonder who is permanently connecting/checking(?) my Tor bridge relay.
> The ip is 66.111.2.129 and the period of the connects are 21 min 21 sec,
> e.g.:
>
> Dec 4 10:32:00 SRC=66.111.2.129
> Dec 4 10:53:21
> On 5 Dec 2018, at 00:20, Charly Ghislain wrote:
>
> I am also questioning myself whether addresses should be printed in log files
> altogether. Maybe even with the unsafe flag on - at least for released
> versions. If one wants to know which ip is connecting to her bridge, she can
> use
Hi,
> On 29 Nov 2018, at 07:29, dluga...@protonmail.com wrote:
>
> today I have found this. If You need more informations please let me know.
>
>
> 16:48:56 [WARN] {BUG} Bug: 0x1076f25 <_start+0xa5> at /usr/local/bin/tor (on
> Tor 0.3.4.9 4ac3ccf2863b86e7)
> │ 16:48:56 [WARN] {BUG} Bug:
Hi,
Just one clarification:
> On 28 Nov 2018, at 22:23, s7r wrote:
>
> You say you want to run a middle relay, why do you want to run it behind
> a VPN in this case? Middle relays get no abuse complaints or anything as
> they can not be used as exit points.
Occasionally, clients will ask
Hi,
> On 28 Nov 2018, at 14:10, Keifer Bly wrote:
>
> Hello, so today when I started my bridge relay, tor popped up with a warning
> saying this
>
> WARNING: According to directory authorities, this version of tor [0.3.4.8] is
> out of date or no longer recommended.
>
> I am running the
Hi,
Thanks for reporting this bug.
> On 28 Nov 2018, at 04:10, dluga...@protonmail.com wrote:
>
> does any could tell me what is mean that Warn ?
>
> 16:32:33 [WARN] {BUG} Bug: 0x1076f25 <_start+0xa5> at /usr/local/bin/tor (on
> Tor 0.3.4.9 4ec3ccf2863b86e7)
> │ 16:32:33 [WARN] {BUG} Bug:
Hi,
> On 24 Nov 2018, at 05:46, Keifer Bly wrote:
>
> Hello, So I am running an obfscated bridge on Windows 10 via the tor expert
> bundle, which, even when I tried downloading it today, is running tor
> 0.3.4.8. I was unaware that tor 0.3.4.9 had been released due to this. Do to
> being
> On 23 Nov 2018, at 21:20, petra...@protonmail.ch wrote:
>
> Hi,
> on a small server I did try to force local DNS requests to the local Tor via
> iptables/ferm (Nat, Output-Chain, protocol udp dport domain REDIRECT to-ports
> 5300). Torrc has the following included: 'DNSPort 127.0.0.1:5300'.
> On 16 Nov 2018, at 06:22, Keifer Bly wrote:
>
> But is it normal for the fast flag to be off and on? Thank you.
Yes. Change is normal.
Embrace change. Do not worry.
T
___
tor-relays mailing list
tor-relays@lists.torproject.org
Hi,
>> On 14 Nov 2018, at 07:11, entensai...@use.startmail.com wrote:
>>
>> Hello List, my bridge relay at
>> https://metrics.torproject.org/rs.html#details/148BD64BED9F2C27637D986DE032ECF14E5B9E9A
>>
>> Is reporting the relay speed is between 50 kb/s and 60 kb/s, when the speed
>> of the
On 12 Nov 2018, at 08:40, DeMarcus Sullivan wrote:
>
> I am running the latest version on Tor 8.0.3 on my Windows desktop. I would
> like to run a non-exit relay 24/7 and I'm having trouble finding the
> step-by-step process to do so. Before I could just copy amd paste the torrc
>
> On 9 Nov 2018, at 20:18, nusenu wrote:
>
> teor:
>> 1. If your exit's DNS fails, it will reject all exit requests in its
>> descriptor.
>
> are you saying that
> https://trac.torproject.org/projects/tor/ticket/21989
> is already implemented and released
Hi,
There are two likely possibilities here:
> On 9 Nov 2018, at 06:17, Toralf Förster wrote:
>
> Signed PGP part
> On 11/8/18 9:12 PM, nusenu wrote:
>>> 2018-11-06 21:00 UTC
>> are you sure this is UTC?
>>
> ick, it was 21:00 CET (the dropdown may even started at 20:00 CET), but
> obvious
> On 31 Oct 2018, at 22:47, Ralph Seichter wrote:
>
> * teor:
>
>> If a client doesn't have a circuit to an exit that supports the port
>> it wants, it randomly chooses an exit that allows that port.
>
> Sure, but is the distinction of what is considered "an
> On 31 Oct 2018, at 16:41, DaKnOb wrote:
>
> You can exit to one of (80,443) to at least a /8 to receive it.. So if you
> add an allow 443 on a not so populated /8, it will get the exit flag.. :-)
Careful:
* this isn't a great experience for users who use your exit, and
* getting the Exit
> On 31 Oct 2018, at 01:53, Ralph Seichter wrote:
>
> * Isaac Grover:
>
>> You are correct in that I won't maintain the exit flag without ports
>> 80 and 443 open, *and* I lose my eligibility for a free t-shirt, *but*
>> I am not likely to attract attention at my home either. =)
>
> No exit
Hi,
Thanks for reporting this bug.
> On 30 Oct 2018, at 04:18, Felix wrote:
>
> Are the two warnings below of the same type for this issue?
Not really: they're corrupt on disk, rather than from the network.
> Am 29.10.2018 um 07:03 schrieb teor:
>>
>>
>>>
Hi Toralf,
Thanks for reporting this issue.
> On 24 Oct 2018, at 07:38, Toralf Förster wrote:
>
> Get this at my exit relay since yesterday:
>
> # head /tmp/warn.log
> Oct 23 23:30:17.000 [notice] Tor 0.3.5.3-alpha opening new log file.
> Oct 23 23:30:33.000 [warn] parse error: internal NUL
101 - 200 of 995 matches
Mail list logo
