u used to participate in the `tor-relays` mailing list.
Frank
May 30, 2024, 11:23 PM by tor-relays@lists.torproject.org:
> Greetings everyone!
>
> Almost three months ago I have set up my first node. Everything seemed to be
> going great at first and as documented in the tor lifecycle blog post.
Keep the same Tor identity keys.
Frank
Jun 4, 2024, 9:56 AM by tor-relays@lists.torproject.org:
> Hello everyone.
> I have to move somewhere else a a (middle) relay I have been running for a few
> years. It will be down for 2-4 weeks, then be back online in a different
&
All:
Does anyone here know the procedure of the
router_do_orport_reachability_checks() function?
I've increased logging of my Tor Relay to info and taken several
packet-captures, but can't seem to identify connections initiated by my Tor
Relay when verifying my ORPort reachability. I just see
All:
After enabling Tor debug logging, we were able to verify the procedure of the
router_do_orport_reachability_checks() function.
The router_do_orport_reachability_checks() function creates a circuit using a
random Guard and Middle Relay with the Exit Relay always being itself.
This can
Hi All!
Curious... What are the magic numbers (i.e., max timeout, reoccurrence, etc)
that earn a relay overloaded status?
I'm trying to tune my portion of the Tor network and finding that sweet spot
has proven elusive.
Thanks!
Gary
On Friday, September 24, 2021, 3:48:18 AM MDT, Silvia
becoming an exit? If not, I would
appreciate any help you can give.
thank you very much___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
.
iBigBlue 63W Solar Array (~12 Hour Charge)
+ 2 x Charmast 26800mAh Power Banks
= iPhone XS Max 512GB (~2 Weeks Charged)
On Thursday, October 14, 2021, 5:10:53 AM PDT, Bleedangel Tor Admin
wrote:
You are running 0.4.5.8, maybe updating to a newer version of tor will help?
Sent from
Keifer,
When you say, "periodically go down once a month" do you mean the Tor service
dies, becomes defunct, circuits bleed off, Internet connectivity issues, power
goes out, etc? Anything in the torlog that might provide a clue? From your
metrics, you can definitely tell your relay
All:
Are the DirectoryAuthority & FallbackDir directives only evaluated at startup
of a Tor instance? I recently ran into an issue where my Tor Relay Farm went
down, due to the manually configured DirectoryAuthority going down and the
FallbackDir didn't seem to back it up.
I
David,
This is exactly the type of information I was hoping for. You should make this
an article and link it to the overloaded support page.
I guess I assumed that Tor preformed external timeout monitoring apposed to
relay reported resource monitoring.
It's interesting that you mention
, October 6, 2021, 12:48:31 AM PDT, Bleedangel Tor Admin
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
This is much more informational. Great job!
As someone with mystery "overloaded" problems, i'd recommend / request / beg
for the following:
1) When the relay is overloaded
David Goulet:
Will you confirm whether the Advertised Bandwidth metric is also client
initiated (I'm assuming to the Directory Authority)?
I have a 250Mb pipe and have seen a maximum Advertised Bandwidth rate of 4MB/s
with my Tor relay. I know resource constraint must be factored
Georg,
Thank you for the reference that confirms the Advertised Bandwidth is from the
Tor client.
I still don't understand why my Tor nodes aren't able to initiate a 10 second
burst higher than 4MB/s. An Internet Speed Test is able to sustain a burst near
my advertised 250Mb/s up and down.
Am
, 2:33:23 PM MDT, Silvia/Hiro
wrote:
On 10/4/21 1:36 PM, David Goulet wrote:
> On 02 Oct (01:29:56), torix via tor-relays wrote:
>> My relays (Aramis) marked overloaded don't make any sense either. Two of
>> the ones marked with orange are the two with the lowest traffic I hav
George,
The referenced support article provides recommendations as to what might be
causing the overloaded state, but it doesn't provide the metric(s) for how Tor
decides whether a relay is overloaded. I'm trying to ascertain the later.
I would assume the overloaded state metric(S
server and extra-info descriptors. If you
download the server one you would be able to verify that there is a
"overload-general" field in there. If there isn't we have a bug :).
Please let me know if this happens again.
Cheers,
-hiro
On 9/24/21 2:39 PM, friendlyexitnode via tor-relays wr
Roger,
For completeness, I should amend point #3 to include configuring the
Loadbalancer's Timeout to a Large Value:
3. Loadbalance using IP Transparency Mode (This was discovered while tirelessly
combing through mountains of Tor debug logs), use Sticky Sessions based on
Source IP Addresses
by the garlic routers
themselves?
My thoughts are... What if the Tor Network distributed encrypted
fingerprint-to-host databases to browsers/bridges/relays during the bootstrap
process, with Directory Authorities, that operators did not have access? Such a
process could be further segmented, so
David/Roger:
Search the tor-relay mail archive for my previous responses on loadbalancing
Tor Relays, which I've been successfully doing for the past 6 months with Nginx
(it's possible to do with HAProxy as well). I haven't had time to implement it
with a Tor Bridge, but I assume
Neel,
I get the security vs usability considerations between centralized vs
decentralized (or in the case of Tor semi-decentralized) networks. However, at
a minimum, doesn't it make sense to exclude publishing address information from
Tor metrics, etc, as to stop giving censorship organizations
I know it might be a fundamental change to the Tor network, but would it be
possible to obfuscate the Tor bridge/relay addresses with their respective
fingerprints; similar, to the I2P network? I've often thought that this aspect
of the I2P network is one that is implemented well. Perhaps
BTW... I just fact-checked my post-script and the cpu affinity configuration I
was thinking of is for Nginx (not Tor). Tor should consider adding a cpu
affinity configuration option. What happens if you configure additional Tor
instances on the same machine (my Tor instances are on different
Hi Kristian,
Thanks for the screenshot. Nice Machine! Not everyone is as fortunate as you
when it comes to resources for their Tor deployments. While a cpu affinity
option isn't high on the priority list, as you point out, many operating
systems do a decent job of load management
Gus,
I have to agree with z-relay on these points.
I won't even provide an obfuscated contact email in my torrc to avoid spam. I
could setup a dedicated email for Tor operation, but I'd likely find my relays
down prior to checking it.
Case in point... When registering a domain name, I've gotten
The following are some of the more important config options that I use for such
a small middle relay:
# Tor: A non-exit relay should be able to handle 7000 concurrent connections
ulimit -n 65535
DirCache 0
Bobby,
I run a Tor relay on dual core 256MB devices with a 250Gb fiber connection and
they are adequate to operate as a fast middle relay.
Monitor your relay on https://metrics.torproject.org/ to verify.
Respectfully,
Gary—
This Message Originated by the Sun.
iBigBlue 63W Solar Array (~12
David Goulet or Georg Koppen:
Can either of you confirm my question regarding whether the DirectoryAuthority
& FallbackDir directives only evaluated at startup of a Tor instance?
I need to verify the best way to configure cloned, loadbalanced Tor Relay
Instances to inter
It's surprising that you're running into CPU issues. It's typically RAM that is
exhausted first.
I have 5 x Dual Core 256MB Tor Relay Nodes loadbalanced as a Single Middle
Relay that never have CPU issues. It's always a matter of running out of RAM
for me. The loadbalanced Tor Relay
On Sunday, December 12, 2021, 1:32:09 AM PST, Natus wrote:
>> As for finding out if anyone is using it or not, I use:
>> netstat -n |grep ESTA|wc -l
>This one does not limit to tor bridge
Pipe the bridge's destination port (i.e., ) through grep as well:
netstat -anp | grep :
Welcome to tor-relays, Kristian. It's nice to meet a fellow Tor Farmer. It
sounds like you are fairly seasoned with quite an extensive deployment of Tor
Relays.
Are you performing any loadbalancing with Tor Nodes or are they Individually,
Distributed Tor Relays?
I have a Single Tor Relay
> What part do you intent to load-balance and to what outcome?
My current implementation is loadbalancing Tor Relay traffic, which provides
high availability and economies of scale using existing, cost-effective, bare
metal nodes. The same approach could be extrapolated to cost-effect
Hi Roger,
I've found the secret to effectively loadbalancing Tor Relay Nodes is as
follows:
1. Use the same version of Tor on all Upstream Servers
2. Start/Stop all Upstream Tor Nodes at the same time to keep in sync
3. Loadbalance using IP Transparency Mode (This was discovered while tirelessly
Are you able to start Tor manually without systemd? Anytime I encounter Tor
start issues, I attempt to manually start Tor without the --quiet option to
verify whether it's a torrc issue or something else. You might consider
increasing the Tor logging level, too. Your existing Tor log shows
ctfully,
Gary
On Wednesday, December 29, 2021, 03:32:55 AM MST, abuse--- via tor-relays
wrote:
Hi Gary,
thanks!
> As an aside... Presently, are you using a single, public address with many
> ports or many, public addresses with a single port for your Tor deployments?
> Have you
David, Roger, et al.,
I just got back from holidays and really enjoyed this thread!
I run my Loadbalanced Tor Relay as a Guard/Middle Relay, very similar to
David's topology diagram, without the Snoflake-Server proxy. I'm using Nginx
(which forks a child process per core) instead of HAProxy
Fellow Tor Operators:
After about 9 months of running Tor as a Middle Relay from my home network, I'm
beginning to experience signs of my public semi-static IPv4 address being
blacklisted with 403 Forbidden errors from Reuters and Venmo. I've confirmed by
successfully accessing both sites
Hi all,
In the effort of deploying obfs4 bridges for the community we are sharing our
Ansible role that allowed us to deploy multiple nodes:
https://github.com/NewNewYorkBridges/ansible-tor-bridge
For now it is only available on Debian but we will make it available for other
distributions
to implement an On-Shore
configuration for Tor Blacklisted Sites. My only concern is latency, with this
type of configuration, but it's better than the current forbidden situation.
I appreciate the heads-up related to Tor and IPv6-only being a non-starter. It
sounds like if I were to migrate
Georg,
>> Are there any "Issues" submitted for a similar change to Concensus Weight
>> and Relay Probability to Tor Metrics on Onionoo? It appears these values are
>> still only being reported for a Single Tor Node.
> Hrm, good question. I don't think so an
David,
I see that the metrics change has been reverted.
If/When the metrics change is implemented, will loadbalanced Tor Relay Nodes
need to be uniquely named or will they all be able to use the same nickname?
I'm glad to hear your loadbalanced Snowflake Relay continues to work well.
Thanks
David,
> When I made my own combined graphs, I relied on different instances
having different nicknames. I don't know an easy way to distinguish the
descriptors of different instances otherwise.
Please let me know what the Tor Metrics Team decides, if/when they reimplement
the change.
&g
Toralf,
It's to allow a Tor Relay to continue to build on an established reputation and
avoid the ramp-up cycle of a new Tor Relay.
Respectfully,
Gary—
This Message Originated by the Sun.
iBigBlue 63W Solar Array (~12 Hour Charge)
+ 2 x Charmast 26800mAh Power Banks
= iPhone XS Max 512GB (~2
Eddie,
You should be able to copy the donor tor directory (preserving user, group,
permissions) to the transplant server (including keys) and be back online with
the same fingerprint (new ip address).
I recommend using the same version of tor and ensure the transplanted tor
directory's user
, 2:52:30 PM MST, li...@for-privacy.net
wrote:
On Friday, March 11, 2022 9:39:14 PM CET Gary C. New via tor-relays wrote:
> It's to allow a Tor Relay to continue to build on an established reputation
> and avoid the ramp-up cycle of a new Tor Relay. Respectfully,
Bridges don't have a r
David,
Has Tor Metrics implemented your RFC related to Written Bytes per Second and
Read Bytes per Second on Onionoo?
As of the 27th of February, I've noticed a change in reporting that accurately
reflects the aggregate of my Tor Relay Nodes opposed to the previously reported
Single Tor Node
Georg,
Yes! That is precisely it!
Please know that the change appears to be working with my loadbalanced Tor
Relay deployment as well.
Are there any "Issues" submitted for a similar change to Concensus Weight and
Relay Probability to Tor Metrics on Onionoo? It appears these values
Hi,
IMHO, this is not a good idea. Tor relay IPs are public, so they are likely to
be blocked as part of censorship in some countries. This will greatly reduce
the usefulness of the bridge running on the same IP. Running both at the same
time on the same public IP does not add much value
David,
On Thursday, January 27, 2022, 1:03:25 AM MST, David Fifield
wrote:
>> It's nice to see that the Snowflake daemon offers a native configuration
>> option for LimitNOFile. I ran into a similar issue with my initial
>> loadbalanced Tor Relay Nodes that was solve
David,
> Making secret_onion_key and secret_onion_key_ntor read-only does not quite
>work, because tor first renames them to secret_onion_key.old and
>secret_onion_key_ntor.old before writing new files. (Making the *.old files
>read-only does not work either, because the `tor_rena
gt; file over them. It does result in an hourly `BUG` stack trace, but otherwise
>> it seems effective.
>> I did a test with two tor instances. The rot1 instance had the directory
>> hack to prevent onion key rotation. The rot2 had nothing to prevent onion
>> key rotati
Heartbeat reporting?
>> > I don't know if it's wrong, exactly. It's reporting something different
>> > than what ExtORPort is providing. The proximate connections to tor are
>> > indeed all IPv4.
>> I see. Perhaps IPv6 connections are less prolific and require m
David,
Excellent Documentation and References!
I hope the proposed RFC's (auth, key, and metrics) for loadbalanced Tor
topologies are seriously considered and implemented by Tor Core and Tor Metrics.
Great Work!
Respectfully,
Gary—
This Message Originated by the Sun.
iBigBlue 63W Solar Array
512GB (~2 Weeks Charged)___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
63W Solar Array (~12 Hour Charge)
+ 2 x Charmast 26800mAh Power Banks
= iPhone XS Max 512GB (~2 Weeks Charged)
_______
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
artbeat logs. It looks like the load is fairly
>balanced, with each of the four tor instances having sent between 400 and 500
>GB since being started.
Your Heartbeat logs continue to appear to be in good health. When keys are
rotated, the Heartbeat logs will be a key indicator i
On Monday, January 17, 2022, 11:47:11 AM MST, David Fifield
wrote:
> Gary, I was wondering how you are dealing with the changing onion key issue,
>and I suppose it is
>[this](https://forum.torproject.net/t/tor-relays-how-to-reduce-tor-cpu-load-on-a-single-bridge/1483/13):
>
David,
> I'd like to see more of your HAProxy configuration. Do you not have to use
>transparent proxy mode with Snowflake instances as you do with Tor Relay
>instances? I hadn't realized HAProxy had a client timeout. Thank you for that
>tidbit. And thank you for referencing my comm
7:00. You can read about
>it here:
>
>https://bugs.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/40095#note_2772325
It's nice to see that the Snowflake daemon offers a native configuration option
for LimitNOFile. I ran into a similar issue with my initial loadbalance
oking for. Otherwise I would prefer
> a Ryzen like the 5750GE.
>
> Andreas
If you don't already have a QAT device, I would not suggest getting one
specifically for Tor. In particular, Tor doesn't spend very much time
actually doing AES. It's mostly overhead from cell processing, TCP,
small
All:
I'm having an issue with a Tor Node catching signal 7 and exiting in high-load
situations.
T= 1650367869
Tor 0.4.5.8 died: Caught signal 7
/opt/sbin/tor(+0x1af500)[0x2a1af500]
/opt/sbin/tor(hs_intro_received_introduce1+0x0
vigate to.
Thanks,
Alex.
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
y=clock_gettime,
FreeBSD 13.1 has CLOCK_MONOTONIC_COARSE, which it says is an alias of
CLOCK_MONOTONIC_FAST for compatibility with other systems. I suppose Tor
could add #if !defined(CLOCK_MONOTONIC_COARSE) &&
defined(CLOCK_MONOTONIC_FAST) #define CLOCK_MONOTONIC_COARSE
CLOCK_MONOTONIC_FAST, but I'm
wrote:
Have a question about how a server I connect to can tell I am running a
guard/middle relay. All I can think of is that they check the published
list of tor nodes against the IP. Or (maybe, but unlikely) portscan the
IP and probe any open ports to determine the service. Are there any
Hi there,
I currently own a Tor Relay that has been running since 2022-05-24. A day ago
it restarted, which was a bit strange. Recently I found that the Relay has
changed to a Guard Relay, which I am pleased about. I was wondering why the
restart occurred as the VPS Server has been online
:
Hi,
A day or two ago, my Tor exit host, Psychz Networks, has sent me
complaints about my IPs being used to send "spam" despite me having
blocked Port 25 (and 465/587) in the exit policy.
Psychz threatened to block Port 25 even when my exit policy explicitly
blocks 25/465/587.
The
t's closer to 1M circuits open.
> All these circuit creations put a strain on the CPU, sometime pegging it
> at 100% (4 core i5-4670K CPU @ 3.40GHz). Worse, it seems to eat memory.
> Normally the tor process uses about 3GB (out of 8GB) but I have seen it
> quickly shoot up
configuration is set to "none?"
BTW... I have the loadbalanced OBFS4 configuration up and running, and am able
to manually confirm loadbalanced OBFS4 connections are successfull.
nginx => obfs4proxy => tor
I believe it's time to enable a DistributionMethod.
Thank you for the clarifications.
Res
e
> kernel when the port is already bound versus when it is not bound. It's
> not as simple as filling in blanks in a 5-tuple in otherwise identical
> code paths.
> Anyway, it is not true that all connections go to the same (IP, port).
> (There would be no need to use a load balancer
10, 2022, 8:01:15 AM MST, David Fifield
wrote:
On Sat, Dec 10, 2022 at 05:19:43AM +, Gary C. New via tor-relays wrote:
>> I'm in the process of trying to cross-compile snowflake for OpenWRT and
>> Entware. Are there any other dependencies to compile snowflake other than Go?
On Saturday, December 10, 2022, 8:01:15 AM MST, David Fifield
wrote:
On Sat, Dec 10, 2022 at 05:19:43AM +, Gary C. New via tor-relays wrote:
>> I'm in the process of trying to cross-compile snowflake for OpenWRT and
>> Entware. Are there any other dependencies to compile sno
ridges don't require a DistributionMethod as your
> loadbalanced Snowflake configuration is set to "none?"
That's correct. Default bridges are not distributed by rdsys, they are
distributed in the configuration of Tor Browser itself. See
extensions.torlauncher.default
All:
What is the status of Bug #7349 - Obfsbridges should be able to "disable" their
ORPort?
https://bugs.torproject.org/tpo/core/tor/7349
I recently setup a loadbalanced OBFS4 bridge and would prefer not to expose the
ORPort to the World.
I've noticed that some of the tas
On Tuesday, December 13, 2022, 07:35:23 PM MST, David Fifield
wrote:
On Tue, Dec 13, 2022 at 07:29:45PM +, Gary C. New via tor-relays wrote:
>> On Tuesday, December 13, 2022, 10:11:41 AM PST, David Fifield
>> wrote:
>>
>> Am I correct in assuming extor-static-cook
On Friday, December 16, 2022, 8:07:46 AM PST, meskio
wrote:
Quoting Gary C. New via tor-relays (2022-12-10 04:20:48)
>> What is the status of Bug #7349 - Obfsbridges should be able to "disable"
>> their ORPort?
>> https://bugs.torproject.org/tpo/core/
(~12 Hour Charge)
+ 2 x Charmast 26800mAh Power Banks
= iPhone XS Max 512GB (~2 Weeks Charged)___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
nsport names force the
>> corresponding protocol?
> It does force the use of the protocol you specified, or at least it
> should and if it doesn't, that's a bug to report. You can quickly
> check this by connecting to an obfs4 bridge while saying it's obfs3:
> tor won't bootstrap
All:
Please disregard. It was human error.
Failed testing of the HTTPTunnelPort and SocksPort was initially attempted
through Tor Browser (which is not permitted).
The HTTPTunnelPort and SocksPort testing was successful through a normal
browser (i.e., Firefox, Chrome, etc).
In short
On Tuesday, December 13, 2022, 10:11:41 AM PST, David Fifield
wrote:
> The Snowflake proxy is not a pluggable transport. You just > run it as a
> normal command-line program. There is no torrc involved, and the proxy
> does not interact with a tor process at all
David,
I finally have time to migrate my loadbalanced Tor relay to a loadbalanced Tor
obfs4proxy configuration.
In the process, I've been reviewing this thread and was hoping you could help
with one clarification regarding your loadbalanced Tor snowflake configuration?
I noticed that you
On Monday, December 12, 2022, 08:31:43 AM MST, David Fifield
wrote:
On Sun, Dec 11, 2022 at 04:25:06AM +, Gary C. New via tor-relays wrote:
>> I was successfully able to get Snowflake cross-compiled and installed for
>> OpenWRT and Entware as a package.
> Thanks, nice w
All:
I noticed that the obfs2, obfs3, and obfs4 transport names seem to be hardcoded
into tor.
I have been able to configure the torrc to register each of the transports for
multiple ServerTransportListenAddr:
# cat torrc
ORPort xxx.xxx.xxx.xxx:443 NoListen
ORPort 192.168.0.31:9001
Gus,
Is there a preferred Bridge Distribution Mechanism?
Within the last couple of months, I've added several obfs4 bridges (latest
version) to the Tor network, which seem to meet the requested criteria, but
they still don't appear to be receiving traffic.
I originally set the Bridge
ServerTransportListenAddr obfs4 0.0.0.0:8081
ExtOrPort auto
Log notice file /var/log/tor/notices.log
ExitPolicy reject *:*
AccountingMax 50 GB
ContactInfo keiferdodderblyyatgmaildoddercom
Strangely, nothing whatsoever is being written to the notices.log file, upon
checking it it is completely empty, nothing there. I
ke any relay.
>> You don't have a stable flag yet either.So just let it run for a week
>> and just watch it.
>>
>>
>> Sandro
>>
>>
>>
>> Am 06.04.23 um 11:50 schrieb Linux-Hus Oni via tor-relays:
>>> Hi to all, i have setup a n
> Nickname gbridge
> ORPort 8080
> SocksPort 0
> BridgeRelay 1
> PublishServerDescriptor bridge
> BridgeDistribution email
> ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy
> ServerTransportListenAddr obfs4 0.0.0.0:8081
> ExtOrPort auto
> Log notice f
Hi to all, i have setup a new tor exit relay with name TorGate, but there are
only a few kb trafic on this?
the flags are exit,running,v2dir,valid and its also messured.
there are no warns or errors in the tor console
any ideas why?
regards Lin
signature.asc
Description: Message signed
On Monday, July 31, 2023, 2:11:52 PM MDT, li...@for-privacy.net
wrote:
> On Montag, 31. Juli 2023 00:55:15 CEST Gary C. New via tor-relays wrote:
> > On Sunday, July 30, 2023, 3:30:55 PM MDT, li...@for-privacy.net wrote:
> > > I don't know if I should ignore that o
On Wednesday, August 2, 2023, 10:09:06 AM MDT, meskio
wrote:
> Quoting li...@for-privacy.net (2023-08-02 17:13:53)
> > On Dienstag, 1. August 2023 23:22:12 CEST Gary C. New via tor-relays wrote:
> > > On Tuesday, August 1, 2023, 10:54:40 AM MDT,
>wrote:
> > &g
On Tuesday, August 1, 2023, 10:54:40 AM MDT, wrote:
On Montag, 31. Juli 2023 23:06:54 CEST Gary C. New via tor-relays wrote:
>> Please let me know, if you are able to get the OBFS4
>> bridge working without exposing the ORPort. Respectfully,
> Yes, that's work
round:
ORPort 8443 NoListen
ORPort 127.0.0.1:8443 NoAdvertise _______
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
the issue is confirmed, you can configure the machine layer firewall to
block all outbound tcp/22 traffic initiated from the server in question with
iptables, etc.
I doubt it is Tor related.
Best Wishes!
Gary—
This Message Originated by the Sun.
iBigBlue 63W Solar Array (~12 Hour Charge)
+ 2 x
On Tuesday, August 8, 2023, 10:24:44 AM MDT, wrote:
On Dienstag, 8. August 2023 00:30:38 CEST Gary C. New via tor-relays wrote:
> > In addition to network diversity, there is the fact that most individuals
> > find it necessary to run an at Home internet connection 24 x
and pivot to an
at-Home, Bridge operator, which has been trouble free and much more amenable to
at-Home operation.
Thanks for running a Tor Relay... or Bridge.
On Thursday, August 3, 2023, 1:58:08 PM MDT, telekobold
wrote:
Hi,
On 03.08.23 14:22, Logforme wrote:
> My "
st wasn’t approved
>>> by
>>> moderator). I was running a relay from my home ISP. After a short while
>>> certain websites became inaccessible from other computers in my home
>>> network that shared the same public IP. After trial and error with other
>>> IP
appen as
> it's been running for a few years, but suddenly saying it's new?
>
>
>
>
> Thanks.
>
>
>
>
> \--Keifer
[https_metrics.torproject.org_rs.html_details_79E3B585803DE805CCBC00C1EF36B1E74372861D]:
https://metrics.torproject.org/rs.html#details/
> > they're all telling me that the IP is in Japan.
> >
> > I'm wondering if perhaps there's an issue with the GeoIP lookup? Or
> > perhaps an outdated database?
> >
> > Thanks!
> >
> >
> > ___
&g
as unstable, you can
try to run some monitoring software, or sign up for the revamped Tor
Weather service (https://weather.torproject.org/). Unfortunately, if
your downtime is due to system updates, you'll need to try to
consolidate those, as even scheduled restarts are counted against a
rel
Valeo,
Paul
On Thu, Oct 12, 2023 at 11:41:58AM +, torrrel...@riseup.net wrote:
> I provided some high speed Tor nodes (non-exits and guards) but I quit
> in this year to make some space for my other projects. I would continue
> collaborating by keep Tor nodes online if I receive some
901 - 998 of 998 matches
Mail list logo
