[tor-bugs] #32597 [Circumvention/Snowflake]: Hello, currently, in China, Tor Browser 9.5a2 still can't connect to Tor network through snowflake bridge

[Tor Bug Tracker & Wiki]

#32597: Hello, currently, in China, Tor Browser 9.5a2 still can't connect to Tor
network through snowflake bridge
-------------------------------------+------------------------
 Reporter:  amiableclarity2011       |          Owner:  (none)
     Type:  defect                   |         Status:  new
 Priority:  Immediate                |      Milestone:
Component:  Circumvention/Snowflake  |        Version:
 Severity:  Normal                   |     Resolution:
 Keywords:                           |  Actual Points:
Parent ID:                           |         Points:
 Reviewer:                           |        Sponsor:
-------------------------------------+------------------------

Comment (by cohosh):

 Replying to [comment:5 amiableclarity2011]:
 > thank you very much for your help. i really appreciate it.
 >
 > but it seems that stun.ekiga.net is not blocked by great firewall
 >
 >
 > ping stun.ekiga.net
 > PING stun.ekiga.net (216.93.246.18) 56(84) bytes of data.
 > 64 bytes from 216.93.246.18 (216.93.246.18): icmp_seq=1 ttl=48 time=224
 ms
 > 64 bytes from 216.93.246.18 (216.93.246.18): icmp_seq=2 ttl=48 time=227
 ms
 > 64 bytes from 216.93.246.18 (216.93.246.18): icmp_seq=3 ttl=48 time=223
 ms
 > 64 bytes from 216.93.246.18 (216.93.246.18): icmp_seq=4 ttl=48 time=222
 ms
 > 64 bytes from 216.93.246.18 (216.93.246.18): icmp_seq=5 ttl=48 time=222
 ms
 > 64 bytes from 216.93.246.18 (216.93.246.18): icmp_seq=6 ttl=48 time=234
 ms
 > 64 bytes from 216.93.246.18 (216.93.246.18): icmp_seq=7 ttl=48 time=222
 ms
 > 64 bytes from 216.93.246.18 (216.93.246.18): icmp_seq=8 ttl=48 time=226
 ms
 > 64 bytes from 216.93.246.18 (216.93.246.18): icmp_seq=9 ttl=48 time=225
 ms
 > 64 bytes from 216.93.246.18 (216.93.246.18): icmp_seq=10 ttl=48 time=222
 ms
 > 64 bytes from 216.93.246.18 (216.93.246.18): icmp_seq=11 ttl=48 time=223
 ms
 > 64 bytes from 216.93.246.18 (216.93.246.18): icmp_seq=12 ttl=48 time=226
 ms
 > 64 bytes from 216.93.246.18 (216.93.246.18): icmp_seq=13 ttl=48 time=227
 ms
 > 64 bytes from 216.93.246.18 (216.93.246.18): icmp_seq=14 ttl=48 time=229
 ms
 > 64 bytes from 216.93.246.18 (216.93.246.18): icmp_seq=15 ttl=48 time=229
 ms
 > 64 bytes from 216.93.246.18 (216.93.246.18): icmp_seq=16 ttl=48 time=229
 ms
 > 64 bytes from 216.93.246.18 (216.93.246.18): icmp_seq=17 ttl=48 time=223
 ms
 > 64 bytes from 216.93.246.18 (216.93.246.18): icmp_seq=18 ttl=48 time=222
 ms
 > 64 bytes from 216.93.246.18 (216.93.246.18): icmp_seq=19 ttl=48 time=223
 ms
 > 64 bytes from 216.93.246.18 (216.93.246.18): icmp_seq=20 ttl=48 time=224
 ms
 > 64 bytes from 216.93.246.18 (216.93.246.18): icmp_seq=21 ttl=48 time=223
 ms
 > 64 bytes from 216.93.246.18 (216.93.246.18): icmp_seq=22 ttl=48 time=229
 ms
 > 64 bytes from 216.93.246.18 (216.93.246.18): icmp_seq=23 ttl=48 time=242
 ms
 > 64 bytes from 216.93.246.18 (216.93.246.18): icmp_seq=24 ttl=48 time=227
 ms
 > ^C
 > --- stun.ekiga.net ping statistics ---
 > 25 packets transmitted, 24 received, 4% packet loss, time 28759ms
 > rtt min/avg/max/mdev = 222.237/226.342/242.273/4.449 ms
 >
 >
 >
 > above is the ping result.
 Thanks for the information, that matches what I'm seeing on the VPS then.

 Have you tried reconnecting multiple times? I've been able to get a
 connection on the VPS but sometimes it takes a few tries first and it's
 still very slow.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/32597#comment:7>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online