Allow natively and by default non-Tor and IANA environments about invizible HOT 7 CLOSED

Thank you. I will add this as an option. This will increase the time that iptables rules are applied and may cause problems on some devices.

In any case, these addresses are not allowed on the Tor exit nodes, so this does not affect privacy or anonymity.

from invizible.

If performance will be affected and also could cause malfunctions, preferrebly we have to discuss alternatives.

For example, add these hosts, if and when possible, to IP whitelist easy feature already provided by Invizible if this causes less conflicts with current app logic.

You just have to add support for entire network blocks to it for applying correctly.

Althought i would think this won't be the proper solution, I'm just making proposals to hear from you which one would fit best for your app.

from invizible.

I know that it is correct to add these addresses. But in real life, we have android limitations. Therefore, I think that the corresponding option will be a compromise.

from invizible.

this requires chaning "10.0.0.0/8" by VirtualAddrNetwork of tor.conf
consider adding

VirtualAddrNetworkIPv6
PreferIPv6Automap

from invizible.

VirtualAddrNetworkIPv6
PreferIPv6Automap

InviZible blocks ipv6 due to security issues in Root mode. It is possible to allow ipv6 in VPN mode, but investigation is required.

from invizible.

this requires chaning "10.0.0.0/8" by VirtualAddrNetwork of tor.conf
consider adding

VirtualAddrNetworkIPv6
PreferIPv6Automap

Networks like 10.0.0.0/8 should never be routed under Tor. Those are strictly defined as non-Tor environments.

By defining VirtualAddrNetwork under 10.0.0.0/8 makes sense as this is made for resolving and stablishing a "virtual local environment" in order to easily enroute requests to special .onion hidden services which otherwise would be impossible to map outside of Tor network logic.

from invizible.

Added in 1.0.8 beta

from invizible.