<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 02/07/2013 04:23 PM, Aaron Gray
wrote:<br>
</div>
<blockquote
cite="mid:CANkmNDfJJLdhTk+8w==yMKRsEKpteJ6ZgXjWW5Shob2OzHbyZA@mail.gmail.com"
type="cite">
<meta http-equiv="Context-Type" content="text/html;
charset=ISO-8859-1">
<div>Can someone who knows firewalld please do a HOWTO to on
setting up a secondary DHCP with DNS and HTTPS access for
PXEBOOTing of Fedora18 please to go with the PXEBOOT HOWTO :-</div>
<div> </div>
<div> <a moz-do-not-send="true"
href="http://linux-sxs.org/internet_serving/pxeboot.html">http://linux-sxs.org/internet_serving/pxeboot.html</a></div>
<div> </div>
<div>Hope someone can help, I put I message on the User List but
got no response.</div>
<div> <br>
</div>
</blockquote>
<br>
Well what seems to be standards sysadmin practice with firewalld on
servers is to disable it and enable iptables. <br>
<br>
Firewalld is aimed at desktop users and roaming hardware which makes
"zones" useless concept for static server within an corporate
infrastructure.<br>
<br>
So the missing steps for your guide simply are...<br>
<br>
systemctl stop firewalld*<br>
systemctl disable firewalld*<br>
systemctl enable iptables.service <br>
systemctl start iptables.service<br>
<br>
JBG<br>
</body>
</html>