-
Notifications
You must be signed in to change notification settings - Fork 446
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ISSUE] protocol2 , port 0, pid -100 (unknown) - in connection log #1214
Comments
thanks for sharing this, an annoyance would perhaps be better word than the issue.. but I happened to notice the Unknown(-100) instance in the new view on my new phone and actually reinstalled (almost - apart for recovery partition) android 10 from scratch.. and its right there again: AFWall+ Mode (whitelist [default enabled]/blacklist) i am currently trying to reinstall this one more time without gapps (F-Droid seems to be good enough replacement, thanks for having updated AFWall+ there) |
after reinstallation of the same lineageos with magisk but without google apps, i saw the above Unknown app in logs for a while ..when logs worked, then something happened and since there there are no new log records even after phone reboot.. and deleting afwall with its data and reinstalling it via adb didn't resolve the problem with broken logs #1223 |
Same here. Anyway, I'm pretty sure -100 isn't one app but multiple. For example I saw LAN connections on port 22000 blocked but that looks like syncthing (which is allowed to access LAN). Also there are so many different IPs ans ports in the log (around one new log/sec when the device is idle, sykrocketing when used), it's hard to believe this is one app. |
Yes, I observed the same thing. My guess is that is the kernel itself or some very low level stuff going on (as previously afwall was reporting). I can replicate with a very simple example. Open spotify app, then instantly there will be logged blocked entries under -100 with destination 224.0.0.22:0 on protocol 2 and source port my wifi lan ip and port 0. Indeed entries triggered from multiple apps are aggregated here. One thing to mention is that I didn't observe any impact so far, and apps are working normally. I managed to reduce the number of blocked connections to minimum, using Autostarts and App Manager (open source projects available on izzyondroid and f-droid) to stop a lot of android system apps i do not use from triggereing on certain events by managing the broadcasts and receivers. |
Same problem on my new installed Galaxy S8, Android 9. edit: the ports are 0 and the correct ports of the addressed service (80, 433,...) |
Any updates on whats causing unknown -100 ? |
This is related to #1232. Duplicate |
I have this entry in connection log (latest afwall)
Old view:
AppID : -1
App Name:
Total Packets Blocked: 100
....
[2]157.229.179.131:0(28)
....
In new view, appears
as unknown (pid -100)
What could this be?
The text was updated successfully, but these errors were encountered: