Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • N Nebulo
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 38
    • Issues 38
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • PublicAndroidApps
  • Nebulo
  • Issues
  • #113
Closed
Open
Issue created Jul 13, 2019 by Daniel Wolf@dwolfMaintainer

Explore a rooted option

On rooted devices there might not be the need for a dummy VPN. Using either iptables or by adding a route on the device traffic could be redirected to Nebulo which could then forward it as it does now anyways.

Pros/Cons:

IpTables:

  • Pro: easy and fast to use, can target ports directly (allowing a forward of *:53 instead of host:* like it is currently)
  • Con: Only works for IPv4 (no ip6tables equivalent)
  • Con: Without using the VPN the dns server can't be set for all apps
  • Con: Without a precise rule packets sent by Nebulo might be intercepted as well

Route:

  • Con: Unsure whether all devices support it
  • Con: Without a precise route packets sent by Nebulo might be intercepted as well (no way to exclude Nebulo from routing)
  • Pro: Works with IPv6
Edited Aug 20, 2019 by Daniel Wolf
Assignee
Assign to
Time tracking