Here is a traceroute from *Verizon Wireless*:
$ traceroute 86.59.21.38
traceroute to 86.59.21.38 (86.59.21.38), 64 hops max, 52 byte packets
1 * * *
2 9.sub-66-174-32.myvzw.com (66.174.32.9) 329.758 ms 57.492 ms 24.798
ms
3 130.sub-69-83-185.myvzw.com (69.83.185.130) 39.733 ms 39.718 ms
This work is completed. Faravahar should be happier.
All the best,
Sina
"Be the change that you wish to see in the world." - Mahatma Gandhi
- On Jan 11, 2018, at 1:06 PM, sina s...@redteam.net wrote:
> FYI, This work will begin shortly.
>
>
> All the best,
> Sina
>
> "Be the change that
FYI, This work will begin shortly.
All the best,
Sina
"Be the change that you wish to see in the world." - Mahatma Gandhi
- On Jan 9, 2018, at 6:28 PM, sina s...@redteam.net wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
>
> Scheduled Maintenance Thursday, January 11, 2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Scheduled Maintenance Thursday, January 11, 2018 at 18:00:00 UTC to 22:00
UTC
Dear Tor Network,
I am upgrading/replacing the hardware for Faravahar, and would like to announce
a maintenance window:
Scheduled Start: Thursday, January 11, 20
Dear Tor Relay Operators,
Faravahar had some hardware issues last night, while I was on an airplane
without internet access.
It took me a few hours to respond and I apologize for the delay.
Please note that redundancy is built into the network, and I am committed to
operating this system with v
Dear Team,
cymrubridge02 (meek-azure) needs a reboot, it's going to be down for
less than a min and will come right back up.
> https://atlas.torproject.org/#details/8F4541EEE3F2306B7B9FEF1795EC302F6B84DAE8
All the best,
Sina
--
Sina Rabbani | Systems Engineer | Team Cymru, In
Dear Relay Operator,
I am the operator of Faravahar, It has been having some network issues,
specifically very long latency. But this is the first time I hear of an issue
like this.
154.35.32.5 is Faravahr's older IP addresses which was replaced with and
154.35.175.225 is the new IP (current).
Hi allicoder,
The images on Tor Cloud website have not been updated for a while. The project
is lacking someone
that can keep it up to date. I tried to take on the responsibility but so far I
have failed to dedicate
the necessary time. Sorry for the bad experience.
As far as the specific proble
There was a new line added to authority director configs, which was a response
to the recent Sybil attack [1]:
MinUptimeHidServDirectoryV2 96 hours
That's only 4 days, I wonder if anything else has changed.
--SiNA
[1]
https://lists.torproject.org/pipermail/tor-consensus-health/2014-December/0
Dear Relay Operators,
I noticed there are very few US based exit nodes in the network. And more and
more
people are jumping on the same set of AS numbers in Europe.
I am not if the reason is lack of Tor friendly ISPs or people are just too
freaked out about
the summer of Snowden.
I think it's
You mind find this script interesting:
https://gitweb.torproject.org/tor-cloud.git/blob/ce98487e1174bff3a76c1f9f0327486b5be89a44:/ec2-prep.sh
--SiNA
- On Nov 4, 2014, at 12:35 PM, Nan n...@goodcrypto.com wrote:
> We're considering trying to make it a single click for a sysadmin to add their
I can also offer hosting, either EU or US. Please let me know, if I can be
helpful.
--SiNA
On Sep 18, 2014 3:14 AM, "Moritz Bartl" wrote:
> On 09/18/2014 04:51 AM, Mike Perry wrote:
> > Forwarded from tor-dev to here, in case any relay operators missed this:
> >
> > - Forwarded message from
Hi,
I have an additional scan on all the relays in the current consensus:
https://encrypted.redteam.net/bleeding_relays/
You may also be interested in the one that tracks Exit and Guards also:
https://encrypted.redteam.net/bleeding_edges/
All the best,
SiNA
--
"be the change we wish to see in
13 matches
Mail list logo
