Request for a firewalld secondary DHCP + PXEBOOT HOWTO

[Aaron Gray]

On 14 February 2013 19:16, Pete Travis <lists at petetravis.com> wrote:

>  On Feb 14, 2013 12:03 PM, "Pete Travis" <lists at petetravis.com> wrote:
> >
> >
> > On Feb 9, 2013 3:47 AM, "Aaron Gray" <aaronngray.lists at gmail.com> wrote:
> > >
> > > On 7 February 2013 16:41, "Jóhann B. Guðmundsson" <johannbg at gmail.com>
> wrote:
> > >>
> > >> On 02/07/2013 04:23 PM, Aaron Gray wrote:
> > >>>
> > >>> 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 :-
> > >>>
> > >>>     http://linux-sxs.org/internet_serving/pxeboot.html
> > >>>
> > >>> Hope someone can help, I put I message on the User List but got no
> response.
> > >>>
> > >>
> > >>
> > >> Well what seems to be standards sysadmin practice with firewalld on
> servers is to disable it and enable iptables.
> > >>
> > >> Firewalld is aimed at desktop users and roaming hardware which makes
> "zones" useless concept for static server within an corporate
> infrastructure.
> > >>
> > >> So the missing steps for your guide simply are...
> > >>
> > >> systemctl stop firewalld*
> > >> systemctl disable firewalld*
> > >> systemctl enable iptables.service
> > >> systemctl start iptables.service
> > >>
> > >
> > >
> > > Jóhann,
> > >
> > > 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.
> > >
> > > Thanks for the reply anyway,
> > >
> > > Aaron
> > >
> > >
> >
> > Have you looked at
> >
> http://docs.fedoraproject.org/en-US/Fedora/17/html/Installation_Guide/sn-pxe-server-manual.html? If so, can you elaborate on what is missing?
>
> Oops, that should be
> http://docs.fedoraproject.org/en-US/Fedora/18/html/Installation_Guide/sn-pxe-server-manual.html
>
Pete,

Yeah that's the easy bits, they need details too. The bit I have yet to
find out how to do is to forward HTTPS and DNS ports between the
primary internet network and the secondary DHCP BOOTP network on
192.168.1.x. I had this working on Shorewall but have taken the time to
work it out on iptables or firewalld ideally and was hoping for a quick fix
without having to reread iptables docs or learn firewalld configuration.

Cheers for the link,

Aaron


> --
> devel mailing list
> devel at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/devel/attachments/20130215/a9a19b81/attachment-0001.html>