The issue I am facing:
It seems my raspberrypi (pi-hole) has 2 IP's
192.168.2.150 (static)
192.168.2.229 (unknown)
When I ping raspberrypi
from another machine it pings the wrong one (192.168.2.229).
Where is the second IP address coming from? Is it the wireless connection? Because I thought I disabled that one.
Strange thing is though, it is in /etc/pihole/dhcp.leases
:
1592592132 dc:a6:32:77:31:83 192.168.2.229 raspberrypi 01:dc:a6:32:77:31:83
Further everything is working fine.
Details about my system:
Pi-hole is configured as DHCP. The router's DHCP is off.
Here are a couple of screenshots:
pi@raspberrypi:~ $ ip addr show
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: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether dc:a6:32:77:31:82 brd ff:ff:ff:ff:ff:ff
inet 192.168.2.150/24 brd 192.168.2.255 scope global noprefixroute eth0
valid_lft forever preferred_lft forever
inet6 fe80::ddfd:cdbb:4a57:dacb/64 scope link
valid_lft forever preferred_lft forever
6: wg0: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1420 qdisc noqueue state UNKNOWN group default qlen 1000
link/none
inet 10.6.0.1/24 scope global wg0
valid_lft forever preferred_lft forever
pi@@raspberrypi:~ $ ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.2.150 netmask 255.255.255.0 broadcast 192.168.2.255
inet6 fe80::ddfd:cdbb:4a57:dacb prefixlen 64 scopeid 0x20<link>
ether dc:a6:32:77:31:82 txqueuelen 1000 (Ethernet)
RX packets 9500312 bytes 4124586591 (3.8 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 5813031 bytes 1668935025 (1.5 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 3155822 bytes 308572261 (294.2 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 3155822 bytes 308572261 (294.2 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wg0: flags=209<UP,POINTOPOINT,RUNNING,NOARP> mtu 1420
inet 10.6.0.1 netmask 255.255.255.0 destination 10.6.0.1
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 1000 (UNSPEC)
RX packets 108069 bytes 29180016 (27.8 MiB)
RX errors 166 dropped 4214 overruns 0 frame 166
TX packets 159517 bytes 159695936 (152.2 MiB)
TX errors 2481 dropped 209 overruns 0 carrier 0 collisions 0
/etc/hosts:
127.0.0.1 localhost
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
127.0.1.1 raspberrypi
/etc/hostname:
raspberrypi
/etc/pihole/local.list:
192.168.2.150 raspberrypi
192.168.2.150 pi.hole
Ping results:
C:\Users\_>ping raspberrypi
Pinging raspberrypi.home [192.168.2.229] with 32 bytes of data:
Reply from 192.168.2.127: Destination host unreachable.
Reply from 192.168.2.127: Destination host unreachable.
Reply from 192.168.2.127: Destination host unreachable.
Reply from 192.168.2.127: Destination host unreachable.
Ping statistics for 192.168.2.229:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
C:\Users\_>ping pi.hole
Pinging pi.hole [192.168.2.150] with 32 bytes of data:
Reply from 192.168.2.150: bytes=32 time<1ms TTL=64
Reply from 192.168.2.150: bytes=32 time<1ms TTL=64
Reply from 192.168.2.150: bytes=32 time<1ms TTL=64
Reply from 192.168.2.150: bytes=32 time<1ms TTL=64
Ping statistics for 192.168.2.150:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
What I have changed since installing Pi-hole:
Added WireGuard.