Description of problem: I thought I would give firewalld a try as a replacement for some home-brewed iptables and ip6tables rules. Much to my surprise it looks like it just might do the job. However, I was also surprised that both DHCPv4 and DHCPv6 server services were not standard definitions. Yes, it was easy enough to add the ports but with all of the other server services defined I thought that these should be too, If I had set the internal NIC to be zone trusted instead of internal, it would have worked. However, I suggest a "server" zone with more thought about just what should be there. Version-Release number of selected component (if applicable): Fedora 18, firewalld 0.2.12-2
I added a service for DHCPv6 server: https://git.fedorahosted.org/cgit/firewalld.git/commit/?id=789e5ac40edf0ddcc2014c06bbcffb055e907727 I don't think we need the same for DHCPv4 server because ISC DHCP(v4) makes use of raw sockets which bypass firewall completely, see https://deepthought.isc.org/article/AA-00378/0/Why-does-DHCP-use-raw-sockets.html
firewalld-0.3.4-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/firewalld-0.3.4-1.fc19
Package firewalld-0.3.4-1.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing firewalld-0.3.4-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-14046/firewalld-0.3.4-1.fc19 then log in and leave karma (feedback).
firewalld-0.3.4-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.