EOS + pihole limited connectivity on WiFi

Setup

EOS with KDE
home network Mikrotik DHCP network @ 192.168.88.1/24 (network 192.168.88.0) - its default network config on mikrotik devices

On the modem there is pihole in container at 172.17.0.0 network setup with this https://help.mikrotik.com/docs/display/ROS/Container

my laptop have only wifi card

All other devides either directly connected via wire or wireless have no problem accesing net through pihole DNS but on laptop i got limited connectivity error. I can ping anything in 192.168.88.x network, but cant go outside. Other laptop with Win11 onboard works the same with phones.

When i add “other dns server” in KDE connections like 8.8.8.8 or 1.1.1.1 and reconnect all work normally then but pihole is omited in connections now ;/

nmap output

sudo nmap --script broadcast-dhcp-discover -e wlan0 ─╯
[sudo] password for damador:
Starting Nmap 7.93 ( https://nmap.org ) at 2023-02-06 00:16 CET
Pre-scan script results:
| broadcast-dhcp-discover:
| Response 1 of 1:
| Interface: wlan0
| IP Offered: 192.168.88.21
| DHCP Message Type: DHCPOFFER
| Subnet Mask: 255.255.255.0
| Router: 192.168.88.1
| Domain Name Server: 172.17.0.2
| IP Address Lease Time: 10m00s
|_ Server Identifier: 192.168.88.1
WARNING: No targets were specified, so 0 hosts scanned.
Nmap done: 0 IP addresses (0 hosts up) scanned in 10.29 seconds

not using UFW @ home

ok that was my fault :slight_smile: there was instance of docker running on the homelab server - it was bridged to the same subnet and also in 172.17.x.x range changed pihole to 172.30.0.2 fixed everything :slight_smile:

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.