Btw, anyone had any luck setting them to something different than 0.0.0.0 and running a local logging server there? https:443 gets too complicated with mitm, but they fallback to http:80 anyway, no?
Interesting idea! Although, if a blocklist already has added a domain to their lists, I’m not really interested in logging connections to that specific address.
What I am interested in is what connections my devices establish unprompted, uncalled for when not using any blocklists. That I do with tcpdump on Linux or PCAPdroid on my phone.
Yeah, but if some brittle webäpp breaks because of a failed tracking connection, i’d like to know why it broke. Or that a site tried to connect <nefarious-url>, for that matter.
Admittedly, my usecase might be a bit special, since i have the blocklist locally insead of a pihole with logging.
Btw, anyone had any luck setting them to something different than 0.0.0.0 and running a local logging server there? https:443 gets too complicated with mitm, but they fallback to http:80 anyway, no?
Interesting idea! Although, if a blocklist already has added a domain to their lists, I’m not really interested in logging connections to that specific address.
What I am interested in is what connections my devices establish unprompted, uncalled for when not using any blocklists. That I do with
tcpdumpon Linux or PCAPdroid on my phone.Yeah, but if some brittle webäpp breaks because of a failed tracking connection, i’d like to know why it broke. Or that a site tried to connect <nefarious-url>, for that matter.
Admittedly, my usecase might be a bit special, since i have the blocklist locally insead of a pihole with logging.