SHARE
TWEET

overnite diversion

a guest Jun 27th, 2019 89 in 10 days
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1.  
  2. Jun 27 03:00:04 rc_service: service 684:notify_rc restart_dnsmasq
  3. Jun 27 03:00:04 custom_script: Running /jffs/scripts/service-event (args: restart dnsmasq) - max timeout = 120s
  4. Jun 27 03:00:04 custom_script: Running /jffs/scripts/hosts.postconf (args: /etc/hosts ) - max timeout = 120s
  5. Jun 27 03:00:04 custom_config: Appending content of /jffs/configs/dnsmasq.conf.add.
  6. Jun 27 03:00:04 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf ) - max timeout = 120s
  7. Jun 27 03:00:05 Diversion: restarted Dnsmasq to apply settings, from /jffs/scripts/dnsmasq.postconf
  8. Jun 27 03:00:07 Skynet: [#] 140112 IPs (+0) -- 1726 Ranges Banned (+0) || 5347 Inbound -- 2460 Outbound Connections Blocked! [save] [7s]
  9. Jun 27 03:00:14 dnsmasq[814]: Insecure DS reply received for net, could be bad domain configuration or lack of DNSSEC support from upstream DNS servers
  10. Jun 27 03:00:15 dnsmasq[814]: Insecure DS reply received for com, could be bad domain configuration or lack of DNSSEC support from upstream DNS servers
  11. Jun 27 03:00:15 dnsmasq[814]: Insecure DS reply received for co, could be bad domain configuration or lack of DNSSEC support from upstream DNS servers
  12. Jun 27 03:00:15 dnsmasq[814]: Insecure DS reply received for com, could be bad domain configuration or lack of DNSSEC support from upstream DNS servers
  13. Jun 27 03:00:15 dnsmasq[814]: Insecure DS reply received for org, could be bad domain configuration or lack of DNSSEC support from upstream DNS servers
  14. Jun 27 03:00:15 dnsmasq[814]: Insecure DS reply received for com, could be bad domain configuration or lack of DNSSEC support from upstream DNS servers
  15. Jun 27 03:00:15 dnsmasq[814]: Insecure DS reply received for net, could be bad domain configuration or lack of DNSSEC support from upstream DNS servers
  16. Jun 27 03:00:15 dnsmasq[814]: Insecure DS reply received for net, could be bad domain configuration or lack of DNSSEC support from upstream DNS servers
  17. Jun 27 03:00:15 dnsmasq[814]: Insecure DS reply received for net, could be bad domain configuration or lack of DNSSEC support from upstream DNS servers
  18. Jun 27 03:00:16 dnsmasq[814]: Insecure DS reply received for ca, could be bad domain configuration or lack of DNSSEC support from upstream DNS servers
  19. Jun 27 03:00:16 dnsmasq[814]: Insecure DS reply received for ca, could be bad domain configuration or lack of DNSSEC support from upstream DNS servers
  20. Jun 27 03:00:25 Skynet: [#] 140112 IPs (+0) -- 1726 Ranges Banned (+0) || 5347 Inbound -- 2460 Outbound Connections Blocked! [whitelist] [16s]
  21. Jun 27 03:01:24 Diversion: updated Small+ blocking list from 9 hosts files, 531255 domains are now blocked, from /opt/share/diversion/file/update-bf.div
RAW Paste Data
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy. OK, I Understand
 
Top