> Currently, most of the major guard operators are well known people
are you sure?
- Zwiebel, 33rd on that list
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
blacklists the following authorities
for serving malware: dizum, tor26, maatuska, urras
I've contacted them about this via [1] and explained that these hosts are
most likely not malicious and got a replay via e-mail saying that they will
remain blacklisted.
- Zwiebel
[1] http://www.senderbase.
On Tue, Mar 08, 2016 at 11:20:09PM +0800, Tim Wilson-Brown - teor wrote:
>
> > On 8 Mar 2016, at 22:37, Zwiebel wrote:
> >
> > Hello,
> > is there a way to shut down Tor relays for a short time without losing
> > consensus weight or bandwidth?
>
&
idn't fully recover from the downtime
in the last two months. I'd gladly provide 200Mb/s+ of relay bandwidth if I
could, but Tor won't let me.
- Zwiebel
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject
I will keep calm next days ...
> Gesendet: Montag, 19. Mai 2014 um 18:19 Uhr
> Von: "Peter Palfrader"
> An: zwie...@quantentunnel.de
> Cc: "Tor Assistants"
> Betreff: Your tor-relays postings (was: [tor-relays] relay not receiving very
> much traffic)
>
> Hey,
>
> you have been posting to tor
torrc looks good in my eyes.
I dont use 'Address'. Did you try the IP 'Address 193.11.113.99' ?
For a higher speed (which we dont talk about today) you can use 'HardwareAccel 1'
I suppose SSL is not bleeding?
Felix (clueless)
Gesendet: Montag, 19. Mai 2014 um 14:26 Uhr
Von: "
Next hi
I find your IP could be on http://www.linode.com. If right I see in https://www.linode.com/pricing there is a monthly(?!) transfer limit of 3TB to 16TB on first glance. Be careful not to run into volume (and extra cost) trouble. Reduce bandwidth to a even lower value until you know things
Hi
It seems something is wrong with your relay. Look at https://consensus-health.torproject.org/ and search your Nickname. You will see it is not voted to be stable.
Further if you check for https://atlas.torproject.org/#details/21F84E3EC92BA954307C28A8B302F52F55E5A54D you will see drop-out time
I see, network admin. Good to have you back again. If you can push 850Mbit from an university we should bring it to run. I am on midrange machines LE 100Mbit/s. We could go through some details (torrc) here or you check ' https://www.torservers.net/partners.html ' for higher skilled advice.
Fe
Your provider is 'Student network in Vasteras/Eskilstuna' (mdfnet.se), AS1653 SUNET Swedish University Network?
Sounds like a shared connect. You can talk to the admins?
Please check the university Tor recommendations.
I could connect through $94F9D8D35C4A4851B1DAF85F70F90DB95065E81E as guard.
Hmm.
https://atlas.torproject.org/#details/94F9D8D35C4A4851B1DAF85F70F90DB95065E81E
https://consensus-health.torproject.org/
both look good as well.
You are sure your speed is like promised? You tried a speed test like iperf with a second server?
Felix
Gesendet: Sonntag, 18. Ma
Hi Markus
can you please tell your Fingerprint? You checked your consensus?
Felix
Gesendet: Sonntag, 18. Mai 2014 um 18:59 Uhr
Von: "Markus Klock"
An: "tor-relays@lists.torproject.org"
Betreff: [tor-relays] relay not receiving very much traffic
Hello!
I deployed a new tor-relay ab
> >
> > I received a notice from a server provider to immediatly
> > update/upgrade/reboot if I would use Debian. It's the CVE-2014-0196 issue. I
> > did and it came up with Wheezy 3.2.57-3+deb7u1 which should be fine. How
> > relevant is this issue?
>
> From what I gather, you're only affected i
Hi
I received a notice from a server provider to immediatly update/upgrade/reboot
if I would use Debian. It's the CVE-2014-0196 issue. I did and it came up with
Wheezy 3.2.57-3+deb7u1 which should be fine. How relevant is this issue?
Felix
==-- - - - - - - - - - - --===
Today I received my guard flag back (on new keys). It took 5 days. No stable
flag.
Felix
>
> I am on Wheezy and did 'apt-get update' and 'apt-get upgrade'.
> 1.0.1e-2+deb7u5 should be good for Wheezy.
>
> ( Deleted keys, restarted tor, receive a new fingerprint and stand back
> in line for ne
I see the same type of warning on a non-exit and non-guard relay. First time
today:
Apr 12 10:11:35.000 [warn] Rejecting INTRODUCE1 on non-OR or non-edge
circuit 2147515154
Apr 12 10:14:45.000 [warn] Rejecting INTRODUCE1 on non-OR or non-edge
circuit 2147486526
Felix
> >
> > Apr 11 11:25:35.0
s is good.
I go to check the 3170 and reinstall the original firmware as I changed the
original settings for DNS override 1 with CCC DNS and 2 with for not using
ISP DNS. If something interesting turns out I will reshoot this thread.
Thanks for help
sure I re-did all.
My default LAN net is 192.168.178.0 and not what tails thinks for 192.168.0.0.
Could this impact?
Thanks, Zwiebel
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Standard: ORPort 9001
Standard: DirPort 9030
Thanks, Zwiebel
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
nd max 25kByte/s
The log messages tell me success and all runs for a week.
Thanks front-up
Zwiebel
_||_
/ \
/ O O \
\ /
\\__//
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
20 matches
Mail list logo
