Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #4423
Closed
Open
Created Nov 07, 2011 by Trac@tracbot

Orbot flushes all foreign iptables rules

Regardless of whether transparency proxy is enabled or not, all foreign iptables rules get flushed when connecting or disconnecting to/from Tor.

Iptables chains stay untouched.

This is a big problem when using iptables based firewalls like "DroidWall" or "LBE Privacy Guard".

Example 1: A internet access blocked application (a game, google location service, etc.) gets unblocked as soon as Orbot connects/disconnects to Tor.

Example 2: A application should just be able to communicate through Tor. iptables related firewall blocks it. But Orbot's transparency proxy should allow it.

This still occures on the latest RC build: "Orbot-1.0.6-Tor-0.2.3.7-alpha-RC3"

Trac:
Username: aribns

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking