Unbound and android 4.1
-
its on a unifi system and looks like with more inspection and droid devices are not obtaining ip addresses switch back and bytime i unlock phone its online not see anything in the log regarding dhcp and only this alog for unbound:
Feb 23 14:56:32 php: config.inc: The command '/usr/pbi/unbound-amd64/sbin/unbound-control dump_cache > /var/tmp/unbound_cache' returned exit code '1', the output was '' -
unbound is not a DHCP server. Seriously cannot see how's this even related. Looks like your DHCP server is simply not running.
-
dhcp claims its running but maybe not ?? its the only change and android breaks so thats what had me thinking unbound is the culprit
-
Feb 23 15:10:28 php: /services_dnsmasq.php: The command '/usr/local/sbin/dhcpd -user dhcpd -group _dhcp -chroot /var/dhcpd -cf /etc/dhcpd.conf -pf /var/run/dhcpd.pid em2' returned exit code '1', the output was 'Internet Systems Consortium DHCP Server 4.2.5-P1 Copyright 2004-2013 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ /etc/dhcpd.conf line 19: semicolon expected. option domain-name-servers 8.8.8.8,8.8.4.4,2620: ^ Configuration file errors encountered – exiting If you did not get this software from ftp.isc.org, please get the latest from ftp.isc.org and install that before requesting help. If you did get this software from ftp.isc.org and have not yet read the README, please read it before requesting help. If you intend to request help from the dhcp-server@isc.org mailing list, please read the section on the README about submitting bug reports and requests for help. Please do not
this is pointing to something only spot dns is entered is in general setup iam thinking its unhappy with ipv6 in general dns settings
-
Obviously messed up. You should NOT put IPv6 DNS servers to Services - DHCP Server configuration.
-
ive not just the dns entrys under general setup
-
Either specify your DNS servers in DHCP server configuration, or remove those IPv6 ones from general setup. (If you can reproduce this with latest 2.1.1 snapshot, you should file a bug; DHCPv4 server is not supposed to pick up IPv6 stuff it does not understand from somewhere.)
(Apparently, you only see this with DNS forwarder disabled, no matter whether unbound is installed or not.)
-
ive not just the dns entrys under general setup
Are you sure you do not have the 3 dns entries inserted on this page? Services -> DHCP Server -> Any interface tab. You can see where I am referring to in the attached picture. DNS here should be left blank.
/usr/local/sbin/dhcpd -user dhcpd -group _dhcp -chroot /var/dhcpd -cf /etc/dhcpd.conf -pf /var/run/dhcpd.pid em2Could this be on a secondary interface you have setup? I only have 1 interface "LAN" but you may have multiple tabs setup. The error above refers to em2. Please double check. Also can you copy and paste your /var/dhcpd/etc/dhcpd.conf file?
 -
not related to unbound i had set under general tab dns 2 ivp6 addresses and that caused problems for dhcpv4
-
Ok great. The only issue for unbound is the dump of the cache. I need to make it work a little bit more reliable.
Will check it out. -
not related to unbound i had set under general tab dns 2 ivp6 addresses and that caused problems for dhcpv4
What verison of pfsense are you running?
-
runnng 2.1.1 64 bit its present in 2.1 also
-
Enough, pretty clear bug…
https://redmine.pfsense.org/issues/3483
-
https://redmine.pfsense.org/projects/pfsense/repository/revisions/9399370b367df7b73b84d605f4f44599c93b0bbe/diff
https://redmine.pfsense.org/issues/3015
-
https://redmine.pfsense.org/projects/pfsense/repository/revisions/9399370b367df7b73b84d605f4f44599c93b0bbe/diff
https://redmine.pfsense.org/issues/3015
That fix clearly did not work (presumably due to the fact is is failing to check anything but the first and second DNS entries in System - General Setup.)
-
https://redmine.pfsense.org/projects/pfsense/repository/revisions/9399370b367df7b73b84d605f4f44599c93b0bbe/diff
https://redmine.pfsense.org/issues/3015
That fix clearly did not work (presumably due to the fact is is failing to check anything but the first and second DNS entries in System - General Setup.)
It is related to the same problem but it is a fix for DNS zones. I have updated your bug report with the related information.