Second Opinion
Folosind serviciul second opinion ne puteți trimite RMN-uri, CT -uri, angiografii, fișiere .pdf, documente medicale. Astfel vă vom putea da o opinie neurochirurgicală, fără ca aceasta să poată înlocui un consult de specialitate. Răspunsurile vor fi date prin e-mail în cel mai scurt timp posibil (de obicei în mai putin de 24 de ore, dar nu mai mult de 48 de ore). Second opinion – Neurohope este un serviciu gratuit. www.neurohope.ro |
PiHole
Last Updated: Feb 18 2022 12:57, Started by
joystick
, Jun 07 2019 13:00
·
0
#1
Posted 07 June 2019 - 13:00
Salut,
Nu am gasit pe aici niciun topic legat de PiHole. As fi vrut sa va intreb care este parerea voastra despre acest lucru. Aveti? Ati folosit? Folositi? Care ar fi riscurile de securitate? https://pi-hole.net/ |
#2
Posted 07 June 2019 - 13:26
Riscurile vin odata cu actualizarea listelor.
Eu am icncercat dar nu-mi suporta NAS-ul |
#3
Posted 07 June 2019 - 13:46
e cel mai misto lucru de la inventarea reclamelor enervate incoace.
la ce riscuri de securitate te gandesti, DNS spoofing? Edited by laffin, 07 June 2019 - 13:46. |
#4
Posted 07 June 2019 - 13:52
Cand spun riscuri de securitate ma refer la orice ar putea sa apara (poate cei care aveti cunostinte mai bune de networking puteti sa ne spuneti).
|
#5
Posted 07 June 2019 - 13:54
joystick, on 07 iunie 2019 - 13:00, said:
Salut, Nu am gasit pe aici niciun topic legat de PiHole. As fi vrut sa va intreb care este parerea voastra despre acest lucru. Aveti? Ati folosit? Folositi? Care ar fi riscurile de securitate? https://pi-hole.net/ Pt. rezolutia efectiva a domeniilor face forward catre o retea de DNS servere consacrate (Cloudflare , Open DNS , chiar si Google daca vrei sa fie fara sens existenta pihole ) . In cazul meu personal ~25-30% din domeniile cerute de clienti reprezinta trafic catre diferite retele de ad-tracking care sunt blocate (asta nu inseamna neaparat ca nu vei mai vedea reclame deloc ci ca pe majoritatea nu iar pe cele pe care le vei vedea nu vor fi relame tintite personal pt. ca tracking-ul in mare parte va fi blocat). Blocat de asemenea va fi si traficul de telemetrie a la Win 10 , clienti spotify sau alt ttafic telemetrie care la fel e cu scopul de tracking ( evident totul depinde de listele la care esti abonat ). Una din limitarile acestui tip de ad blocking vs un addon browser (uBlockOrigin de ex.) e ca nu poate bloca inserturile de publicitate din video-urile youtube pe SmartTV sau clinetul nativ Android (vor fi reclame pt. publicul general nu tintite , motiv pt. care m-am trezit cu reclame PSD inaintea alegerilor de ex , dar tot vor fi ). Ca si resurse utilizate este foarte lightweight ; ruleaza intr-un VM Ubuntu pe NAS cu 512 MB RAM/30 GB HDD si doar 1 nucleu din cele 4 Atom @2GHz ale NAS-ului . Edited by me_iauras, 07 June 2019 - 14:14. |
#6
Posted 07 June 2019 - 14:00
stai linistit. credeam ca te referi la extraterestrii. il tii local, iar daca are cineva acces la el, inseamna ca ai alte probleme mai grave.
|
#7
Posted 07 June 2019 - 17:28
Mi-am instalat si eu PiHole ptr. ca am avut un Raspberry pi model B (cu 256k ram) nefolosit.
Merge foarte bine dar nu blocheaza reclamele de pe youtube pe smart TV, iar pe PC nu prea simt efectul ptr. ca isi face treaba uBlock Origin. Un lucru bun este ca poti sa adaugi foarte usor site-uri in blacklist. |
#8
Posted 07 June 2019 - 18:35
Hmmm... Cred ca trebuie sa mai incerc și eu o data pihole.... Ideea e ca prima oara mi-am prins urechile in microtik
|
#9
Posted 07 June 2019 - 20:15
Nu stiu exact care e legatura microtik cu pihole insa uite aici un tutorial pt. pihole pe Ubuntu 18.04 LTS (pt a avea garantia unui suport de lunga durata e indicat sa alegi versiunile Long Term Support) .
Pt. teste poti crea o masina virtuala pe propriul notebook/PC folosind VMWare Player/Workstation sau Virtual Box .(evident poti folosi docker daca ai experienta sau chiar un SBC Raspeberry Pi daca ai) In router nu trebuie decat sa schimbi server-ele DNS din cele deja folosite in IP-ul appliance-ului pihole . Fiindca domeniile blacklisted vin pe baza unor liste la care te abonezi te vei intalni ocazional cu domenii pe care chiar vrei sa le vizitezi dar care sunt blocate ; la inceput vei fi nevoit sa ii faci un mic training in sensul ca la incidentele de acest gen va trebui sa pui domeniul respectiv pe whitelist (se face simplu apasand un buton) insa pt. o persoana neinitiata poate parea ca ori nu ii merge conexiunea internet ori ca e ceva in neregula cu pihole-ul (saracu nu face decat sa respecte ce ii spun respectivele liste) Edited by me_iauras, 07 June 2019 - 20:16. |
#10
Posted 07 June 2019 - 21:21
Pai iti explic eu legatura...
Nu stiu exact unde trebuie sa pun IP-ul lui PI Hole . Poza 1: - la server? In campul rosu? - daca apas STATIC apare fereastra de deasupra. Poza 2: - la 192.168.0.0/24 vad ca nu am pus niciun server DNS - la 192.168.10.0/24 vad ca am DNS de google... Unde ar trebui deci sa pun IP-ul lui PI Hole? Attached Files |
|
#11
Posted 07 June 2019 - 21:34
In mod normal serverul DNS trebuie pus in configurarea VLAN-urilor ; de fapt in configurarea server-ului DHCP care anunta/deserveste retelele/VLAN-urlle respective , asta daca vrei ca toti clientii sa interogheze direct serverele respective DNS .
In cazul tau as spune ca in meniul din poza 2 ar trebui inlocuit DNS-ul Google (pe care apropo recomand sa-l inlocuiesti cu pihole cu forwarder Cloudflare1.1.1.1/1.0.0.1 si din ratiuni de viteza de raspuns si din ratiuni de anonimizare cautari fata de o companie care isi bazeaza busines-ul pe profilarea utilizatorilor si servirea de publicitate tintita) . In mom. asta din cate imi dau seama clientii tai (din VLAN-urile 10 si 20) fac query-uri DNS direct in DNS server-ele google vs. o retea obisnuita unde gateway-ul (router-ul) se comporta ca server DNS (de fapt doar un forwarder DNS dar pt. clienti nu conteaza). Un beneficiu minor al pihole ar fi ca poti adauga in fisierul host intern inregistrari personale de hostname-uri ; de ex. daca ai un NAS sau accesezi un calc. de pe alt calc nu mai depinzi de IP-uri sau WINS in cel mai bun caz ci iti poti pune tu ce hostname-uri vrei pt. device-urile tale in functie de rezervarile lor statice DHCP (sau dinamice daca folosesti functia de DHCP server din pihole) Edited by me_iauras, 07 June 2019 - 21:42. |
#12
Posted 07 June 2019 - 21:48
joystick, on 07 iunie 2019 - 21:21, said:
Pai iti explic eu legatura... Nu stiu exact unde trebuie sa pun IP-ul lui PI Hole . Poza 1: - la server? In campul rosu? - daca apas STATIC apare fereastra de deasupra. Static folosesti ca sa asignezi tot timpul acelasi ip unui device. Atentie totusi daca ai mai multe vlanuri: ori pui pihole-ul in toate vlanurile in care ai nevoie de serviciul asta (3 vlan-uri - 3 interfețe), ori folosesti niste rute pentru a ajunge dintr-un vlan in altul. Edited by MembruAnonim, 07 June 2019 - 21:52. |
#13
Posted 08 June 2019 - 07:57
Mulțumesc. O sa incerc sa reinstalez pihole și sa testez un pic.
|
#14
Posted 11 November 2020 - 22:50
salutare
am pierdut 1 zi..nu merge si pace nu porneste FLT ul si pace.pe orice SO ( vesiune Ubuntu l-as pune) am incercat cam tot ce am gasit pe net ( partea cu dns-ul care nu merge am rezolvat-o) il folosesc in VMWare. o pun pe un sistem cu esx ( sunt mai multe vm-uri ) dar de test am incercat pe un latop cu vmws |
#15
Posted 11 November 2020 - 23:33
ce erori ai?
sudo pihole -d mai jos un pihole ce merge pe un 20.04 care e de fapt o masina virtuala pe un synology: ogo@zeus:~$ cat /etc/*release* DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.1 LTS" NAME="Ubuntu" VERSION="20.04.1 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.1 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/" SUPPORT_URL="https://help.ubuntu.com/" BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/" PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy" VERSION_CODENAME=focal UBUNTU_CODENAME=focal ogo@zeus:~$ ogo@zeus:~$ sudo pihole -v Pi-hole version is v5.1.2 (Latest: v5.1.2) AdminLTE version is v5.1.1 (Latest: v5.1.1) FTL version is v5.2 (Latest: v5.2) |
|
#16
Posted 11 November 2020 - 23:37
Bine ai venit aici.
Ultimele linii din log FLT ce zic ? Sau din service-ul aferent? LE: vad ca e si ogo pe fir, deci ești pe maini bune Edited by wolfydRg, 11 November 2020 - 23:39. |
#17
Posted 12 November 2020 - 00:11
2 sec:
-rw-r--r-- 1 pihole pihole 20020 Nov 11 18:35 /var/log/pihole-FTL.log -----head of pihole-FTL.log------ [2020-11-11 12:05:49.412 4001M] Using log file /var/log/pihole-FTL.log [2020-11-11 12:05:49.414 4001M] ########## FTL started! ########## [2020-11-11 12:05:49.414 4001M] FTL branch: master [2020-11-11 12:05:49.414 4001M] FTL version: v5.2 [2020-11-11 12:05:49.414 4001M] FTL commit: dbd4a69 [2020-11-11 12:05:49.414 4001M] FTL date: 2020-08-09 22:09:43 +0100 [2020-11-11 12:05:49.414 4001M] FTL user: pihole [2020-11-11 12:05:49.414 4001M] Compiled for x86_64 (compiled on CI) using gcc (Debian 6.3.0-18+deb9u1) 6.3.0 20170516 [2020-11-11 12:05:49.414 4001M] Starting config file parsing (/etc/pihole/pihole-FTL.conf) [2020-11-11 12:05:49.414 4001M] SOCKET_LISTENING: only local [2020-11-11 12:05:49.415 4001M] AAAA_QUERY_ANALYSIS: Show AAAA queries [2020-11-11 12:05:49.415 4001M] MAXDBDAYS: max age for stored queries is 365 days [2020-11-11 12:05:49.415 4001M] RESOLVE_IPV6: Resolve IPv6 addresses [2020-11-11 12:05:49.415 4001M] RESOLVE_IPV4: Resolve IPv4 addresses [2020-11-11 12:05:49.415 4001M] DBINTERVAL: saving to DB file every minute [2020-11-11 12:05:49.415 4001M] DBFILE: Using /etc/pihole/pihole-FTL.db [2020-11-11 12:05:49.415 4001M] MAXLOGAGE: Importing up to 24.0 hours of log data [2020-11-11 12:05:49.415 4001M] PRIVACYLEVEL: Set to 0 [2020-11-11 12:05:49.415 4001M] IGNORE_LOCALHOST: Show queries from localhost [2020-11-11 12:05:49.415 4001M] BLOCKINGMODE: Null IPs for blocked domains [2020-11-11 12:05:49.415 4001M] ANALYZE_ONLY_A_AND_AAAA: Disabled. Analyzing all queries [2020-11-11 12:05:49.415 4001M] DBIMPORT: Importing history from database [2020-11-11 12:05:49.415 4001M] PIDFILE: Using /run/pihole-FTL.pid [2020-11-11 12:05:49.415 4001M] PORTFILE: Using /run/pihole-FTL.port [2020-11-11 12:05:49.415 4001M] SOCKETFILE: Using /run/pihole/FTL.sock [2020-11-11 12:05:49.415 4001M] SETUPVARSFILE: Using /etc/pihole/setupVars.conf [2020-11-11 12:05:49.415 4001M] MACVENDORDB: Using /etc/pihole/macvendor.db [2020-11-11 12:05:49.415 4001M] GRAVITYDB: Using /etc/pihole/gravity.db [2020-11-11 12:05:49.415 4001M] PARSE_ARP_CACHE: Active [2020-11-11 12:05:49.416 4001M] CNAME_DEEP_INSPECT: Active [2020-11-11 12:05:49.416 4001M] DELAY_STARTUP: No delay requested. [2020-11-11 12:05:49.416 4001M] NICE: Set process niceness to -10 (default) [2020-11-11 12:05:49.416 4001M] BLOCK_ESNI: Enabled, blocking _esni.{blocked domain} [2020-11-11 12:05:49.416 4001M] NAMES_FROM_NETDB: Enabled, trying to get names from network database [2020-11-11 12:05:49.416 4001M] Finished config file parsing -----tail of pihole-FTL.log------ [2020-11-11 18:35:47.969 10593M] RESOLVE_IPV6: Resolve IPv6 addresses [2020-11-11 18:35:47.969 10593M] RESOLVE_IPV4: Resolve IPv4 addresses [2020-11-11 18:35:47.969 10593M] DBINTERVAL: saving to DB file every minute [2020-11-11 18:35:47.969 10593M] DBFILE: Using /etc/pihole/pihole-FTL.db [2020-11-11 18:35:47.969 10593M] MAXLOGAGE: Importing up to 24.0 hours of log data [2020-11-11 18:35:47.970 10593M] PRIVACYLEVEL: Set to 0 [2020-11-11 18:35:47.970 10593M] IGNORE_LOCALHOST: Show queries from localhost [2020-11-11 18:35:47.970 10593M] BLOCKINGMODE: Null IPs for blocked domains [2020-11-11 18:35:47.970 10593M] ANALYZE_ONLY_A_AND_AAAA: Disabled. Analyzing all queries [2020-11-11 18:35:47.970 10593M] DBIMPORT: Importing history from database [2020-11-11 18:35:47.970 10593M] PIDFILE: Using /run/pihole-FTL.pid [2020-11-11 18:35:47.970 10593M] PORTFILE: Using /run/pihole-FTL.port [2020-11-11 18:35:47.970 10593M] SOCKETFILE: Using /run/pihole/FTL.sock [2020-11-11 18:35:47.970 10593M] SETUPVARSFILE: Using /etc/pihole/setupVars.conf [2020-11-11 18:35:47.970 10593M] MACVENDORDB: Using /etc/pihole/macvendor.db [2020-11-11 18:35:47.970 10593M] GRAVITYDB: Using /etc/pihole/gravity.db [2020-11-11 18:35:47.970 10593M] PARSE_ARP_CACHE: Active [2020-11-11 18:35:47.970 10593M] CNAME_DEEP_INSPECT: Active [2020-11-11 18:35:47.970 10593M] DELAY_STARTUP: No delay requested. [2020-11-11 18:35:47.971 10593M] NICE: Set process niceness to -10 (default) [2020-11-11 18:35:47.971 10593M] BLOCK_ESNI: Enabled, blocking _esni.{blocked domain} [2020-11-11 18:35:47.972 10593M] NAMES_FROM_NETDB: Enabled, trying to get names from network database [2020-11-11 18:35:47.972 10593M] Finished config file parsing [2020-11-11 18:35:47.973 10593M] Database version is 7 [2020-11-11 18:35:47.973 10593M] Database successfully initialized [2020-11-11 18:35:47.973 10593M] Imported 0 queries from the long-term database [2020-11-11 18:35:47.973 10593M] -> Total DNS queries: 0 [2020-11-11 18:35:47.973 10593M] -> Cached DNS queries: 0 [2020-11-11 18:35:47.973 10593M] -> Forwarded DNS queries: 0 [2020-11-11 18:35:47.973 10593M] -> Blocked DNS queries: 0 [2020-11-11 18:35:47.973 10593M] -> Unknown DNS queries: 0 [2020-11-11 18:35:47.973 10593M] -> Unique domains: 0 [2020-11-11 18:35:47.973 10593M] -> Unique clients: 0 [2020-11-11 18:35:47.973 10593M] -> Known forward destinations: 0 [2020-11-11 18:35:47.973 10593M] Successfully accessed setupVars.conf FTL Information The FTL service is offline! ogo, on 11 noiembrie 2020 - 23:33, said:
ce erori ai? sudo pihole -d mai jos un pihole ce merge pe un 20.04 care e de fapt o masina virtuala pe un synology: ogo@zeus:~$ cat /etc/*release* DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.1 LTS" NAME="Ubuntu" VERSION="20.04.1 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.1 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/" SUPPORT_URL="https://help.ubuntu.com/" BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/" PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy" VERSION_CODENAME=focal UBUNTU_CODENAME=focal ogo@zeus:~$ ogo@zeus:~$ sudo pihole -v Pi-hole version is v5.1.2 (Latest: v5.1.2) AdminLTE version is v5.1.1 (Latest: v5.1.1) FTL version is v5.2 (Latest: v5.2) arata identic cu al tau! 100% This process collects information from your Pi-hole, and optionally uploads it to a unique and random directory on tricorder.pi-hole.net. The intent of this script is to allow users to self-diagnose their installations. This is accomplished by running tests against our software and providing the user with links to FAQ articles when a problem is detected. Since we are a small team and Pi-hole has been growing steadily, it is our hope that this will help us spend more time on development. NOTE: All log files auto-delete after 48 hours and ONLY the Pi-hole developers can access your data via the given token. We have taken these extra steps to secure your data and will work to further reduce any personal information gathered. *** [ INITIALIZING ] [i] 2020-11-11:22:08:51 debug log has been initialized. *** [ INITIALIZING ] Sourcing setup variables [i] Sourcing /etc/pihole/setupVars.conf... *** [ DIAGNOSING ]: Core version [i] Core: v5.1.2 (https://discourse.pi...ate-pi-hole/249) [i] Remotes: origin https://github.com/pi-hole/pi-hole.git (fetch) origin https://github.com/pi-hole/pi-hole.git (push) [i] Branch: master [i] Commit: v5.1.2-0-g6b536b7 *** [ DIAGNOSING ]: Web version [i] Web: v5.1.1 (https://discourse.pi...ate-pi-hole/249) [i] Remotes: origin https://github.com/p...le/AdminLTE.git (fetch) origin https://github.com/p...le/AdminLTE.git (push) [i] Branch: master [i] Commit: v5.1.1-0-ga03d1bd *** [ DIAGNOSING ]: FTL version [✓] FTL: v5.2 *** [ DIAGNOSING ]: lighttpd version [i] 1.4.55 *** [ DIAGNOSING ]: php version [i] 7.4.3 *** [ DIAGNOSING ]: Operating system [✓] Distro: Ubuntu [✓] Version: 20.04 *** [ DIAGNOSING ]: SELinux [i] SELinux not detected *** [ DIAGNOSING ]: Processor [i] x86_64 *** [ DIAGNOSING ]: Networking [✓] IPv4 address(es) bound to the ens33 interface: 192.168.3.93/24 matches the IP found in /etc/pihole/setupVars.conf [✓] IPv6 address(es) bound to the ens33 interface: 2a02:2f0a:4500:8200::4 does not match the IP found in /etc/pihole/setupVars.conf (https://discourse.pi...or-pi-hole/2127) 2a02:2f0a:4500:8200:20c:29ff:fe72:d245 matches the IP found in /etc/pihole/setupVars.conf 2a02:2f0a:4500:8200:d81e:b21d:b976:6e3 does not match the IP found in /etc/pihole/setupVars.conf (https://discourse.pi...or-pi-hole/2127) fe80::9abb:4b81:b873:a0e0 does not match the IP found in /etc/pihole/setupVars.conf (https://discourse.pi...or-pi-hole/2127) fe80::20c:29ff:fe72:d245 does not match the IP found in /etc/pihole/setupVars.conf (https://discourse.pi...or-pi-hole/2127) ^ Please note that you may have more than one IP address listed. As long as one of them is green, and it matches what is in /etc/pihole/setupVars.conf, there is no need for concern. The link to the FAQ is for an issue that sometimes occurs when the IPv6 address changes, which is why we check for it. [i] Default IPv4 gateway: 192.168.3.1 * Pinging 192.168.3.1... [✓] Gateway responded. [i] Default IPv6 gateway: fe80::1 fe80::1 * Pinging fe80::1 fe80::1... [✗] Gateway did not respond. (https://discourse.pi...or-pi-hole/3546) *** [ DIAGNOSING ]: Ports in use 127.0.0.1:953 named (IPv4) [53] is in use by named (https://docs.pi-hole...quisites/#ports) [53] is in use by named (https://docs.pi-hole...quisites/#ports) [53] is in use by named (https://docs.pi-hole...quisites/#ports) [53] is in use by named (https://docs.pi-hole...quisites/#ports) [53] is in use by named (https://docs.pi-hole...quisites/#ports) [53] is in use by named (https://docs.pi-hole...quisites/#ports) [53] is in use by named (https://docs.pi-hole...quisites/#ports) [53] is in use by named (https://docs.pi-hole...quisites/#ports) [53] is in use by named (https://docs.pi-hole...quisites/#ports) [::1]:953 named (IPv6) *:22 sshd (IPv4) *:22 sshd (IPv6) *:10000 miniserv.p (IPv4) [80] is in use by lighttpd [80] is in use by lighttpd *** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain [✗] Failed to resolve prod-m-node-1112.nexage.com via localhost (127.0.0.1) [✓] prod-m-node-1112.nexage.com is m-node-alb-ssl-1112-466259459.us-east-1.elb.amazonaws.com. 52.206.58.115 34.227.4.16 18.211.110.252 54.159.212.63 34.224.151.115 35.174.52.131 52.73.108.144 34.201.158.250 via Pi-hole (192.168.3.93) [✓] doubleclick.com is 172.217.20.14 via a remote, public DNS server (8.8.8.8) *** [ DIAGNOSING ]: Name resolution (IPv6) using a random blocked domain and a known ad-serving domain [✓] iwangetherrr.com is via localhost (::1) [✗] Failed to resolve iwangetherrr.com via Pi-hole (2a02:2f0a:4500:8200:20c:29ff:fe72:d245) [✓] doubleclick.com is 2a00:1450:400d:805::200e via a remote, public DNS server (2001:4860:4860::8888) *** [ DIAGNOSING ]: Pi-hole processes [✓] lighttpd daemon is active [✓] pihole-FTL daemon is active *** [ DIAGNOSING ]: Setup variables PIHOLE_INTERFACE=ens33 IPV4_ADDRESS=192.168.3.93/24 IPV6_ADDRESS=2a02:2f0a:4500:8200:20c:29ff:fe72:d245 PIHOLE_DNS_1=8.8.8.8 PIHOLE_DNS_2=8.8.4.4 QUERY_LOGGING=true INSTALL_WEB_SERVER=true INSTALL_WEB_INTERFACE=true LIGHTTPD_ENABLED=true BLOCKING_ENABLED=true *** [ DIAGNOSING ]: Dashboard and block page [✓] Block page X-Header: X-Pi-hole: A black hole for Internet advertisements. [✓] Web interface X-Header: X-Pi-hole: The Pi-hole Web interface is working! *** [ DIAGNOSING ]: Gravity List and Database -rw-rw-r-- 1 pihole pihole 5210112 Nov 11 12:10 /etc/pihole/gravity.db *** [ DIAGNOSING ]: Info table property value -------------------- ---------------------------------------- version 12 updated 1605096626 gravity_count 86511 Last gravity run finished at: Wed 11 Nov 2020 12:10:26 PM UTC ----- First 10 Gravity Domains ----- localhost.localdomain n2019cov.XXXXXXXXXapp.com webmail-who-int.XXXXXXXXXapp.com 010sec.com 01mspmd5yalky8.com 0byv9mgbn0.com ns6.0pendns.org dns.0pengl.com ios.0pengl.com 0x4fc271.tk *** [ DIAGNOSING ]: Groups id enabled name date_added date_modified description ---- ------- -------------------------------------------------- ------------------- ------------------- -------------------------------------------------- 0 1 Default 2020-11-11 09:53:44 2020-11-11 09:53:44 The default group *** [ DIAGNOSING ]: Domainlist (0/1 = exact white-/blacklist, 2/3 = regex white-/blacklist) id type enabled group_ids domain date_added date_modified comment ---- ---- ------- ------------ ---------------------------------------------------------------------------------------------------- ------------------- ------------------- -------------------------------------------------- 2 1 1 0 www.youtube.com 2020-11-11 10:10:45 2020-11-11 10:13:12 *** [ DIAGNOSING ]: Clients *** [ DIAGNOSING ]: Adlists id enabled group_ids address date_added date_modified comment ---- ------- ------------ ---------------------------------------------------------------------------------------------------- ------------------- ------------------- -------------------------------------------------- 1 1 0 https://raw.githubus...ts/master/hosts 2020-11-11 09:53:44 2020-11-11 09:53:44 Migrated from /etc/pihole/adlists.list 2 1 0 https://mirror1.malw...les/justdomains 2020-11-11 09:53:44 2020-11-11 09:53:44 Migrated from /etc/pihole/adlists.list *** [ DIAGNOSING ]: contents of /etc/pihole -rw-r--r-- 1 root root 134 Nov 11 12:10 /etc/pihole/local.list 192.168.3.93 ubuntu 2a02:2f0a:4500:8200:20c:29ff:fe72:d245 ubuntu 192.168.3.93 pi.hole 2a02:2f0a:4500:8200:20c:29ff:fe72:d245 pi.hole -rw-r--r-- 1 root root 238 Nov 11 11:58 /etc/pihole/logrotate /var/log/pihole.log { su root syslog daily copytruncate rotate 5 compress delaycompress notifempty nomail } /var/log/pihole-FTL.log { su root syslog weekly copytruncate rotate 3 compress delaycompress notifempty nomail } -rw-rw-r-- 1 pihole root 15 Nov 11 11:58 /etc/pihole/pihole-FTL.conf PRIVACYLEVEL=0 *** [ DIAGNOSING ]: contents of /etc/dnsmasq.d -rw-r--r-- 1 root root 1386 Nov 11 11:58 /etc/dnsmasq.d/01-pihole.conf addn-hosts=/etc/pihole/local.list addn-hosts=/etc/pihole/custom.list localise-queries no-resolv cache-size=10000 log-queries log-facility=/var/log/pihole.log local-ttl=2 log-async server=8.8.8.8 server=8.8.4.4 interface=ens33 server=/use-application-dns.net/ *** [ DIAGNOSING ]: contents of /etc/lighttpd -rw-r--r-- 1 root root 0 Nov 11 11:58 /etc/lighttpd/external.conf -rw-r--r-- 1 root root 4066 Nov 11 11:58 /etc/lighttpd/lighttpd.conf server.modules = ( "mod_access", "mod_accesslog", "mod_auth", "mod_expire", "mod_compress", "mod_redirect", "mod_setenv", "mod_rewrite" ) server.document-root = "/var/www/html" server.error-handler-404 = "/pihole/index.php" server.upload-dirs = ( "/var/cache/lighttpd/uploads" ) server.errorlog = "/var/log/lighttpd/error.log" server.pid-file = "/run/lighttpd.pid" server.username = "www-data" server.groupname = "www-data" server.port = 80 accesslog.filename = "/var/log/lighttpd/access.log" accesslog.format = "%{%s}t|%V|%r|%s|%b" index-file.names = ( "index.php", "index.html", "index.lighttpd.html" ) url.access-deny = ( "~", ".inc", ".md", ".yml", ".ini" ) static-file.exclude-extensions = ( ".php", ".pl", ".fcgi" ) compress.cache-dir = "/var/cache/lighttpd/compress/" compress.filetype = ( "application/json", "application/vnd.ms-fontobject", "application/xml", "font/eot", "font/opentype", "font/otf", "font/ttf", "image/bmp", "image/svg+xml", "image/vnd.microsoft.icon", "image/x-icon", "text/css", "text/html", "text/javascript", "text/plain", "text/xml" ) mimetype.assign = ( ".ico" => "image/x-icon", ".jpeg" => "image/jpeg", ".jpg" => "image/jpeg", ".png" => "image/png", ".svg" => "image/svg+xml", ".css" => "text/css; charset=utf-8", ".html" => "text/html; charset=utf-8", ".js" => "text/javascript; charset=utf-8", ".json" => "application/json; charset=utf-8", ".map" => "application/json; charset=utf-8", ".txt" => "text/plain; charset=utf-8", ".eot" => "application/vnd.ms-fontobject", ".otf" => "font/otf", ".ttc" => "font/collection", ".ttf" => "font/ttf", ".woff" => "font/woff", ".woff2" => "font/woff2" ) include_shell "/usr/share/lighttpd/use-ipv6.pl " + server.port include_shell "find /etc/lighttpd/conf-enabled -name '*.conf' -a ! -name 'letsencrypt.conf' -printf 'include \"%p\" ' 2>/dev/null" $HTTP["url"] =~ "^/admin/" { setenv.add-response-header = ( "X-Pi-hole" => "The Pi-hole Web interface is working!", "X-Frame-Options" => "DENY" ) $HTTP["url"] =~ "\.(eot|otf|tt[cf]|woff2?)$" { setenv.add-response-header = ( "Access-Control-Allow-Origin" => "*" ) } } $HTTP["url"] =~ "^/admin/\.(.*)" { url.access-deny = ("") } expire.url = ( "" => "access plus 0 seconds" ) include_shell "cat external.conf 2>/dev/null" *** [ DIAGNOSING ]: contents of /etc/cron.d -rw-r--r-- 1 root root 1755 Nov 11 11:58 /etc/cron.d/pihole 45 3 * * 7 root PATH="$PATH:/usr/sbin:/usr/local/bin/" pihole updateGravity >/var/log/pihole_updateGravity.log || cat /var/log/pihole_updateGravity.log 00 00 * * * root PATH="$PATH:/usr/sbin:/usr/local/bin/" pihole flush once quiet @reboot root /usr/sbin/logrotate /etc/pihole/logrotate */10 * * * * root PATH="$PATH:/usr/sbin:/usr/local/bin/" pihole updatechecker local 25 15 * * * root PATH="$PATH:/usr/sbin:/usr/local/bin/" pihole updatechecker remote @reboot root PATH="$PATH:/usr/sbin:/usr/local/bin/" pihole updatechecker remote reboot *** [ DIAGNOSING ]: contents of /var/log/lighttpd -rw-r--r-- 1 www-data www-data 13994 Nov 11 22:08 /var/log/lighttpd/error.log 2020-11-11 09:53:29: (server.c.1488) server started (lighttpd/1.4.55) 2020-11-11 09:53:40: (server.c.1970) server stopped by UID = 0 PID = 1 2020-11-11 09:53:41: (server.c.1488) server started (lighttpd/1.4.55) 2020-11-11 09:59:05: (server.c.1970) server stopped by UID = 0 PID = 1 2020-11-11 09:59:18: (server.c.1488) server started (lighttpd/1.4.55) 2020-11-11 10:00:19: (server.c.1970) server stopped by UID = 0 PID = 1 2020-11-11 10:00:20: (server.c.1488) server started (lighttpd/1.4.55) 2020-11-11 10:04:03: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning: Executing sudo pihole restartdns reload-lists failed. in /var/www/html/admin/scripts/pi-hole/php/func.php on line 79 2020-11-11 10:10:23: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning: Executing sudo pihole restartdns reload-lists failed. in /var/www/html/admin/scripts/pi-hole/php/func.php on line 79 2020-11-11 10:10:45: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning: Executing sudo pihole restartdns reload-lists failed. in /var/www/html/admin/scripts/pi-hole/php/func.php on line 79 2020-11-11 10:12:54: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning: Executing sudo pihole restartdns reload-lists failed. in /var/www/html/admin/scripts/pi-hole/php/func.php on line 79 2020-11-11 10:13:12: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning: Executing sudo pihole restartdns reload-lists failed. in /var/www/html/admin/scripts/pi-hole/php/func.php on line 79 2020-11-11 10:21:01: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning: fopen(/etc/pihole/custom.list): failed to open stream: No such file or directory in /var/www/html/admin/scripts/pi-hole/php/func.php on line 101 2020-11-11 10:21:39: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice: Trying to access array offset on value of type null in /var/www/html/admin/settings.php on line 17 2020-11-11 10:21:39: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice: Trying to access array offset on value of type null in /var/www/html/admin/settings.php on line 17 2020-11-11 10:22:00: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice: Trying to access array offset on value of type null in /var/www/html/admin/settings.php on line 17 2020-11-11 10:22:00: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice: Trying to access array offset on value of type null in /var/www/html/admin/settings.php on line 17 2020-11-11 10:22:17: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice: Trying to access array offset on value of type null in /var/www/html/admin/settings.php on line 17 2020-11-11 10:22:17: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice: Trying to access array offset on value of type null in /var/www/html/admin/settings.php on line 17 2020-11-11 10:23:05: (server.c.1970) server stopped by UID = 0 PID = 1 2020-11-11 10:23:18: (server.c.1488) server started (lighttpd/1.4.55) 2020-11-11 10:23:41: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice: Trying to access array offset on value of type null in /var/www/html/admin/settings.php on line 17 2020-11-11 10:23:41: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice: Trying to access array offset on value of type null in /var/www/html/admin/settings.php on line 17 2020-11-11 10:33:31: (server.c.1970) server stopped by UID = 0 PID = 1 2020-11-11 11:35:28: (server.c.1488) server started (lighttpd/1.4.55) *** [ DIAGNOSING ]: contents of /var/log -rw-r--r-- 1 pihole pihole 20020 Nov 11 18:35 /var/log/pihole-FTL.log -----head of pihole-FTL.log------ [2020-11-11 12:05:49.412 4001M] Using log file /var/log/pihole-FTL.log [2020-11-11 12:05:49.414 4001M] ########## FTL started! ########## [2020-11-11 12:05:49.414 4001M] FTL branch: master [2020-11-11 12:05:49.414 4001M] FTL version: v5.2 [2020-11-11 12:05:49.414 4001M] FTL commit: dbd4a69 [2020-11-11 12:05:49.414 4001M] FTL date: 2020-08-09 22:09:43 +0100 [2020-11-11 12:05:49.414 4001M] FTL user: pihole [2020-11-11 12:05:49.414 4001M] Compiled for x86_64 (compiled on CI) using gcc (Debian 6.3.0-18+deb9u1) 6.3.0 20170516 [2020-11-11 12:05:49.414 4001M] Starting config file parsing (/etc/pihole/pihole-FTL.conf) [2020-11-11 12:05:49.414 4001M] SOCKET_LISTENING: only local [2020-11-11 12:05:49.415 4001M] AAAA_QUERY_ANALYSIS: Show AAAA queries [2020-11-11 12:05:49.415 4001M] MAXDBDAYS: max age for stored queries is 365 days [2020-11-11 12:05:49.415 4001M] RESOLVE_IPV6: Resolve IPv6 addresses [2020-11-11 12:05:49.415 4001M] RESOLVE_IPV4: Resolve IPv4 addresses [2020-11-11 12:05:49.415 4001M] DBINTERVAL: saving to DB file every minute [2020-11-11 12:05:49.415 4001M] DBFILE: Using /etc/pihole/pihole-FTL.db [2020-11-11 12:05:49.415 4001M] MAXLOGAGE: Importing up to 24.0 hours of log data [2020-11-11 12:05:49.415 4001M] PRIVACYLEVEL: Set to 0 [2020-11-11 12:05:49.415 4001M] IGNORE_LOCALHOST: Show queries from localhost [2020-11-11 12:05:49.415 4001M] BLOCKINGMODE: Null IPs for blocked domains [2020-11-11 12:05:49.415 4001M] ANALYZE_ONLY_A_AND_AAAA: Disabled. Analyzing all queries [2020-11-11 12:05:49.415 4001M] DBIMPORT: Importing history from database [2020-11-11 12:05:49.415 4001M] PIDFILE: Using /run/pihole-FTL.pid [2020-11-11 12:05:49.415 4001M] PORTFILE: Using /run/pihole-FTL.port [2020-11-11 12:05:49.415 4001M] SOCKETFILE: Using /run/pihole/FTL.sock [2020-11-11 12:05:49.415 4001M] SETUPVARSFILE: Using /etc/pihole/setupVars.conf [2020-11-11 12:05:49.415 4001M] MACVENDORDB: Using /etc/pihole/macvendor.db [2020-11-11 12:05:49.415 4001M] GRAVITYDB: Using /etc/pihole/gravity.db [2020-11-11 12:05:49.415 4001M] PARSE_ARP_CACHE: Active [2020-11-11 12:05:49.416 4001M] CNAME_DEEP_INSPECT: Active [2020-11-11 12:05:49.416 4001M] DELAY_STARTUP: No delay requested. [2020-11-11 12:05:49.416 4001M] NICE: Set process niceness to -10 (default) [2020-11-11 12:05:49.416 4001M] BLOCK_ESNI: Enabled, blocking _esni.{blocked domain} [2020-11-11 12:05:49.416 4001M] NAMES_FROM_NETDB: Enabled, trying to get names from network database [2020-11-11 12:05:49.416 4001M] Finished config file parsing -----tail of pihole-FTL.log------ [2020-11-11 18:35:47.969 10593M] RESOLVE_IPV6: Resolve IPv6 addresses [2020-11-11 18:35:47.969 10593M] RESOLVE_IPV4: Resolve IPv4 addresses [2020-11-11 18:35:47.969 10593M] DBINTERVAL: saving to DB file every minute [2020-11-11 18:35:47.969 10593M] DBFILE: Using /etc/pihole/pihole-FTL.db [2020-11-11 18:35:47.969 10593M] MAXLOGAGE: Importing up to 24.0 hours of log data [2020-11-11 18:35:47.970 10593M] PRIVACYLEVEL: Set to 0 [2020-11-11 18:35:47.970 10593M] IGNORE_LOCALHOST: Show queries from localhost [2020-11-11 18:35:47.970 10593M] BLOCKINGMODE: Null IPs for blocked domains [2020-11-11 18:35:47.970 10593M] ANALYZE_ONLY_A_AND_AAAA: Disabled. Analyzing all queries [2020-11-11 18:35:47.970 10593M] DBIMPORT: Importing history from database [2020-11-11 18:35:47.970 10593M] PIDFILE: Using /run/pihole-FTL.pid [2020-11-11 18:35:47.970 10593M] PORTFILE: Using /run/pihole-FTL.port [2020-11-11 18:35:47.970 10593M] SOCKETFILE: Using /run/pihole/FTL.sock [2020-11-11 18:35:47.970 10593M] SETUPVARSFILE: Using /etc/pihole/setupVars.conf [2020-11-11 18:35:47.970 10593M] MACVENDORDB: Using /etc/pihole/macvendor.db [2020-11-11 18:35:47.970 10593M] GRAVITYDB: Using /etc/pihole/gravity.db [2020-11-11 18:35:47.970 10593M] PARSE_ARP_CACHE: Active [2020-11-11 18:35:47.970 10593M] CNAME_DEEP_INSPECT: Active [2020-11-11 18:35:47.970 10593M] DELAY_STARTUP: No delay requested. [2020-11-11 18:35:47.971 10593M] NICE: Set process niceness to -10 (default) [2020-11-11 18:35:47.971 10593M] BLOCK_ESNI: Enabled, blocking _esni.{blocked domain} [2020-11-11 18:35:47.972 10593M] NAMES_FROM_NETDB: Enabled, trying to get names from network database [2020-11-11 18:35:47.972 10593M] Finished config file parsing [2020-11-11 18:35:47.973 10593M] Database version is 7 [2020-11-11 18:35:47.973 10593M] Database successfully initialized [2020-11-11 18:35:47.973 10593M] Imported 0 queries from the long-term database [2020-11-11 18:35:47.973 10593M] -> Total DNS queries: 0 [2020-11-11 18:35:47.973 10593M] -> Cached DNS queries: 0 [2020-11-11 18:35:47.973 10593M] -> Forwarded DNS queries: 0 [2020-11-11 18:35:47.973 10593M] -> Blocked DNS queries: 0 [2020-11-11 18:35:47.973 10593M] -> Unknown DNS queries: 0 [2020-11-11 18:35:47.973 10593M] -> Unique domains: 0 [2020-11-11 18:35:47.973 10593M] -> Unique clients: 0 [2020-11-11 18:35:47.973 10593M] -> Known forward destinations: 0 [2020-11-11 18:35:47.973 10593M] Successfully accessed setupVars.conf *** [ DIAGNOSING ]: contents of /dev/shm -rw------- 1 pihole pihole 331776 Nov 11 18:35 /dev/shm/FTL-clients -rw------- 1 pihole pihole 144 Nov 11 18:35 /dev/shm/FTL-counters -rw------- 1 pihole pihole 4096 Nov 11 18:35 /dev/shm/FTL-dns-cache -rw------- 1 pihole pihole 98304 Nov 11 18:35 /dev/shm/FTL-domains -rw------- 1 pihole pihole 48 Nov 11 18:35 /dev/shm/FTL-lock -rw------- 1 pihole pihole 45056 Nov 11 18:35 /dev/shm/FTL-overTime -rw------- 1 pihole pihole 4096 Nov 11 18:35 /dev/shm/FTL-per-client-regex -rw------- 1 pihole pihole 262144 Nov 11 18:35 /dev/shm/FTL-queries -rw------- 1 pihole pihole 12 Nov 11 18:35 /dev/shm/FTL-settings -rw------- 1 pihole pihole 4096 Nov 11 18:35 /dev/shm/FTL-strings -rw------- 1 pihole pihole 4096 Nov 11 18:35 /dev/shm/FTL-upstreams *** [ DIAGNOSING ]: Locale LANG=en_US.UTF-8 *** [ DIAGNOSING ]: Pi-hole log -rw-r--r-- 1 pihole pihole 0 Nov 11 18:35 /var/log/pihole.log -----head of pihole.log------ ******************************************** ******************************************** [✓] ** FINISHED DEBUGGING! ** * The debug log can be uploaded to tricorder.pi-hole.net for sharing with developers only. * For more information, see: https://pi-hole.net/...raspberry-pi-3/ * If available, we'll use openssl to upload the log, otherwise it will fall back to netcat. * Log will NOT be uploaded to tricorder. * A local copy of the debug log can be found at: /var/log/pihole_debug.log |
#18
Posted 12 November 2020 - 00:16
sudo service pihole-FTL restartce zice? fisierul /var/run/pihole/ exista? daca nu creaza-l si sa fie detinut de userul pihole Edited by ogo, 12 November 2020 - 00:16. |
Anunturi
▶ 0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users