Just to be triple sure, with lan permitted can't apps access the router creating the lan and from there the outside internet?Basically yes, but only for LAN (local) traffic. WAN traffic (internet) can still be filtered with this option on.
The router will normally not allow/route this, so no, they can't.Just to be triple sure, with lan permitted can't apps access the router creating the lan and from there the outside internet?
NetGuard tried to connect to a remote server via a Linux socket and got "no route to host" back. This can have a number of causes, but this is not caused and cannot be fixed by NetGuard.Hello, when I'm at home on my wifi, the browser sometimes says that website can't be reached/there's no connection (but there is - script ping reply is not interrupted e.g. 220916: 9 bytes from 147.32.235.161: icmp_seq=2628 ttl=64).
Whart can be the reason for this?
Here is part from logcat NG v2.251 logcat:
07-11 22:09:16.960 30386 21267 E NetGuard.JNI: TCP socket from 10.1.10.1/37696 to 192.168.1.1/7 LISTEN loc 0 rem 0 SO_ERROR 113: No route to host
07-11 22:09:20.049 30386 21267 I NetGuard.Service: Filtering uid=1000 v4 p1 192.168.1.1/7481 allowed=true rule v4 p1 port=0 uid=1000 192.168.1.1//192.168.1.1
07-11 22:09:21.054 30386 21267 I NetGuard.Service: Filtering uid=1000 v4 p1 192.168.1.1/7481 allowed=true rule v4 p1 port=0 uid=1000 192.168.1.1//192.168.1.1
07-11 22:09:22.070 30386 21267 I NetGuard.Service: Filtering uid=1000 v4 p6 192.168.1.1/7 allowed=true rule v4 p6 port=7 uid=1000 192.168.1.1//192.168.1.1
07-11 22:09:23.048 30386 21267 E NetGuard.JNI: TCP socket from 10.1.10.1/37700 to 192.168.1.1/7 LISTEN loc 0 rem 0 SO_ERROR 113: No route to host
07-11 22:09:32.212 30386 21267 E NetGuard.JNI: TCP socket from 10.1.10.1/47964 to 213.150.2.133/443 LISTEN loc 0 rem 0 SO_ERROR 113: No route to host
etc.
I don't think this is caused by removing the VPN handover.Hello Marcel
Since version 2.252 the key symbol in the notification area has disappeared although I've enabled all notifications for the app.
Is it due to the VPN handover deletion?
Thanks for the answer.
Just trying to learn and I don't know German.I can also capture the constantly increasing RAM consumption by NG with filtering enabled on a new Android 9 smartphone (see screenshot, even more than the Android operating system!). Too bad Marcel can't reproduce it like this.
Do you use work profiles or things like Island?I don't know either, especially I don't know what the difference between 'Android operating system' and 'Android system' can be. It is a brand new UMIDIGI S3 Pro with Android 9.
NetGuard tried to connect to a remote server via a Linux socket and got "no route to host" back. This can have a number of causes, but this is not caused and cannot be fixed by NetGuard.
Possible causes are that there is another, external firewall blocking connections or that the host is not responding (in time).
NetGuard cannot force sockets to connect and it is highly unlikely that there are bugs in this part of the Linux kernel.It happens to 3 diff. connections at the same time:
192.168.1.1/7 (icmp)
213.150.2.133/443 (https)
217.11.199.167/443 (https)
It could be if my router can behave like firewall but I don't think so.
NG logcat for that section attached.
EHOSTUNREACH
The destination host cannot be reached (probably because the host is down or a remote router cannot reach it).
Basically the FAQ says that this is not possible because DNS over TLS appears encrypted to NetGuard.Thanks for Netguard. It is a very intuitive and useful software.
My question/suggestion is could you add the app/service DNS over TLS uses or Netguard shows to the FAQ item 64 as it isn't overly apparent and if the choice of blocking everything by default is selected, then it is obviously blocked.
Does this among other things mean less battery consumption?This version will, depending on how your Android version handles connectivity changes, restart the Android VPN less often.
Depending on how your Android version handles connectivity changes: yes.