Remove Pi-hole


#1

Although I like the idea of Pi-hole, my internal network almost become unusable since I installed Pi-hole. So I want to completely remove it from my Synology, and later re-install it on a Pi.

What is the best way to remove this?


#2

Sorry to hear that! pihole uninstsall should get you where you need, though uncertain if it is the same on the Synology NAS, as we don’t officially support that. Getting it working there has largely been a community effort.

Out of interest, what kind of issues are you seeing that are making your network unusable?


#3

It slows doen the internal network so much that I have to wait several minutes (10+ now) to open a connection to another servicerunning (Logitech Mediaserver, Domoticz). Even accessing with SSH to the NAS becomes almost impossible. Also the admin page for Pi-hole itself takes forever.


#4

Hmm OK, thanks for the feedback, it’s certainly interesting… though I’ve never noticed it myself.

I’m going to take a guess that it’s down to limited memory on the NAS itself, what does the memory usage show on the Admin page?


#5

Last time I could access the admin page it was around 90%. Not sure how much memory this NAS has. I believe it’s about 512Mb.


#6

Do you have anything else installed on the NAS aside from the standard synology stuff and Pi-hole? You may be asking too much of it! :slight_smile:


#7

I’ve got Domoticz running and the Logitech Media server. That is the reason I want to remove Pi-hole and someday later reintall it on a Pi (when I have a spare one).


#8

You should just be able to use pihole uninstall, but let’s ping @bakman2 and see if he can offer any other advice before you do that…


#9

Will wait for him :slight_smile: Thanks


#10

If you uninstall chroot via the dsm interface, pihole should be gone.


#11

Will be trying that… If I ever come in the dsm interface. :slight_smile:


#12

It sounds like your network setup is not configured properly. Did you verify the network interface on the system you are trying to access DSM from ? ipconfig /all or ifconfig if on linux.


#13

It has been working untill yesterday.

This is what I get when using ifconfig (on Mac)

lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
options=1203<RXCSUM,TXCSUM,TXSTATUS,SW_TIMESTAMP>
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
nd6 options=201<PERFORMNUD,DAD>
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=10b<RXCSUM,TXCSUM,VLAN_HWTAGGING,AV>
ether c8:2a:14:22:26:e0
inet6 fe80::14d8:2029:bbd8:6564%en0 prefixlen 64 secured scopeid 0x4
inet 192.168.0.15 netmask 0xffffff00 broadcast 192.168.0.255
nd6 options=201<PERFORMNUD,DAD>
media: autoselect (100baseTX )
status: active
en1: flags=8823<UP,BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 1500
ether 10:9a:dd:a5:87:91
nd6 options=201<PERFORMNUD,DAD>
media: autoselect ()
status: inactive
fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 4078
lladdr c8:2a:14:ff:fe:8c:77:0a
nd6 options=201<PERFORMNUD,DAD>
media: autoselect
status: inactive
en2: flags=963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX> mtu 1500
options=60<TSO4,TSO6>
ether d2:00:18:c7:70:a0
media: autoselect
status: inactive
bridge0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=63<RXCSUM,TXCSUM,TSO4,TSO6>
ether d2:00:18:c7:70:a0
Configuration:
id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
ipfilter disabled flags 0x2
member: en2 flags=3<LEARNING,DISCOVER>
ifmaxaddr 0 port 7 priority 0 path cost 0
nd6 options=201<PERFORMNUD,DAD>
media:
status: inactive
p2p0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 2304
ether 02:9a:dd:a5:87:91
media: autoselect
status: inactive
utun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 2000
inet6 fe80::7c4c:335e:7aaa:46b0%utun0 prefixlen 64 scopeid 0xa
nd6 options=201<PERFORMNUD,DAD>


#14

Finally, after restarting the Synology, and running the webinterface when it was powerd up, I could remove CHROOT and therefore Pi-Hole.

next thing is getting another Pi to get it running on again. Thanks for the help.