ations. But also,
maybe people just quietly stopped trying and left, who knows.
I run my tor relay inside a Debian KVM on a ProxMox (2C, 8G ram); Ryzen
5 5500 CPU. No weird setups here.
(C) The old-school way of handling this was to get a dyndns account and
then set your torrc Address
Greetings fellow relay operators!
I'm currently running a tor relay on a dynamic IP Address connection,
usually my ISP gives me a new address every day or so-
Lately [for the past like week or so- /can't remember when it started
happening/], I have to manually restart it when
figure and deploy
> sslh on large scale.
>
> If tor handshake can be handled by sslh, could the process (of the tor
> relay) be listening on 127.0.0.1:12345 and publish good relay
> descriptor as well ?
>
> Currently, in my relay config, I have the following:
>
> &quo
just a little update:
I've reproduced this bug on my laptop with Debian Buster.
I've noticed that this problem occurs only with tor 0.4.2.5. Tor
0.4.1.6, from Debian buster backports repository, works properly.
Il 05/01/20 07:43, tor-re...@riseup.net ha scritto:
Hi,
I'm running an exit re
Hi,
I'm running an exit relay on a Debian Buster. I installed libseccomp and
I've built tor 0.4.2.5 using debuild, like the wiki says.
Today I noticed that tor crashes on HUP signal, only when the Sandbox
option is on. I never had this problem.
This is what my log says:
an 05 08:23:10.000
I think that a network based to much on remotes VMs, with closed source
software running on the most deep machine level, is not very resilient
and secure.
So the reason why I was thinking to do so is that I wanted to run a
small exit relay on a device running only open source software, like
O
Hello dear friends
I'm running a non exit relay on a debian machine (in the next few months
I will switch to *BSD) on a Lime2. I'm running an exit relay too on a
remote VM.
I would turn my non-exit relay in an exit one, but for obvious reasons,
I don't want to run It from my shitty ISP IP. I
2206C72ECC0D55593BC7B698F982533F1E141DD2
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
Hello AMuse,
we faced the same about 1-2 month ago. Actuall people use fail2ban which
creates abuse mails to you provider.
Thats not new. But recently the abuse mails have risen to numbers which
lead us to believe there are acutally more people abusing ssh via tor
than people really using it.
In
Hello Moritz,
we run such an setting since several years.
Whois records show our ripe object with abuse-r...@...as abuse-mailbox
address.
This is connected to an auto-responder.
In auto-responder mail we explain what is going on and offer to write to
our abuse@ email address.
This really is
Hello Roger,
I updated the ticket. You will find the output of the valgrind there as
well:
https://trac.torproject.org/projects/tor/attachment/ticket/22255/valgrind.txt
best regards
Dirk
On 23.05.2017 06:00, Roger Dingledine wrote:
> On Tue, May 23, 2017 at 03:01:10AM +, John Ricketts wrote
Dear all,
we are operating two exit nodes with each two tor processes out of
Switzerland.
The nodes worked quite stable until about 2-3 weeks ago.
Since then we experience frequent disruptions (Up to several times a
day). This is caused by a significant rise in memory consumption
by the tor proce
It was two days ago. Today I can not reach it as well.
best regards
Dirk
On 01.05.2017 08:08, scar wrote:
> I was unable to reach the site, is it still in operation?
>
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.t
Hello,
I'm part of the abuse team of the mentioned Tor Exit.
Also I follow this mailing list.
I read you post several times but I'm not sure what you where doing.
It looks to me like you running a tor node and have also a dyndns update
process running.
Is this correct ? Please provide some more
> fixed, thanks.
https://gitweb.torproject.org/debian/tor.git/commit/?id=040fffc07b430d825e5acc88e6d2085a17b718fa
There is a little typo in the fix
tor@$name "
vs
tor@$name"
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torpr
This is only relevant for debian users.
If you assume you can manage your instances with the usual systemctl commands
like
systemctl disable/enable tor@myinstance
beware that they have no effect.
Note: systemctl start/stop works as expected.
This is important to know especially if you have mult
https://gitweb.torproject.org/debian/tor.git/tree/debian/tor-instance-create#n89
is:
systemctl tor@$name start
should be:
systemctl start tor@$name mailto:tor@$name
https://gitweb.torproject.org/debian/tor.git/tree/debian/tor-instance-create.8.txt#n18
brdige -> bridge
__
When upgrading the tor package on debian I get the following syslog messages:
systemd[1]: Failed to reset devices.list on /system.slice: Invalid argument
systemd[1]: Failed to reset devices.list on /system.slice/system-tor.slice:
Invalid argument
Should I be concerned?
made a ticket:
https://trac.torproject.org/projects/tor/ticket/19847
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> So there is no way to disable the default instance using systemctl after all?
To answer my own question:
systemctl mask tor@default
disables the default instance for real.
..but I'm still curious why tor@default is a static unit (without [Install]
section)
https://bbs.archlinux.org/viewtopic.p
> > > > Also: you can not start/stop/restart tor.service separately without
> > > > leaving all other tor instances untouched.
> > >
> > > tor.service is *not* the default service. tor.service is the collection
> > > of all service instances.
> >
> >
> > Gosh, you are right there is tor@defaul
> On August 5, 2016 at 1:24 PM Peter Palfrader wrote:
>
>
> On Fri, 05 Aug 2016, tor relay wrote:
>
> > Also: you can not start/stop/restart tor.service separately without leaving
> > all other tor instances untouched.
>
> tor.service is *not* the def
>
> Why this hack (disable a service by moving away its config) and not the
> more clean approach like the one take by the RPM maintainer?
>
..that allows one to manage (start/stop/enable/disable) each service
separately using standard tools and methodologies (and not service specific
wa
>
> On August 4, 2016 at 10:23 AM Peter Palfrader
> wrote:
>
> On Thu, 04 Aug 2016, tor relay wrote:
>
> > >
> > > > >
> > > On August 3, 2016 at 11:51 PM Green Dream
> > > wrote:
> >
https://trac.torproject.org/projects/tor/ticket/19825___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> On August 3, 2016 at 11:51 PM Green Dream wrote:
>
> Sorry, I didn't understand that your daemon didn't restart after the
> upgrade. I ran through the upgrade on 2 relays, and apt started the service
> post-upgrade on both.
>
>
>
Since it is reproducible in my case as well I assume y
> On August 3, 2016 at 11:04 PM Green Dream wrote:
>
>
> > When upgrading, all running tor instances are stopped (not restarted,
> as expected)
>
> > syslog shows:
>
> > Interrupt: we have stopped accepting new connections, and will shut
> down in 30 seconds. Interrupt again to
Hi,
I'm running a relay on debian jessie using packages from deb.torproject.org.
I want to share the problems I had so others are aware of them when upgrading
their relays.
While upgrading from 0.2.7.6 to 0.2.8.6 via apt-get, I did a
tail -f syslog
to make sure I notice problems during the up
> On July 28, 2016 at 8:13 PM "Tor-Node.net" wrote:
>
>
> Markus Koch mailto:niftybu...@googlemail.com >
> wrote:
>
> > exit allowed?
>
> I can vouch forhttp://www.stayon.no
>
>
>
" We are also changing the direction of our business, and becoming a hosting
provider for IT c
> On July 28, 2016 at 2:48 PM Markus Koch wrote:
>
>
> exit allowed?
no, that is why I put "non-exit" in the subject of my email.
https://trac.torproject.org/projects/tor/wiki/doc/GoodBadISPs#Italy1
And yes, their support is poor, but as long as your servers run you won't need
them.
Anothe
>
> On July 28, 2016 at 9:11 AM Roman Mamedov wrote:
>
> On Thu, 28 Jul 2016 08:09:12 +0100
> "Louie Cardone-Noott" wrote:
>
> > >
> > Am I right in thinking that even 2 TByte/month is fairly low? That's
> > only 6 Mbit/s average (whether that's 6/6 or 3/3
> On July 6, 2016 at 6:16 PM Jean-Philippe Décarie-Mathieu
> wrote:
>
> I've been running an exit node for over a year on OVH now, no problems so
> far. Highly recommended (especially since they give me 10TB of traffic for
> about 10$USD/month; considering I use about 7-8TB of that per mo
> Well, I'm still sticking with CoolHousing/Virtual Server Lite because I
> hardly ever get abuse
> complaints. For ITL, I may leave after my term expires.
> But a few other companies I found were:
> https://hostmaze.com/
tested it, made really bad experience with them, network performance was
It appears that First Tech Federal Credit Union is blocking all Tor
nodes (including non-exit nodes) from connecting to their website,
http://www.firsttechfed.com
This seems ... misguided on their part. Blocking exit nodes is one
thing, but preventing random people who happen to run a Tor middle
an I via mobile internet so I'm down to
suspecting that they are blocking all Tor relay IPs. This is the exact
error I get:
Access DeniedYou don't have permission to access "http://www.nhs.uk/"; on
this server.
Reference #18.1f7f1002.1397514736.1fe2170c
The reference seems to change e
My several attempts to update to TBB 3.5.4 (XP)unsuccessfully made Tor
exit upon starting, so I fell back to 3.5.3. Atlas shows that my efforts
hadn't gone unnoticed; OnionTorte now appears four times w/ my IP address.
0D50D43BAA728D6E0C4EB181AB79E5C1D7036D08 is the correct one but it
somehow
t increments by one every time; that probably means that
the relay
uses per-IP counters or so, and as far as I know, that should be fine.
After a bit of testing, I think that this issue is present on a lot of Tor
relay nodes. Here
are the first few in the alphabet that look suspicious (didn
wrote:
Question how long you'll stay in the Top 50. Maybe you are lucky but
probably the ISP will end your contract for "abusing" fair use
policies/TOS. Best case they'll throttle you down. Let us know in 30 days :)
Am 22.03.14 21:51, schrieb Trigger Happy:
Hi list,
I'm run
I am a n00b relay (OnionTorte) operator, and, as such, know lamentably
little of what I'm doing. (Yes, I'm one of *those* relay operators.)
When I went to bed last night I had an HSDir flag, but it has since
disappeared. And since this A.M. my consensus was halved. A bit of
promiscuous pokin
39 matches
Mail list logo
