Asus AC68


#102

SOrry, my bad…again!

pi@PiHole:~ $ grep -v ‘^#|^$’ /etc/dhcpcd.conf
hostname
clientid
persistent
option rapid_commit
option domain_name_servers, domain_name, domain_search, host_name
option classless_static_routes
option ntp_servers
option interface_mtu
require dhcp_server_identifier
slaac private
interface eth0
static ip_address=10.1.1.3/24
static routers=10.1.1.1
static domain_name_servers=127.0.0.1
interface eth0
static ip_address=10.1.1.240/24
static routers=10.1.1.1
static domain_name_servers=127.0.0.1
pi@PiHole:~ $


#103

You have two instances now of the same eth0 interface thats not connected.
Somehow the changes you made not being stored ? EDIT: sorry it was stored but the two instances is creating problems.

Try edit again:

sudo nano /etc/dhcpcd.conf

Delete everything under the line with “#fallback static_eth0”,
and paste below at the bottom:

interface wlan0
    static ip_address=10.1.1.3/24
    static routers=10.1.1.1
    static domain_name_servers=127.0.0.1

Save it and check if stored now with:

cat /etc/dhcpcd.conf

Reboot and check out the new IP:

ip a


#104

Just to ensure I am following the instructions correctly, I still have not switched off DHCP on the router…as I thought it came after this step…???..

AARGH!..now I cannot VNC into the Rpi as the IP has changed from 240 to 3 and I forgot to adjust the VNC …so I have to get out the screen and keyboard and set it all up again…sorry…I may be some time…probably tomorrow as it is getting late here.


#105

First get Pi-hole working and configured properly before switching DHCP service.

Dont need VNC if the SSH daemon on Pi is enebled:


#106

SSH not enabled as I generally use VNC :frowning:


#107

I dont use/install desktops on any of my servers.
All is done through SSH and Bash.
If I need a graphical application that needs desktop support, I export my display on server to network and use X to run applications on from a remote PC/laptop/etc:

https://www.x.org/wiki/


#108

That is certainly the ideal!..but for a novice like me…who does sporadic projects and forgets easily…VNC seems to work. I would certainly follow your suggested route if I were more experienced.


#109

You can have both VNC and SSHd active … after you get in again :wink:


#110

Given this experience, I think it would be a good idea!

Good night …thanks again for your patience and your help!


#111

Sorry about that!..I am back!

pi@PiHole:~ $ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
    link/ether b8:27:eb:dd:0c:bf brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether b8:27:eb:88:59:ea brd ff:ff:ff:ff:ff:ff
    inet 10.1.1.3/24 brd 10.1.1.255 scope global wlan0
       valid_lft forever preferred_lft forever
    inet6 fe80::c275:c91:b0e:89c9/64 scope link 
       valid_lft forever preferred_lft forever
pi@PiHole:~ $

#112

Looks good.
Run below ones on Pi to enable the sshd daemon and start sshd for next time you lose VNC:

sudo systemctl enable ssh

sudo systemctl start ssh

From the pj-selgbuild client, you should now be able to ssh into Pi with:

ssh -l pi 10.1.1.3

Next configure Pi-hole to use the new 10.1.1.3 address by running reconfigure:

echo 'nameserver 8.8.8.8' | sudo tee /etc/resolv.conf

pihole -r

Reboot Pi to be sure and test from Pi and a client:

nslookup pi.hole 10.1.1.3

If that all works, you can try switching DHCP service from router to Pi-hole:

After the switch, reboot the pj-selgbuild client and run below ones on it to see if it picked up the new DHCP settings including the Pi DNS IP:

ip a

cat /etc/resolv.conf

nslookup pi.hole

If that looks good, reboot your other client devices to renew DHCP lease so they too start using the new DHCP service + ad blocking through Pi-hole’s DNS.


#113

??? Where did the 240 come from now???

[i] Existing PHP installation detected : PHP version 7.0.33-0+deb9u3
[i] Repair option selected
[✓] Disk space check
[✓] Update local cache of available packages

[✓] Checking apt-get for upgraded packages… up to date!

[i] Installer Dependency checks…
[✓] Checking for apt-utils
[✓] Checking for dialog
[✓] Checking for debconf
[✓] Checking for dhcpcd5
[✓] Checking for git
[✓] Checking for iproute2
[✓] Checking for whiptail

[i] Performing reconfiguration, skipping download of local repos
[✓] Resetting repository within /etc/.pihole…
[✓] Resetting repository within /var/www/html/admin…
[i] Main Dependency checks…
[✓] Checking for cron
[✓] Checking for curl
[✓] Checking for dnsutils
[✓] Checking for iputils-ping
[✓] Checking for lsof
[✓] Checking for netcat
[✓] Checking for psmisc
[✓] Checking for sudo
[✓] Checking for unzip
[✓] Checking for wget
[✓] Checking for idn2
[✓] Checking for sqlite3
[✓] Checking for libcap2-bin
[✓] Checking for dns-root-data
[✓] Checking for resolvconf
[✓] Checking for libcap2
[✓] Checking for lighttpd
[✓] Checking for php7.0-common
[✓] Checking for php7.0-cgi
[✓] Checking for php7.0-sqlite3

[✓] Enabling lighttpd service to start on reboot…

[i] FTL Checks…

[✓] Detected ARM-hf architecture (armv7+)
[i] Checking for existing FTL binary…
[i] Latest FTL Binary already installed (v4.2.3). Confirming Checksum…
[i] Checksum correct. No need to download!
[✓] Checking for user ‘pihole’
[✓] Installing scripts from /etc/.pihole

[i] Installing configs from /etc/.pihole…
[i] Existing dnsmasq.conf found… it is not a Pi-hole file, leaving alone!
[✓] Copying 01-pihole.conf to /etc/dnsmasq.d/01-pihole.conf

[i] Installing blocking page…
[✓] Creating directory for blocking page, and copying files
[✗] Backing up index.lighttpd.html
No default index.lighttpd.html file found… not backing up

[✓] Installing sudoer file

[✓] Installing latest Cron script

[✓] Installing latest logrotate script
[i] Backing up /etc/dnsmasq.conf to /etc/dnsmasq.conf.old
[✓] man pages installed and database updated
[i] Testing if systemd-resolved is enabled
[i] Systemd-resolved is not enabled
[✓] Restarting lighttpd service…
[✓] Enabling lighttpd service to start on reboot…
[i] Restarting services…
[✓] Enabling pihole-FTL service to start on reboot…
[✓] Restarting pihole-FTL service…
[✓] Deleting existing list cache
[i] Pi-hole blocking is enabled
[i] Neutrino emissions detected…
[✓] Pulling blocklist source list into range

[i] Target: raw.githubusercontent.com (hosts)
[✓] Status: Retrieval successful

[i] Target: mirror1.malwaredomains.com (justdomains)
[✓] Status: Retrieval successful

[i] Target: sysctl.org (hosts)
[✓] Status: Retrieval successful

[i] Target: zeustracker.abuse.ch (blocklist.php?download=domainblocklist)
[✓] Status: Retrieval successful

[i] Target: s3.amazonaws.com (simple_tracking.txt)
[✓] Status: Retrieval successful

[i] Target: s3.amazonaws.com (simple_ad.txt)
[✓] Status: Retrieval successful

[i] Target: hosts-file.net (ad_servers.txt)
[✓] Status: Retrieval successful

[✓] Consolidating blocklists
[✓] Extracting domains from blocklists
[i] Number of domains being pulled in by gravity: 134824
[✓] Removing duplicate domains
[i] Number of unique domains trapped in the Event Horizon: 112381
[i] Number of whitelisted domains: 0
[i] Number of blacklisted domains: 2
[i] Number of regex filters: 0
[✓] Parsing domains into hosts format
[✓] Cleaning up stray matter

[✓] Force-reloading DNS service
[✓] DNS service is running
[✓] Pi-hole blocking is Enabled

[i] The install log is located at: /etc/pihole/install.log
Update Complete!

Current Pi-hole version is v4.2.2
Current AdminLTE version is v4.2
Current FTL version is v4.2.3
pi@PiHole:~ $ nslookup pi.hole 10.1.1.3
Server: 10.1.1.3
Address: 10.1.1.3#53

Name: pi.hole
Address: 10.1.1.240

pi@PiHole:~ $


#114

Ooops! did not do the reboot! :frowning:


#115

Hmmm! even after the reboot 240 still comes up? what am I doing wrong?

pi@PiHole:~ $ nslookup pi.hole 10.1.1.3
Server: 10.1.1.3
Address: 10.1.1.3#53

Name: pi.hole
Address: 10.1.1.240

pi@PiHole:~ $


#116

When you did run reconfigure pihole -r, did you select the correct interface wlan0 ?
And further on, were you not asked to use your current network settings ?
What did you reply here (yes/no) and what IP address was displayed here ?

Can you post outcome for below ones again pls ?

ip a

grep -v '^#\|^$' /etc/dhcpcd.conf

grep 'IPV[4,6]_ADDRESS\|PIHOLE_INTERFACE' /etc/pihole/setupVars.conf

sudo grep -v '^#\|^$' -R /etc/dnsmasq.*

It might be that your desktop runs some kind of network manager that messes things up.


#117

Ohw if some network manager is messing, below one might reveal:

sudo grep 10.1.1.240 -R /etc/


#118

Ooops! I just realised the problem…I ran this late last night…and was distracted by somebody at the crucial moment and so hit repair instead of reconfigure…my bad! Sorry! Back to square 1 and I will start again!


#119

Yeah I noticed later :smiley:


#120

But you could check below ones anyway to search for rouge network managers:

sudo grep 10.1.1.240 -R /etc/

sudo grep 10.1.1.240 -R ~


#121

OK will do…but I seem to have screwed something up…

pi@PiHole:~ $ nslookup pi.hole 10.1.1.3
;; connection timed out; no servers could be reached

pi@PiHole:~ $ nslookup pi.hole 10.1.1.3
;; connection timed out; no servers could be reached

pi@PiHole:~ $