@Sebastian-Roth I had to reinstall node.js, but I followed a different set of directions than before, and wouldn’t you know, node-dhcproxy functions as it should. I’m guessing that I did not have node.js setup properly the last time I ran it. I’ve attached the dump file anyway.
Thanks for your help on this, it is nice to have another option for our network environment should dnsmasq becomes unusable. -kurt
From what I can tell, the installer is adding lines to the fog.conf file that keeps the httpd service from restarting.
I can take out the bad lines from the fog.conf file and the httpd service restarts as it should.
-kurt
That did it, problem solved. Thanks for the info on the new DNSMasq binary.
-kurt
Disabling IPv6 did the trick. I ran:
sudo echo "1" > /proc/sys/net/ipv6/conf/all/disable_ipv6
and the installer ran normally. I’ll need to shut it down permanently.
Thank you for your help. Is this IPv6 issue consistent in all of the builds?
-kurt