Hey guys!! I’m having a weird issue since updating my Gateway to a unify gateway. Pihole is working fine and all devices are using pihole for DNS, but I’m consistently getting an error now. The error is: “ignoring query from non-local network 169.254.61.115 (logged only once)”. Everything including WireGuard seems to be working for remote access and tunneling as well. Also, I don’t recognize that remote IP 169.254.61.115. I checked online for this error, but the recommended setting to “Bind to eth0” breaks Wiregaurd connectivity from Cellular connection. Any help would be greatly appreciated.
That address space is APIPA, or the address space that systems choose from when they need an IP address and they are not configured for a static IP address and they can not reach a DHCP server for an address.
Not sure if that helps but that information combined with the fact that your Unify was recently updated might point you in the right direction. It's not a remote address, it would have to be from a client/server/system on the LAN.
Thanks for that tip. I had no idea what that IP was for. Well I recently upgraded my whole setup. Replaced a Asus Router with a Unify gateway and switch and still use the asus router as an access point. Before the migration I made DHCP reservations for all of my devices using MAC addresses, kept the same IP range, and kept the WiFi SSID’s intact. All of my connected devices have the same IP they previously had. After the migration all services worked perfectly and pihole/unbound continued to function as normal. I’m wondering if maybe the Unify switch is expecting to have some kind of reserved IP, iits the only new device that has a new IP Address. If not, it may simply be a bug in the Unify Network Software/Controller. I’ll check up with Unify, thanks for the tip. Much appreciated.
I’ve got a full UniFi setup in my home with Pi-hole and Unbound. I think I’ve only seen that message once or twice, and don’t recall if it was associated with initially adding equipment, or not. I used to have some equipment from Netgear, but eliminated that over time.
My devices are all up to date with the firmware/network application, and I try to keep them current. Best guess is you might want to review various configuration parameters for any VLANs you have setup. My main VLAN uses Pi-hole for DNS/DHCP. The other VLANs just use Pi-hole for DNS. There are quite a few settings with UniFi, and they tend not to hold your hand as much as typical home equipment in my experience.
I previously just had a CloudKey Gen2+, 2 Ai Ports, an Ai Key and a Pro Max PoE switch with three cams using the Cloud Key as a controller. The cloudkey was the controller for both Protect and Network. All of those devices had static IPs except for the switch. After adding the gateway, I decided to take some of the load off of the cloudkey and run network on the gateway itself. When I made those changes, I assigned a static IP for the switch on the Network App on the Gateway. Maybe the change of IP on the switch caused this abnormality and it MIGHT have been temporary, as it hasn’t been back since last night. I haven't configured any VLANS yet as I have almost 70 devices, of which almost half are Matter over Thread devices, in a Apple Centered environment and I'm honestly afraid I'm going to break things and cause automations to fail. I have a bit of reading and studying to do before I venture into VLANS. The Zone based firewalls are interesting as well. Lots to learn with the Networking side of things with Unify!! Thanks for sharing your experience with me, I'm hoping I have the same results you had and it was just a hiccup due to the IP change of the switch.