Bug #3334
13.0.6 - I cannot log in to Wifi network
| Status: | New | Start date: | 05/01/2014 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | Spent time: | - | |
| Target version: | v15 - MayPhlowerz | |||
| Component: |
Description
I connect to various wifi networks that require a login (or "accept terms"). I leave Browser un-torified so I can connect to the network, then use Orweb for everything else, and I proxy basically all my other applications through Orbot.
When I upgraded to 13.0.6, I had problems, and downgraded to 13.0.4a.
What happens in 13.0.6 is that when I move to a network that requires intervention, Orbot cannot work because it cannot reach any nodes, and Browser won't work, because it seems that Orbot won't let it connect unsupervised while it's disabled? I end up having to shut down Orbot, connect to the network, and then start Orbot up again. Although somtimes even that doesn't work and I have to disable Orbot and reboot.
Am I doing something wrong, or am I missing a setting that would change this behavior?
History
#1 Updated by n8fr8 over 3 years ago
Just to be clear, you are using root+transparent proxying in "app" mode, and you are NOT enabling the stock Browser app to be proxied through Tor, via the Orbot app select list?
#2 Updated by luigibai over 3 years ago
Yes. I am using root/superuser, transparent proxying in "app" mode, with most apps proxied via the Orbot select list.
Browser is NOT proxied, so I can respond to the local wifi AP challenge/auth page.
#3 Updated by n8fr8 over 3 years ago
- Target version set to v15 - MayPhlowerz