This seems to have been asked again and and again and I have found no clear solution bare the superbly elegant one posted here in this closed thread that I am continuing:
Kudos to @trendy for actually clarifying the simple easy way to do this. Like many I have OpenWRT installed on some WAPs/switches and I don't want them playing any role at all whatsoever in dhcp or dns service, just be WAPS and switches.
But here's the crunch, I check the completeness of the disable with netstat to see what's listening and after disabling and stopping dnsmasq and odhcp as @trendy suggested I still see:
# netstat -tulpen
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 959/uhttpd
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 810/dropbear
tcp 0 0 :::80 :::* LISTEN 959/uhttpd
tcp 0 0 :::22 :::* LISTEN 810/dropbear
udp 0 0 :::546 :::* 1188/odhcp6c
Yes, odhcp6c is still listening on port 546. Grrrr.
@bernd-wechner have you checked some other tips from the page below?
I personally ended up doing a custom build removing all packages not needed for an access point (removed all IPv6 support, dnsmasq, firewall, etc and installed only base LuCI).
Is that useful? A lot of detail and background reading demanded for me to understand all these settings (even then the docs are not always fulfilling alas).
Oh, I see. The c in odhcp6c is for "client"? Correct?
Puzzles me why a DHCP client has a IPv6 listener and not an IPv4 listener and why it needs a listener at all (isn't the DHCP request broadcast and the DHCP offer also broadcast on the local LAN?) Just curious - ever learning and ever curious.
Ah, well, it's not WAN facing. But I guess if the LAN DHCP server started issuing IPv6 addresses it's still used for that too. But from what @vgaetera suggests this is part of the IPV6 protocol suite (A reconfigure message) which perhaps doesn't exist in the IPv4 DHCP protocol and hence no listener needed.