1. 01 Apr, 2015 1 commit
  2. 27 Mar, 2015 1 commit
  3. 16 Mar, 2015 11 commits
  4. 15 Mar, 2015 1 commit
  5. 14 Mar, 2015 2 commits
  6. 13 Mar, 2015 1 commit
  7. 10 Mar, 2015 3 commits
  8. 05 Mar, 2015 1 commit
  9. 27 Feb, 2015 3 commits
    • Lorenzo Colitti's avatar
      Add oif rules that allow UID 0 to bypass the VPN. · 57947f02
      Lorenzo Colitti authored
      This is needed for wifi calling so that the kernel (which does
      not set marks) can tee packets towards the modem. It also fixes
      things like not being able to reply to DHCP requests from
      tethered clients when a VPN is up.
      
      System apps can already bypass the VPN using explicit marks, so
      allowing UID 0 to do so does not create additional bypass VPN
      issues.
      
      Bug: 19500693
      Change-Id: Ie324026893637e9bd8e7aa65a37579569390e7b7
      57947f02
    • Lorenzo Colitti's avatar
      Separate NAT from forwarding. · 32d76879
      Lorenzo Colitti authored
      Bug: 19500693
      
      Change-Id: Ib3871106ea3c0d68327611e7568c0710210e4ff2
      32d76879
    • Lorenzo Colitti's avatar
      Make the VPN rule only to originated, not forwarded, traffic. · 5ad4e98f
      Lorenzo Colitti authored
      Currently the VPN rule for the primary user will match every
      forwarded packet on the system, because it specifies a UID range
      that includes 0, and forwarded packets have UID 0.
      
      Use "iif lo" to limit the rule match to locally-originated
      traffic. This requires a kernel that sets the loopback ifindex.
      when originating packets. Anything based on 3.10 is fine, but
      devices using 3.4 will need a one-line change for IPv6.
      
      Bug: 19500693
      Change-Id: Iaab88bed62716dc1cea33b45c4e258f6b3bfc9d0
      5ad4e98f
  10. 25 Feb, 2015 2 commits
  11. 12 Feb, 2015 3 commits
  12. 11 Feb, 2015 1 commit
  13. 04 Feb, 2015 3 commits
  14. 03 Feb, 2015 7 commits