Unable to query from Br0 and Eth0 interfaces #3
Comments
|
For the first error try setting in [dns]
interface = "br0"
listeningMode = "BIND"
For the second error: [ntp.ipv4]
active = false
listeningMode = "BIND"I'm guessing you're already running NTP server and the port is taken so that's what the error message is about. I've edited your message to wrap the log into expandable section to not take so much space. |
|
Thank you so much for the quick reply!!! I followed your steps along with rebooting my router the errors are no longer present however, it appears that queries are still not passing through the pihole.
I'm quite sure i got my DNS settings correct, not too sure what else i could be missing here.
|
|
Does these work when executed from the router: Have you tried running I'm not really familiar with Merlin's firmware - maybe something else in the firmware is blocking it? |
|
Interesting, i port forwarded port 53:53 to 192.168.1.1 (my router) and it gave me a second connection within PiHole Seems like messing around with port forwarding may be the route. nslookup returns this: |
Did that generate an entry in Pi-hole's Query Log page? Because if it did not then the request was most likely handled by firmware's dnsmasq (which shouldn't happen with |
|
it did not appear to generate anything within the log: my (i guess i did not enter it right?) |
|
Can you check if dnsmasq config contains that port line (and doesn't have a second one)? |
|
My dnsmasq.conf``` pid-file=/var/run/dnsmasq.pid user=nobody bind-dynamic interface=br0 interface=pptp* no-dhcp-interface=pptp* no-resolv servers-file=/tmp/resolv.dnsmasq no-poll no-negcache cache-size=1500 min-port=4096 dns-forward-max=1500 domain=admin expand-hosts bogus-priv domain-needed local=/admin/ dhcp-range=lan,192.168.1.25,192.168.1.254,255.255.255.0,86400s dhcp-option=lan,3,192.168.1.1 dhcp-option=lan,6,192.168.1.14,192.168.1.14,0.0.0.0 dhcp-option=lan,15,admin dhcp-option=lan,44,192.168.1.1 dhcp-option=lan,252,"\n" dhcp-option=lan,42,0.0.0.0 dhcp-authoritative interface=tun21 interface=br1 dhcp-range=br1,192.168.101.2,192.168.101.254,255.255.255.0,86400s dhcp-option=br1,3,192.168.101.1 interface=br2 dhcp-range=br2,192.168.102.2,192.168.102.254,255.255.255.0,86400s dhcp-option=br2,3,192.168.102.1 interface=wgs1 no-dhcp-interface=wgs1 dhcp-host=A0:36:BC:75:55:E0,set:A0:36:BC:75:55:E0,Ai-Mesh,192.168.1.2 dhcp-host=4C:2E:B4:A6:3A:1F,set:4C:2E:B4:A6:3A:1F,iPad-WiFi,192.168.1.4 dhcp-host=20:7B:D2:A5:57:F7,set:20:7B:D2:A5:57:F7,iPad-RJ45,192.168.1.5 dhcp-host=76:13:01:82:C1:0E,set:76:13:01:82:C1:0E,iPhone-11,192.168.1.6 dhcp-host=34:FD:6A:1B:85:2A,set:34:FD:6A:1B:85:2A,Apple-TV-1,192.168.1.8 dhcp-host=34:FD:6A:20:3B:B8,set:34:FD:6A:20:3B:B8,Apple-TV-2,192.168.1.9 dhcp-host=94:EA:32:99:CA:85,set:94:EA:32:99:CA:85,Homepod-1,192.168.1.10 dhcp-host=94:EA:32:9D:15:99,set:94:EA:32:9D:15:99,Homepod-2,192.168.1.11 dhcp-host=90:81:2A:76:FD:CF,set:90:81:2A:76:FD:CF,Apple-Watch,192.168.1.15 dhcp-host=F8:4E:73:F1:A3:3D,set:F8:4E:73:F1:A3:3D,iPhone-11-pro,192.168.1.16 hcp-host=D8:3A:DD:56:F2:3E,set:D8:3A:DD:56:F2:3E,HomeBridge,192.168.1.14 dhcp-host=C4:29:96:09:B6:7A,set:C4:29:96:09:B6:7A,SyncBox,192.168.1.7 dhcp-host=1C:5A:3E:C6:B4:02,set:1C:5A:3E:C6:B4:02,SamsungTV,192.168.1.12 dhcp-host=04:D4:C4:71:FC:CF,set:04:D4:C4:71:FC:CF,Laptop,192.168.1.3 dhcp-host=EC:B5:FA:8E:1E:09,set:EC:B5:FA:8E:1E:09,HueBridge,192.168.1.13 dhcp-host=3C:2A:F4:9C:1A:0D,set:3C:2A:F4:9C:1A:0D,brother-printer,192.168.1.48 dhcp-host=0C:9D:92:1B:EF:14,set:0C:9D:92:1B:EF:14,desktop,192.168.1.17 dhcp-name-match=set:wpad-ignore,wpad dhcp-ignore-names=tag:wpad-ignore dhcp-script=/sbin/dhcpc_lease script-arp edns-packet-max=1232 address=/homebridge.local/192.168.1.14 ```Unfortunately i've gotten myself into a bigger problem now. I can't seem to start the
Edit: New pihole -d log new debug log``` YokeThaJoker@RT-AX86U-Pro:/tmp/etc# This process collects information from your Pi-hole, and optionally uploads it to a unique and random directory on tricorder.pi-hole.net.The intent of this script is to allow users to self-diagnose their installations. This is accomplished by running tests against our software and providing the user with links to FAQ articles when a problem is detected. Since we are a small team and Pi-hole has been growing steadily, it is our hope that this will help us spend more time on development. NOTE: All log files auto-delete after 48 hours and ONLY the Pi-hole developers can access your data via the given token. We have taken these extra steps to secure your data and will work to further reduce any personal information gathered. *** [ INITIALIZING ] *** [ DIAGNOSING ]: Core version *** [ DIAGNOSING ]: Web version *** [ DIAGNOSING ]: FTL version *** [ DIAGNOSING ]: Operating system *** [ DIAGNOSING ]: SELinux *** [ DIAGNOSING ]: FirewallD *** [ DIAGNOSING ]: System hardware configuration *** [ DIAGNOSING ]: Processor details *** [ DIAGNOSING ]: Disk usage *** [ DIAGNOSING ]: Network interfaces and addresses *** [ DIAGNOSING ]: Network routing table *** [ DIAGNOSING ]: Networking
*** [ DIAGNOSING ]: Ports in use *** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain *** [ DIAGNOSING ]: Name resolution (IPv6) using a random blocked domain and a known ad-serving domain *** [ DIAGNOSING ]: Discovering active DHCP servers (takes 10 seconds)
DHCP packets received on br0: 1 *** [ DIAGNOSING ]: Pi-hole processes *** [ DIAGNOSING ]: Pi-hole-FTL full status *** [ DIAGNOSING ]: Pi-hole FTL Query Database *** [ DIAGNOSING ]: Gravity Database *** [ DIAGNOSING ]: Info table version 18 ----- First 10 Gravity Domains ----- *** [ DIAGNOSING ]: Groups 0 1 Default 2024-09-15 21:49:25 2024-09-15 21:49:25 The default group *** [ DIAGNOSING ]: Domainlist (0/1 = exact white-/blacklist, 2/3 = regex white-/blacklist) *** [ DIAGNOSING ]: Clients *** [ DIAGNOSING ]: Adlists 1 1 0 https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts 2024-09-15 21:49:25 2024-09-15 21:49:25 Migrated from /opt/etc/pihole/adlists.list *** [ DIAGNOSING ]: contents of /opt/etc/pihole -rw-r--r-- 1 YokeThaJ root 463 Sep 15 21:49 /opt/etc/pihole/logrotate -rw-rw---- 1 pihole pihole 49.0K Sep 15 21:52 /opt/etc/pihole/pihole.toml -rw-r--r-- 1 pihole pihole 457 Sep 15 21:49 /opt/etc/pihole/versions *** [ DIAGNOSING ]: contents of /opt/etc/dnsmasq.d *** [ DIAGNOSING ]: contents of /opt/etc/cron.d -rw-r--r-- 1 YokeThaJ root 1.6K Sep 15 21:49 /opt/etc/cron.d/pihole *** [ DIAGNOSING ]: contents of /opt/var/log/pihole -rw-r----- 1 pihole pihole 389.2K Sep 15 21:49 /opt/var/log/pihole/FTL.log -----tail of FTL.log------ -rw-r----- 1 pihole pihole 5.8K Sep 15 14:19 /opt/var/log/pihole/webserver.log -----tail of webserver.log------ *** [ DIAGNOSING ]: contents of /dev/shm *** [ DIAGNOSING ]: contents of /opt/etc lrwxrwxrwx 1 YokeThaJ root 16 Sep 14 18:55 /opt/etc/resolv.conf -> /etc/resolv.conf *** [ DIAGNOSING ]: Pi-hole diagnosis messages *** [ DIAGNOSING ]: Locale *** [ DIAGNOSING ]: Pi-hole log -----tail of pihole.log------ [✓] ** FINISHED DEBUGGING! **
|
|
Firmware dnsmasq is taking port 53 so Pi-hole can't run on it, that's why it fails to start. You gotta find out why it didn't run - permissions? Check router log to verify if it ran the script. 'pihole enable' requires Pi-hole to be running as far as I know, it's weird that it threw those errors though but it happens on my side too so it's Pi-hole's bug. PS You have to add new line after and before three ` otherwise it won't work. |
So i browsed through my routers logs and came across this: I ran
When i first lost access to the PiHole on my router i did re-test that my Raspberry Pi was still able to start & establish a connection otherwise none of my DNS queries would parse and i would be shit-outta-luck when i left my house and my wireguard would fail to shake hands with my router. Currently the Raspberry Pi instance is dead so i should be able to test it out on the router. Apolgies for such a late reply! Edit - After rebooting my router my logs now state this: it appears that New pihole debug log new debug logHonestly not sure where to go from here. Doesn't seem to matter what i do, the webserver just doesnt wan't to start anymore. attempt at starting overLast edit on this post (i promise) - While i do endorse the work you've done making this work for the AX58U i honeslty don't think my Ax86U is up to the task (which is shame), i'll keep tinkering around when i get free time but from what i see, i've hit a dead end. |
That's on me for not testing this with multiple interface lines, I will try to update the postconf script today. That line should be present in the config only once. Alternatively you could peak at stock Asuswrt install wiki page and try to run it on not-53 port instead and direct dnsmasq to redirect DNS requests to it. Edit: I've updated postconf script on the wiki page. |
Edit; Using Asus WRT Merlin firmware on an Asus RT-AX86U Pro
I tried to follow this guide as closely as possible however have been having issues getting query request to pass through PiHole;
(Removed LAN IP's & Mac address information)
My PiHole diagnostics tab is spitting two errors that i can't seem to resolve:
My pihole debug log (removed as much personal information as i can see)
debug log
The text was updated successfully, but these errors were encountered: