Bug?! DHCPv6 server keeps starting although disabled

VFrontDe

Hi all,

I have disabled the DHCP and DHCPv6 servers on both the LAN and WAN interfaces, but the DHCPv6 server keeps starting on the LAN interface even after a reboot.
In the shell I see these processes:

# ps waux| grep dhc
dhcpd   31851   0.0  2.2  20724 10840  -  Is    9:26PM  0:00.00 /usr/local/sbin/dhcpd -6 -user dhcpd -group _dhcp -chroot /var/dhcpd -cf /etc/dhcpdv6.conf -pf /var/run/dhcpdv6.pid em0
root    32378   0.0  0.4   8316  1880  -  Is    9:26PM  0:00.00 /usr/local/sbin/dhcpleases6 -c /usr/local/bin/php -f /usr/local/sbin/prefixes.php|/bin/sh -l /var/dhcpd/var/db/dhcpd6.leases
root    50926   0.0  0.5  14664  2336  -  Ss    9:26PM  0:00.01 /usr/sbin/syslogd -s -c -c -l /var/dhcpd/var/run/log -P /var/run/syslog.pid -f /var/etc/syslog.conf

and the DHCP server process hands out IPv6 address leases on the LAN interface (em0) although it is NOT enabled in the WebGUI (in Services / DHCPv6 Server / RA). Of course this causes issues on my network, because I already have another box running that does DHCP. I tried ENabling and DISabling the service in the GUI, but that did not help.

For now I have manually killed the dhcpd and dhcpleases6 processes, but they will return after a reboot. I have tried to find out what script starts the daemon and why. There must be something wrong with the config files, but I cannot figure out what it is.

Can someone help me to look at the right files and fix the issue?

Thanks
Andreas

hda

pfSense 2.2.2 ?

Did you use save button after unchecking the server in GUI ?

VFrontDe

Yes, it's 2.2.2. And sure I used the Save button.

I even tried to backup and restore the configuration via WebGUI/Diagnostics. To no avail … In the GUI the service is always shown as not enabled, but it is really running.

I have other pfSense 2.2.2 appliances that do not show this issue, but they have all been updated from earlier versions, whereas this is a fresh install.

Where should I start looking to find the root cause? Any advice?

hda

Diff this problem config.xml with your good-upgraded-2.2.2 you said is ok.

[Else I would fresh install & fresh (manual) config.]

VFrontDe

I could not figure out any diffs in the config.xml files that would explain the behavior.

So, I started over with a clean install of 2.2.2, and noticed the same issue directly after the initial setup at the console.

Filed a bug report: https://redmine.pfsense.org/issues/4749