meek seems blocked in China since 2016-10-19

129 views
Skip to first unread message

David Fifield

unread,
Oct 28, 2016, 4:33:17 PM10/28/16
to traff...@googlegroups.com
https://bugs.torproject.org/20495

It looks like meek was blocked in China since about October 19, 2016.

I don't know any details yet. I didn't receive any report. I just
happened to check the graph.
userstats-bridge-combined-cn-2016-07-30-2016-10-28.png

Ox Cart

unread,
Oct 28, 2016, 4:50:09 PM10/28/16
to traff...@googlegroups.com
Thanks for the heads up. Lantern's domain fronting is still working via CloudFront.

Cheers,
Ox


-----------------------------------------------------------------------------------------

"I love people who harness themselves, an ox to a heavy cart,
who pull like water buffalo, with massive patience,
who strain in the mud and the muck to move things forward,
who do what has to be done, again and again."

- Marge Piercy




--
You received this message because you are subscribed to the Google Groups "Network Traffic Obfuscation" group.
To unsubscribe from this group and stop receiving emails from it, send an email to traffic-obf+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

David Fifield

unread,
Nov 14, 2016, 8:52:31 PM11/14/16
to traff...@googlegroups.com
Some time has passed and this no longer looks like a block by China to
me. For one thing, there was a simultaneous drop in many countries, not
only China:

https://bugs.torproject.org/20495#comment:5

And on November 10, there was a simultaneous increase to previous
levels:

https://bugs.torproject.org/20495#comment:7

I still don't know what might have happened, but it doesn't seem like a
censorship block.

Adam Fisk

unread,
Nov 14, 2016, 10:19:23 PM11/14/16
to traff...@googlegroups.com
Interesting David thanks. Maybe server side or client side updates on
those dates? We seem to have seen more blocking since the Donald made
his big win, but nothing meek related in particular.
> --
> You received this message because you are subscribed to the Google Groups "Network Traffic Obfuscation" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to traffic-obf...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



--
--
President
Brave New Software Project, Inc.
https://www.getlantern.org

Nathan Freitas

unread,
Nov 14, 2016, 11:23:59 PM11/14/16
to traff...@googlegroups.com

Could have been the tumultuous upgrade cycle we had for the last version of Orbot... We released an RC that was pretty broken, taking out a good chunk of our users for awhile starting around October 20th:

https://lists.mayfirst.org/pipermail/guardian-dev/2016-October/004938.html

and finally stabilizing around Nov 7th:

https://lists.mayfirst.org/pipermail/guardian-dev/2016-November/004986.html



--
You received this message because you are subscribed to the Google Groups "Network Traffic Obfuscation" group.
To unsubscribe from this group and stop receiving emails from it, send an email to traffic-obf+unsubscribe@googlegroups.com.

Adam Fisk

unread,
Nov 15, 2016, 12:32:16 AM11/15/16
to Nathan Freitas, traff...@googlegroups.com
That sounds fairly likely based on those dates, Nathan. Any idea what
percentage of overall Meek traffic is Orbot? You guys turn it on by
default, which is unique amongst all Tor deployments, is that right?
>> email to traffic-obf...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Network Traffic Obfuscation" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to traffic-obf...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



Nathan Freitas

unread,
Nov 15, 2016, 12:34:07 AM11/15/16
to Adam Fisk, traff...@googlegroups.com
It is not on by default, but we do make it easily accessible.

David Fifield

unread,
Nov 16, 2016, 2:04:09 PM11/16/16
to traff...@googlegroups.com
On Mon, Nov 14, 2016 at 11:23:38PM -0500, Nathan Freitas wrote:
> Could have been the tumultuous upgrade cycle we had for the last version of
> Orbot... We released an RC that was pretty broken, taking out a good chunk of
> our users for awhile starting around October 20th:
>
> https://lists.mayfirst.org/pipermail/guardian-dev/2016-October/004938.html
>
> and finally stabilizing around Nov 7th:
>
> https://lists.mayfirst.org/pipermail/guardian-dev/2016-November/004986.html

Thanks, that's a good idea. If the hypothesis is correct, it means that
Orbot users account for the bulk of meek users in several countries.

FYI, I'm starting to keep track of potential explanations of
metrics-related events at this wiki page:
https://trac.torproject.org/projects/tor/wiki/doc/MetricsTimeline
Reply all
Reply to author
Forward
0 new messages