Administered by:
I expetience some strange behaviour with @torproject #TorBrowser on a (throttled) mobile connection:
Neither bridges (obfs4, meek-azure nor snowflake) nor without with get some.stable.connection and just contantly have circuits dying before it can even load the homepage to show it's connected.
Is it just me or do #MVNO's using #CGNAT on #RFC1918 adress spaces also try to prevent and block #Tor useage?
@kkarhan
Are you able to elaborate/simplify the last paragraph?
Tor can be censored. Different bridges can help. Does I2P work for you?
@torproject
@dsfgs @torproject I tested it on a "throtted" 4G connection in Germany.
Circuts constantly crashed and didn't get built at all.
I tried all bridge options (tho I didn't add any extra/unlisted bridges cuz I was on the go) and it constantly broke.
I don't use #I2P so I don't have any data to compare.
I'd love to see more comparative data from other users in #Germany using #TorBrowser over a "throttled" #mobile connection.
@dsfgs @torproject I didn't have any of these issues before and I'be been using #TorBrowser and #Orbot for over 13 years now on different mobile devices.
In fact, I'd rather experienced #Orbot to work like a #PerformanceProxy on throttled connections...
@kkarhan
Bizarre. Silly question perhaps but when you say "throttled", is that by you or by the ISP? Not that it should matter.
@torproject
@kkarhan@mstdn.social@dsfgs @torproject it's by the #MVNO, and they do it very ugly by not negotiating a lower #LinkRate (which would make sense given the actual claims why they trottle people down) but just limiting packet rate and dropping shit that would exceed the bandwith.
Resulting in #SlowStart issues...
But this seems almost like connections get reset.
@kkarhan
We are not familiar but it sounds like you will need to do something on your end to limit the rate. Even more strange that the ISP would operate like that to simply drop packets. Sounds wasteful.
@torproject