Open mechgt opened 4 months ago
cheehoong
commented
4 months ago Still possible to send me the LOGGING=$PIHOLE_FOLDER/log.txt ? Per App_Central_Developer_Guide_4.2.5_20231030.pdf, setup file can get the correct ip address using ServerIP=$AS_NAS_INET4_IP1.
======================= By default, in app setup will use below setting
docker-compose.yml environment: TZ: 'Asia/Singapore' ServerIP: 192.168.1.1 (replace by ServerIP=$AS_NAS_INET4_IP1)
dns:
cheehoong
commented
3 months ago Problem: My NAS has its two NICs bonded, so the 'normal' interface is now bond0, not eth0. This is all setup using the normal Asustor web interface. I then installed pihole, and found that it wasn't working. It seems that it's listening on eth0, not bond0. I tried manually changing this in several of the configuration files I found, but if I stop/start pihole, they all revert back to eth0.
The setup scripts seem to capture certain details correctly (e.g. the ServerIP address), however they need to also dynamically collect the correct network interface name and include this in the docker/environment/config parameter.
Version: v5.17.1.r01
Currently I'm unable to run pihole from the AppStore as the DNS server is attached to the wrong interface (eth0, not bond0).
Please help to download the testing package, and install it on your NAS. It will get all key values while installing the App from App Central, and we need to check what's the ETH0 and BOND0 on the NAS.
Please send the /volume1/Public/install_test.txt back for us.
In general, AS_NAS_INET4_IP1 will get 1st IP from eth0, bond0, Wi-fi if they are available.
BTW, if your app is a docker container, using PortainerCE to change the environment of the container to duplicate the container, and re-start it should be the current solution for the user to update the correct IP address in pi-hole.
https://drive.google.com/file/d/1bv9ekNmxhLls3Y8sZDNfLzDWUZrQXcUq/view?usp=sharing
Problem: My NAS has its two NICs bonded, so the 'normal' interface is now bond0, not eth0. This is all setup using the normal Asustor web interface. I then installed pihole, and found that it wasn't working. It seems that it's listening on eth0, not bond0. I tried manually changing this in several of the configuration files I found, but if I stop/start pihole, they all revert back to eth0.
The setup scripts seem to capture certain details correctly (e.g. the ServerIP address), however they need to also dynamically collect the correct network interface name and include this in the docker/environment/config parameter.
Version: v5.17.1.r01
Currently I'm unable to run pihole from the AppStore as the DNS server is attached to the wrong interface (eth0, not bond0).