<p dir="ltr"><br>
On Feb 9, 2013 3:47 AM, "Aaron Gray" <<a href="mailto:aaronngray.lists@gmail.com">aaronngray.lists@gmail.com</a>> wrote:<br>
><br>
> On 7 February 2013 16:41, "Jóhann B. Guđmundsson" <<a href="mailto:johannbg@gmail.com">johannbg@gmail.com</a>> wrote:<br>
>><br>
>> On 02/07/2013 04:23 PM, Aaron Gray wrote:<br>
>>><br>
>>> 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 :-<br>
>>> <br>
>>> <a href="http://linux-sxs.org/internet_serving/pxeboot.html">http://linux-sxs.org/internet_serving/pxeboot.html</a><br>
>>> <br>
>>> Hope someone can help, I put I message on the User List but got no response.<br>
>>> <br>
>><br>
>><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>
><br>
> <br>
> Jóhann,<br>
> <br>
> That's okay so far, sort of makes sense, but I though firewalld had equivalent functionality to iptables. Anyway I still need a HOWTO on setting up a secondary DHCP on a second Ethernet controller in order to run PXEBOOT.<br>
> <br>
> Thanks for the reply anyway,<br>
> <br>
> Aaron<br>
> <br>
></p>
<p dir="ltr">Have you looked at <br>
<a href="http://docs.fedoraproject.org/en-US/Fedora/17/html/Installation_Guide/sn-pxe-server-manual.html">http://docs.fedoraproject.org/en-US/Fedora/17/html/Installation_Guide/sn-pxe-server-manual.html</a> ? If so, can you elaborate on what is missing? </p>