# Asus AC68
**URL:** https://discourse.pi-hole.net/t/asus-ac68/18179
**Category:** Help
**Created:** [March 9, 2019, 6:19am UTC](https://discourse.pi-hole.net/t/asus-ac68/18179 "2019-03-09T06:19:58Z")
**Posts on this page:** 20
**Page:** 3
### Author:  [@dunbrokin](https://discourse.pi-hole.net/u/dunbrokin)
#### Post date: [March 12, 2019, 4:26am UTC](https://discourse.pi-hole.net/t/asus-ac68/18179/42 "2019-03-12T04:26:25Z")
Post reboot of Pi (did you reboot the Pi or the client?)
pi@PiHole:~ $ nslookup pi.hole 10.1.1.240
;; connection timed out; no servers could be reached
pi@PiHole:~ $
---
### Author:  [@dunbrokin](https://discourse.pi-hole.net/u/dunbrokin)
#### Post date: [March 12, 2019, 4:27am UTC](https://discourse.pi-hole.net/t/asus-ac68/18179/43 "2019-03-12T04:27:35Z")
On Client pre and post reboot of Pi
pj@pj-selgbuild:~$ nslookup pi.hole 10.1.1.240
;; connection timed out; no servers could be reached
pj@pj-selgbuild:~$ nslookup pi.hole 10.1.1.240
;; connection timed out; no servers could be reached
---
### Author:  [@dunbrokin](https://discourse.pi-hole.net/u/dunbrokin)
#### Post date: [March 12, 2019, 4:30am UTC](https://discourse.pi-hole.net/t/asus-ac68/18179/44 "2019-03-12T04:30:05Z")
I don't see any personal details....what am I missing?
pi@PiHole:~ $ sudo grep -v '^#|^$' -R /etc/dnsmasq.\*
/etc/dnsmasq.conf:conf-dir=/etc/dnsmasq.d
/etc/dnsmasq.conf.old:conf-dir=/etc/dnsmasq.d
/etc/dnsmasq.d/01-pihole.conf:addn-hosts=/etc/pihole/gravity.list
/etc/dnsmasq.d/01-pihole.conf:addn-hosts=/etc/pihole/black.list
/etc/dnsmasq.d/01-pihole.conf:addn-hosts=/etc/pihole/local.list
/etc/dnsmasq.d/01-pihole.conf:localise-queries
/etc/dnsmasq.d/01-pihole.conf:no-resolv
/etc/dnsmasq.d/01-pihole.conf:cache-size=10000
/etc/dnsmasq.d/01-pihole.conf:log-queries
/etc/dnsmasq.d/01-pihole.conf:log-facility=/var/log/pihole.log
/etc/dnsmasq.d/01-pihole.conf:local-ttl=2
/etc/dnsmasq.d/01-pihole.conf:log-async
/etc/dnsmasq.d/01-pihole.conf:dhcp-name-match=set:wpad-ignore,wpad
/etc/dnsmasq.d/01-pihole.conf:dhcp-ignore-names=tag:wpad-ignore
/etc/dnsmasq.d/01-pihole.conf:server=10.1.1.240
/etc/dnsmasq.d/01-pihole.conf:server=10.1.1.240
/etc/dnsmasq.d/01-pihole.conf:interface=eth0
---
### Author:  [@deHakkelaar](https://discourse.pi-hole.net/u/deHakkelaar)
#### Post date: [March 12, 2019, 4:42am UTC](https://discourse.pi-hole.net/t/asus-ac68/18179/45 "2019-03-12T04:42:11Z")
> [@dunbrokin](#):
>
> What is Ohw???
Like in I forgot something π
> [@dunbrokin](#):
>
> ```
> pi@PiHole:~ $ grep βIPV[4,6]_ADDRESS|PIHOLE_INTERFACEβ /etc/pihole/setupVars.conf
> PIHOLE_INTERFACE=eth0
> IPV4_ADDRESS=10.1.1.240/24
> IPV6_ADDRESS=
>
> ```
> [@dunbrokin](#):
>
> ```
> pi@PiHole:~ $ sudo grep -v β^#|^$β -R /etc/dnsmasq.*
> /etc/dnsmasq.d/01-pihole.conf:interface=eth0
>
> ```
Above two shows its still clinging on the the `eth0` interface instead of `wlan0`.
> [@dunbrokin](#):
>
> ```
> pi@PiHole:~ $ sudo grep -v β^#|^$β -R /etc/dnsmasq.*
> /etc/dnsmasq.d/01-pihole.conf:server=10.1.1.240
> /etc/dnsmasq.d/01-pihole.conf:server=10.1.1.240
>
> ```
And above one tells you have have configured Pi-hole to use its own IP address for upstream DNS resolution thus creating a loop.
Try run the reconfigure again (with `nameserver` hack) and select another upstream resolver and not the Pi-hole IP address!
And make sure `wlan0` is selected during the reconfigure!
---
### Author:  [@dunbrokin](https://discourse.pi-hole.net/u/dunbrokin)
#### Post date: [March 12, 2019, 4:47am UTC](https://discourse.pi-hole.net/t/asus-ac68/18179/46 "2019-03-12T04:47:02Z")
Nameserver hack??
So, should I choose the router 10.1.1.1 as the upstream?
---
### Author:  [@deHakkelaar](https://discourse.pi-hole.net/u/deHakkelaar)
#### Post date: [March 12, 2019, 4:48am UTC](https://discourse.pi-hole.net/t/asus-ac68/18179/47 "2019-03-12T04:48:27Z")
> [@dunbrokin](#):
>
> Nameserver hack??
> [@deHakkelaar](#):
>
> Set `nameserver` first before running `pihole -r` to reconfigure:
>
> `echo 'nameserver 8.8.8.8' | sudo tee /etc/resolv.conf`
>
> `pihole -r`
> [@dunbrokin](#):
>
> So, should I choose the router 10.1.1.1 as the upstream?
Yeah why not at first.
Can alter later with the web GUI.
---
### Author:  [@dunbrokin](https://discourse.pi-hole.net/u/dunbrokin)
#### Post date: [March 12, 2019, 4:48am UTC](https://discourse.pi-hole.net/t/asus-ac68/18179/48 "2019-03-12T04:48:55Z")
Ah got you the 8.8.8.8 hack...ok! Running now!
---
### Author:  [@dunbrokin](https://discourse.pi-hole.net/u/dunbrokin)
#### Post date: [March 12, 2019, 4:51am UTC](https://discourse.pi-hole.net/t/asus-ac68/18179/49 "2019-03-12T04:51:43Z")
sudo echo 'nameserver 8.8.8.8' | sudo tee /etc/resolv.conf
nameserver 8.8.8.8
pi@PiHole:~ $ pihole -r
[β] Root user check
```
.;;,.
.ccccc:,.
:cccclll:. ..,,
:ccccclll. ;ooodc
'ccll:;ll .oooodc
.;cll.;;looo:.
.. ','.
.',,,,,,'.
.',,,,,,,,,,.
.',,,,,,,,,,,,....
....''',,,,,,,'.......
......... .... .........
.......... ..........
.......... ..........
......... .... .........
........,,,,,,,'......
....',,,,,,,,,,,,.
.',,,,,,,,,'.
.',,,,,,'.
..'''.
```
[i] Existing PHP installation detected : PHP version 7.0.33-0+deb9u3
[i] Reconfigure option selected
[β] Disk space check
[β] Update local cache of available packages
[β] Checking apt-get for upgraded packages... 1 updates available
[i] It is recommended to update your OS after installing the Pi-hole!
[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] Using interface: eth0
[i] Using [i] Static IP already configured
[i] Unable to find IPv6 ULA/GUA address, IPv6 adblocking will not be enabled
[i] IPv4 address: 10.1.1.240/24
[i] IPv6 address:
[i] Web Interface On
[i] Web Server On
[i] Logging On.
[i] Privacy level 0 [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
[i] Skipping firewall configuration
[β] 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: 134827
[β] Removing duplicate domains
[i] Number of unique domains trapped in the Event Horizon: 112384
[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] View the web interface at [http://pi.hole/admin](http://pi.hole/admin) or [http://10.1.1.240/admin](http://10.1.1.240/admin)
[i] You may now configure your devices to use the Pi-hole as their DNS server
[i] Pi-hole DNS (IPv4): 10.1.1.240
[i] If you set a new IP address, please restart the server running the Pi-hole
[i] The install log is located at: /etc/pihole/install.log
Installation Complete!
pi@PiHole:~ $
---
### Author:  [@dunbrokin](https://discourse.pi-hole.net/u/dunbrokin)
#### Post date: [March 12, 2019, 4:54am UTC](https://discourse.pi-hole.net/t/asus-ac68/18179/50 "2019-03-12T04:54:06Z")
OK we have web access on the Pi!
---
### Author:  [@deHakkelaar](https://discourse.pi-hole.net/u/deHakkelaar)
#### Post date: [March 12, 2019, 5:01am UTC](https://discourse.pi-hole.net/t/asus-ac68/18179/51 "2019-03-12T05:01:37Z")
> [@dunbrokin](#):
>
> `[i] Using interface: eth0`
Hmmm one glitch tough, it still says `eth0`.
What if you hard set with below:
`sudo sed -i 's/PIHOLE_INTERFACE=eth0/PIHOLE_INTERFACE=wlan0/' /etc/pihole/setupVars.conf`
And run **REPAIR** this time:
`echo 'nameserver 8.8.8.8' | sudo tee /etc/resolv.conf`
`pihole -r`
EDIT: and check afterwards again:
`grep 'IPV[4,6]_ADDRESS\|PIHOLE_INTERFACE' /etc/pihole/setupVars.conf`
---
### Author:  [@dunbrokin](https://discourse.pi-hole.net/u/dunbrokin)
#### Post date: [March 12, 2019, 5:06am UTC](https://discourse.pi-hole.net/t/asus-ac68/18179/52 "2019-03-12T05:06:27Z")
i@PiHole:~ $ sudo sed -i 's/PIHOLE\_INTERFACE=eth0/PIHOLE\_INTERFACE=wlan0/' /etc/pihole/setupVars.conf
pi@PiHole:~ $
pi@PiHole:~ $ sudo sed -i 's/PIHOLE\_INTERFACE=eth0/PIHOLE\_INTERFACE=wlan0/' /etc/pihole/setupVars.conf
pi@PiHole:~ $ sudo echo 'nameserver 8.8.8.8' | sudo tee /etc/resolv.conf
nameserver 8.8.8.8
pi@PiHole:~ $ pihole -r
[β] Root user check
```
.;;,.
.ccccc:,.
:cccclll:. ..,,
:ccccclll. ;ooodc
'ccll:;ll .oooodc
.;cll.;;looo:.
.. ','.
.',,,,,,'.
.',,,,,,,,,,.
.',,,,,,,,,,,,....
....''',,,,,,,'.......
......... .... .........
.......... ..........
.......... ..........
......... .... .........
........,,,,,,,'......
....',,,,,,,,,,,,.
.',,,,,,,,,'.
.',,,,,,'.
..'''.
```
[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... 1 updates available
[i] It is recommended to update your OS after installing the Pi-hole!
[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
[β] DNS resolution is currently unavailable
[β] DNS resolution is now available
[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: 134827
[β] Removing duplicate domains
[i] Number of unique domains trapped in the Event Horizon: 112384
[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:~ $ grep 'IPV[4,6]\_ADDRESS|PIHOLE\_INTERFACE' /etc/pihole/setupVars.conf
PIHOLE\_INTERFACE=wlan0
IPV4\_ADDRESS=10.1.1.240/24
IPV6\_ADDRESS=
pi@PiHole:~ $
---
### Author:  [@deHakkelaar](https://discourse.pi-hole.net/u/deHakkelaar)
#### Post date: [March 12, 2019, 5:08am UTC](https://discourse.pi-hole.net/t/asus-ac68/18179/53 "2019-03-12T05:08:45Z")
Looks better.
And what bout `nslookup`'s on Pi and client ?
---
### Author:  [@dunbrokin](https://discourse.pi-hole.net/u/dunbrokin)
#### Post date: [March 12, 2019, 5:09am UTC](https://discourse.pi-hole.net/t/asus-ac68/18179/54 "2019-03-12T05:09:09Z")
Ooops! Sorry!
---
### Author:  [@dunbrokin](https://discourse.pi-hole.net/u/dunbrokin)
#### Post date: [March 12, 2019, 5:10am UTC](https://discourse.pi-hole.net/t/asus-ac68/18179/55 "2019-03-12T05:10:20Z")
pi@PiHole:~ $ nslookup pi.hole 10.1.1.240
Server: 10.1.1.240
Address: 10.1.1.240#53
Name: pi.hole
Address: 10.1.1.240
pi@PiHole:~ $
---
### Author:  [@dunbrokin](https://discourse.pi-hole.net/u/dunbrokin)
#### Post date: [March 12, 2019, 5:10am UTC](https://discourse.pi-hole.net/t/asus-ac68/18179/56 "2019-03-12T05:10:45Z")
pj@pj-selgbuild:~$ nslookup pi.hole 10.1.1.240
Server: 10.1.1.240
Address: 10.1.1.240#53
Name: pi.hole
Address: 10.1.1.240
pj@pj-selgbuild:~$
---
### Author:  [@deHakkelaar](https://discourse.pi-hole.net/u/deHakkelaar)
#### Post date: [March 12, 2019, 5:29am UTC](https://discourse.pi-hole.net/t/asus-ac68/18179/57 "2019-03-12T05:29:06Z")
That look all good.
DNS is working and if you query a naughty domain, you'll notice it gets redirected to `0.0.0.0`:
`nslookup doubleclick.com 10.1.1.240`
I wouldn't even bother trying to configure the Asus router to push the Pi-hole IP address for DNS resolution via DHCP to its clients as described here (method 1):
> [@How do I configure my devices to use Pi-hole as their DNS server?](https://discourse.pi-hole.net/t/how-do-i-configure-my-devices-to-use-pi-hole-as-their-dns-server/245):
>
> Three methods Generally, there are three different methods that will enable devices on your network to be protected by Pi-hole. 1. Define Pi-hole's IP address as the only DNS entry in the router Rationale Only is italicized here for a reason: Pi-hole needs to be the only DNS server because it intercepts queries and decides whether or not they should be blocked. If you have other DNS servers configured, you may be sent to the correct domain, bypassing Pi-hole completely. Because of this, we reβ¦
This because most Asus routers encountered push two DNS servers instead of only the Pi-hole IP address:
> [@Pi-Hole not blocking ads](https://discourse.pi-hole.net/t/pi-hole-not-blocking-ads/16700/18):
>
> Sounds like the Asus router is pushing two DNS servers to the clients via DHCP: If want to know for sure, install nmap on Pi-hole: sudo apt install nmap And do a DHCP discovery targeting the "\": sudo nmap -sU -p67 --script dhcp-discover \
Better switch off the DHCP service on the Asus router and flip it on on Pi-hole:
> [@How do I use Pi-hole's built in DHCP server (and why would I want to)?](https://discourse.pi-hole.net/t/how-do-i-use-pi-holes-built-in-dhcp-server-and-why-would-i-want-to/3026):
>
> Using Your Existing Router For Network-wide Ad Blocking You might not need to use Pi-hole's DHCP server: In many home environments, your router also functions as your DHCP server. In this case, you can often [set Pi-hole to be the DNS server for your network clients in the router's DHCP (or LAN) settings page](https://discourse.pi-hole.net/t/how-do-i-configure-my-devices-to-use-pi-hole-as-their-dns-server/245), which allows all of your network clients to block ads simply by connecting to the network. Setting it up this way is also what makes Pi-hole very powerful for network-wide ad blocking. Wβ¦
But before that, try assign a lower static IP address to Pi-hole like for example `10.1.1.2` or `10.1.1.3`.
That way you can set the DHCP range of IP addresses to be handed out to the clients (can alter later on web GUI) from lets say `10.1.1.10` up to `10.1.1.254`
If you edit below file, you'll notice it has a section at the bottom with your interface and IP address.
If edit any, you'll need to `reboot` and run `pihole -r` reconfigure again (maybe with `nameserver` hack).
If you change IP address, make sure its not taken already by pinging the address first!
`sudo nano /etc/dhcpcd.conf`
If your interested if your Asus router's DHCP service behaves the same as hours:
`sudo apt install nmap`
`sudo nmap -sU -p67 --script dhcp-discover 10.1.1.1`
---
### Author:  [@dunbrokin](https://discourse.pi-hole.net/u/dunbrokin)
#### Post date: [March 12, 2019, 8:44am UTC](https://discourse.pi-hole.net/t/asus-ac68/18179/58 "2019-03-12T08:44:18Z")
Thank you for your help...it is very much appreciated!
Can I just not leave it as it is now....it seem quite complicated to go too much further. 10.1.1.3 is available. If all I have to do is to set 10.1.1.3 as the static address for the Pi and put that ip address at the end of the dhcpcd.conf file, I think I can manage that! π
---
### Author:  [@dunbrokin](https://discourse.pi-hole.net/u/dunbrokin)
#### Post date: [March 12, 2019, 8:55am UTC](https://discourse.pi-hole.net/t/asus-ac68/18179/59 "2019-03-12T08:55:37Z")
pi@PiHole:~ $ sudo nmap -sU -p67 --script dhcp-discover 10.1.1.1
Starting Nmap 7.40 ( [https://nmap.org](https://nmap.org) ) at 2019-03-12 21:54 NZDT
Nmap scan report for router.asus.com (10.1.1.1)
Host is up (0.0014s latency).
PORT STATE SERVICE
67/udp open dhcps
| dhcp-discover:
| DHCP Message Type: DHCPACK
| Server Identifier: 10.1.1.1
| IP Address Lease Time: 20h18m24s
| Subnet Mask: 255.255.255.0
| Broadcast Address: 10.1.1.255
| WPAD:
|
| Domain Name Server: 10.1.1.240, 10.1.1.1
|\_ Router: 10.1.1.1
MAC Address: xxxxxxxxxxxxxxxx (Asustek Computer)
Nmap done: 1 IP address (1 host up) scanned in 2.04 seconds
pi@PiHole:~ $
---
### Author:  [@dunbrokin](https://discourse.pi-hole.net/u/dunbrokin)
#### Post date: [March 12, 2019, 9:00am UTC](https://discourse.pi-hole.net/t/asus-ac68/18179/60 "2019-03-12T09:00:14Z")
Hmmm! Maybe I over reacted...it does not seem too complicated. Just turn off on Asus and turn on on Rpi?
---
### Author:  [@dunbrokin](https://discourse.pi-hole.net/u/dunbrokin)
#### Post date: [March 12, 2019, 9:07am UTC](https://discourse.pi-hole.net/t/asus-ac68/18179/61 "2019-03-12T09:07:01Z")
"But before that, try assign a lower static IP address to Pi-hole like for example `10.1.1.2` or `10.1.1.3` .
That way you can set the DHCP range of IP addresses to be handed out to the clients (can alter later on web GUI) from lets say `10.1.1.10` up to `10.1.1.254`
If you edit below file, youβll notice it has a section at the bottom with your interface and IP address.
If edit any, youβll need to `reboot` and run `pihole -r` reconfigure again (maybe with `nameserver` hack).
If you change IP address, make sure its not taken already by pinging the address first!
`sudo nano /etc/dhcpcd.conf`"
So, let me sure I understand this. On my PC I assign 10.1.1.3 to my RPi. Then I just need to go to dhcpcd.conf and change the IP address as the end (which now reads 10.1.1.240). Do the pi -r and it is all done!?
[Previous page](https://discourse.pi-hole.net/t/asus-ac68/18179.md?page=2)
[Next page](https://discourse.pi-hole.net/t/asus-ac68/18179.md?page=4)