Bug #338
No connectivity at all after starting Orbot v11
| Status: | Closed | Start date: | 10/02/2012 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | Spent time: | - | |
| Target version: | - | |||
| Component: |
Description
After moving to v11 of Orbot, I have no connectivity at all after starting Orbot. All web sites are Not Found, no apps work. Toggling built-in iptables option made no difference.
Cyanogenmod 7.2, HTC Vision (a/k/a T-Mobile G2), wifi connected
History
#1 Updated by n8fr8 over 5 years ago
Do you have connectivity if you disable "transparent proxying"? What about doing transproxy app by app?
#2 Updated by kmz over 5 years ago
Selecting per-app transproxy works.
#3 Updated by kmz over 5 years ago
This appears to be a DNS issue. I can pull up sites by IP, not by name.
#4 Updated by kmz over 5 years ago
I still have this problem; who should I send my logs from aLogcat to (and what filter should I use: orbot? tor?)?
#5 Updated by groksteady over 5 years ago
For me, I have to enable transparent proxying but select apps, as well as use default iptables.
This is on Android 4.1.2, the Helly Bean CM variant for Samsung Galaxy S i9000, build 20121810.
#6 Updated by n8fr8 about 5 years ago
- Status changed from New to Resolved
We've done a major rewrite of our iptables rules. Please test the latest release.
The latest version can be found:
1) In Google Play: https://play.google.com/store/apps/details?id=org.torproject.android
2) In our F-Droid repo: https://guardianproject.info/2012/03/15/our-new-f-droid-app-repository/
3) Our via direct APK here:
https://guardianproject.info/releases/Orbot-release-0.2.3.23-rc-1.0.11-RC6.apk (.asc)
#7 Updated by n8fr8 about 5 years ago
- Status changed from Resolved to Closed