Setting up Pi-hole

As this seems really popular
Does anyone notice a bottleneck with the raspberry pi?

Most speed tests on the pi's eth0 seem to max at ~70Mbps download :confused: ref ref2
Raspberrypi's still use internal ethernet over USB? (check dmesg | grep eth0)
Code: 
smsc95xx v1.0.4
smsc95xx 1-1.1:1.0: eth0: register 'smsc95xx' at usb-bcm2708_usb-1.1, smsc95xx USB 2.0 Ethernet
 
The amount of traffic that DNS generates is tiny and it uses very little bandwidth. There's no issues at all with the ethernet port on the RPi.

My Pi has been up for about 5 days and the total traffic on eth0 is 166Mb RX, 48.4Mb TX. That includes the traffic generated by a couple of 'apt-get update' and traffic to the Pi-Hole web interface.

Code: 
root@rapihole:~:$ ifconfig eth0
eth0      Link encap:Ethernet  HWaddr b8:27:eb:df:ba:ca  
          inet addr:192.168.8.2  Bcast:192.168.8.255  Mask:255.255.255.0
          inet6 addr: fe80::9e92:890d:ac63:b7db/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1216829 errors:0 dropped:103422 overruns:0 frame:0
          TX packets:393919 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:174757388 (166.6 MiB)  TX bytes:50778894 (48.4 MiB)

root@rapihole:~:$ uptime
 17:28:15 up 5 days,  2:55,  1 user,  load average: 0.00, 0.00, 0.00
root@rapihole:~:$
 
the-evaluator;30480302 said:
The amount of traffic that DNS generates is tiny and it uses very little bandwidth. There's no issues at all with the ethernet port on the RPi.

My Pi has been up for about 5 days and the total traffic on eth0 is 166Mb RX, 48.4Mb TX. That includes the traffic generated by a couple of 'apt-get update' and traffic to the Pi-Hole web interface.

Code: 
root@rapihole:~:$ ifconfig eth0
eth0      Link encap:Ethernet  HWaddr b8:27:eb:df:ba:ca  
          inet addr:192.168.8.2  Bcast:192.168.8.255  Mask:255.255.255.0
          inet6 addr: fe80::9e92:890d:ac63:b7db/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1216829 errors:0 dropped:103422 overruns:0 frame:0
          TX packets:393919 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:174757388 (166.6 MiB)  TX bytes:50778894 (48.4 MiB)

root@rapihole:~:$ uptime
 17:28:15 up 5 days,  2:55,  1 user,  load average: 0.00, 0.00, 0.00
root@rapihole:~:$
Click to expand...
Ah cool

I thought this project was one of the ones where you use the rpi as a gateway/proxy like SquidGuard. :)
 
I run it manually when I do an apt-get update && apt-get upgrade. Personally I wouldn't do it unattended because a major version upgrade put password protection on the web interface and had I not seen mention of that at the consoel when doing the upgrade I'd be stuck for a while until I realised how to reset the password.

I have shoved 'pihole -g' and 'pihole restartdns' into a cron job that fires at 2am every day,
 
the-evaluator said:
I run it manually when I do an apt-get update && apt-get upgrade. Personally I wouldn't do it unattended because a major version upgrade put password protection on the web interface and had I not seen mention of that at the consoel when doing the upgrade I'd be stuck for a while until I realised how to reset the password.

I have shoved 'pihole -g' and 'pihole restartdns' into a cron job that fires at 2am every day,
Click to expand...
I've just changed mine from -up to -g. I didn't realise you could do the ad domain lists on their own. Nice one Thanks
 
You must log in or register to reply here.
Back
Top Bottom