19-Jul-2019, 02:52 PM
Pages: 1 2
20-Apr-2020, 01:00 PM
Just as an update on this, hopefully of use to someone.... there have been a couple of updates and I now have a better understanding of what is happening and to fix.
1. When installing pihole, choose YES to install admin interface and NO to install lighttpd
2. The snakeoil firmware upgrade process replaces the contents of /var/www, deleting all pihole web admin files (not data)
3. Workaround. Make a copy of /var/www/html somewhere else (home directory)
- after upgrade, copy ~/html back to /var/www
For pihole admin, use the full path http://x.x.x.x/html/admin/index.php
For snakeoil admin use http://x.x.x.x/
1. When installing pihole, choose YES to install admin interface and NO to install lighttpd
2. The snakeoil firmware upgrade process replaces the contents of /var/www, deleting all pihole web admin files (not data)
3. Workaround. Make a copy of /var/www/html somewhere else (home directory)
- after upgrade, copy ~/html back to /var/www
For pihole admin, use the full path http://x.x.x.x/html/admin/index.php
For snakeoil admin use http://x.x.x.x/
20-Apr-2020, 01:16 PM
(20-Apr-2020, 01:00 PM)davem Wrote: [ -> ]For pihole admin, use the full path http://x.x.x.x/html/admin/index.phpI'll not recommend running pi-hole on the Snakeoil machine as it's basically the DNS server that'll run on your network. Depending on how many clients you have in your setup, the number of DNS queries can be huge. e.g. this is mine:
For snakeoil admin use http://x.x.x.x/
Long story short, there will be a lot of network sessions on pi-hole. This might affect the RT nature of Snakeoil playback... You're better off to run Pi-hole on a raspberry Pi, or in a virtual machine. Alternatively you can also run pfSense with pfBlocker-NG (I think this is better than pi-hole).
Pages: 1 2