Thanks!
On Fri, May 25, 2018, 17:35 wrote:
> >Hi tor-relays mailing list,
> >
> >Good news! Verizon unblocked tor26 (86.59.21.38).
> >
> >I posted something similar on NANOG (with modifications for network
> people) here:
> >https://mailman.nanog.org/pipermail/nanog/2018-May/095386.html
> >
> >S
>Hi tor-relays mailing list,
>
>Good news! Verizon unblocked tor26 (86.59.21.38).
>
>I posted something similar on NANOG (with modifications for network people)
>here:
>https://mailman.nanog.org/pipermail/nanog/2018-May/095386.html
>
>Someone nice at Verizon must have read NANOG (VZ NOC people pr
Hi tor-relays mailing list,
Good news! Verizon unblocked tor26 (86.59.21.38).
I posted something similar on NANOG (with modifications for network
people) here:
https://mailman.nanog.org/pipermail/nanog/2018-May/095386.html
Someone nice at Verizon must have read NANOG (VZ NOC people probably
So just letting Quad9 wouldn’t solve things if Verizon needs to block a
specific IP Address. It’s good to hear blocking that one server doesn’t cripple
the Tor network. I hope this gets resolved.
Sent from my iPhone
> On May 16, 2018, at 11:45 AM, Matthew Finkel wrote:
>
>> On Wed, May 16, 20
On Wed, May 16, 2018 at 11:36:58AM -0400, Nathaniel Suchy (Lunorian) wrote:
> If Verizon is suddenly worried about malware, why not block at the DNS level
> with something like Quad9 where it’s managed by more competent professionals?
> (Of course still allowing alternate DNS Servers)
They proba
On Wed, May 16, 2018 at 11:33:54AM -0400, Nathaniel Suchy (Lunorian) wrote:
> Can you still use Tor on Verizon with bridges?
This is only one of the directory authorities. A tor client using
Verizon may never notice they can't reach this one server.
___
If Verizon is suddenly worried about malware, why not block at the DNS level
with something like Quad9 where it’s managed by more competent professionals?
(Of course still allowing alternate DNS Servers) Does Tor bootstrap by IP
Address directly?
Sent from my iPhone
> On May 16, 2018, at 11:32
Can you still use Tor on Verizon with bridges?
Sent from my iPhone
> On May 16, 2018, at 11:05 AM, Roger Dingledine wrote:
>
>> On Tue, May 15, 2018 at 08:12:50PM -0400, Neel Chauhan wrote:
>> Hi tor-relays mailing list,
>>
>> I have noticed that the Tor consensus server tor26
>> (https://met
Quoting Roger Dingledine (2018-05-16 15:05:29)
> The fix (if my theory is right) would be to reach whatever engineer made
> this leap, and teach them about Tor. But it will be extra challenging
> because they don't even know that there's something they need to learn.
like the fact that malware can
On Tue, May 15, 2018 at 08:12:50PM -0400, Neel Chauhan wrote:
> Hi tor-relays mailing list,
>
> I have noticed that the Tor consensus server tor26
> (https://metrics.torproject.org/rs.html#details/847B1F850344D7876491A54892F904934E4EB85D)
> is blocked on Verizon's UUNET (AS701) backbone, and ther
The Verizon Wireless network seems to be the same.
https://imgur.com/a/fw6X9ZY
On Wed, May 16, 2018 at 8:17 AM Matthew Glennon
wrote:
> My relay exhibits the same results on AS701, MCI Communications Services,
> Inc. d/b/a Verizon Business
>
> https://metrics.torproject.org/rs.html#details/924B2
My relay exhibits the same results on AS701, MCI Communications Services,
Inc. d/b/a Verizon Business
https://metrics.torproject.org/rs.html#details/924B24AFA7F075D059E8EEB284CC400B33D3D036
matthew@freedom:~$ traceroute 86.59.21.38
traceroute to 86.59.21.38 (86.59.21.38), 30 hops max, 60 byte pack
On Tue, May 15, 2018 at 08:12:50PM -0400, Neel Chauhan wrote:
> Hi tor-relays mailing list,
>
> I have noticed that the Tor consensus server tor26
> (https://metrics.torproject.org/rs.html#details/847B1F850344D7876491A54892F904934E4EB85D)
> is blocked on Verizon's UUNET (AS701) backbone, and ther
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
On Tue, May 15, 2018 at 08:12:50PM -0400, Neel Chauhan wrote:
> Hi tor-relays mailing list,
>
> I have noticed that the Tor consensus server tor26
> (https://metrics.torproject.org/rs.html#details/847B1F850344D7876491A54892F904934E4EB85D)
> is blocked on Verizon's UUNET (AS701) backbone, and ther
Hi tor-relays mailing list,
I have noticed that the Tor consensus server tor26
(https://metrics.torproject.org/rs.html#details/847B1F850344D7876491A54892F904934E4EB85D)
is blocked on Verizon's UUNET (AS701) backbone, and therefore, Verizon's
retail services like FiOS and Wireless. I can confir
16 matches
Mail list logo
