![]() usbcore: registered new interface driver brcmfmac If trying above, after a reboot, check with lsmod if a driver is missing now.įYI, my Pi3 loads below driver for wifi: $ lsmodįilename: /lib/modules/4.14.34-v7+/kernel/drivers/net/wireless/broadcom/brcm80211/brcmfmac/brcmfmac.koĭescription: Broadcom 802.11 wireless LAN fullmac $ dmesg -T | grep brcmfmac Maybe it is time to remove pi-hole and start again. Disable pi-hole and it is fine.Īdding the site to the whitelist as either Regex Whitelist or Exact Whitelist makes no difference. However clicking theĭisplayed link to - just one level down - nothing. At least the sudo: unable to resolve host. Irritatingly I have to keep setting the Wifi country to GB, for it seems to intermittently forget, despite a correct entry in /etc/wpa_supplicant/wpa_nf I have hopefully permanently clobbered it with an entry in /boot/config under On reboot, it would randomly reinstate wifi after disabling it in the GUI. Not giving name webserver to the DHCP lease of 192.168.1.202 because the name exists in /etc/hosts with address 127.0.1.1 18:22:17ĝNSMASQ_WARN Warning in dnsmasq core: Not giving name webserver.lan to the DHCP lease of 192.168.1.202 because the name exists in /etc/hosts with address 127.0.1.1 I now get warnings Warning in dnsmasq core: I have reinstated the dhcpdc file to read # Inform the DHCP server of our hostname for DDNS.Īnd we are back to square one-ish. Thank you for your very kind and wise guidance. If correct, your Pi doesnt acquire an IP via DHCP anymore and instead, those details are set statically: $ tail /etc/nfīest to restore that line to default: # Inform the DHCP server of our hostname for DDNS. This setting is intended for if the host were to acquire an IP via DHCP. If hostname is an empty string then the current Sends hostname to the DHCP server so it can be registered lighttpd has an additional nf file with "server.port = 8080". I understand this is something to do with 'loopback' Interestingly running the inbuilt generate debug log also fires up dhcp-discover and generates the same error Įverything appears to be working so do I just ignore the lo warning, or does it suggest something in my setup needs attention? "Warning in dnsmasq core: no address range available for DHCP request via lo" However, if I then run pihole-FTL dhcp-discover I get a new warning. This has been done and the problems described appear to have gone away. "# Inform the DHCP server of our hostname for DDNS. I subsequently discovered that I had foolishly not amended the dhcpdc file to reflect the hostname under I followed your wise guidance and rebooted. Thank you for taking the time to respond. …and then the “.unable to resolve host….” warning returns.Ĭan any kind soul please give me a shove in the right direction? ![]() "127.0.0.1 pihole-server" from the Hosts file Not giving name pihole-server to the DHCP lease of 192.168.1.251 because the name exists in /etc/hosts with address 127.0.0.1" ![]() Not giving name pihole-server.lan to the DHCP lease of 192.168.1.251 because the name exists in /etc/hosts with address 127.0.0.1 This nag goes away and I get another warning “sudo: unable to resolve host pihole-server: Name or service not known” When updating Pi or restarting services I get I am stuck in a circle and have no idea how to escape.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |