• I have a in home network with fog that i use to work on peoples systems almost daily. I also used a ddwrt router that recently died. It was becuaSe of this I chose to seek new options. Pfsense was that new option and i must tell you i am so happy with that option. with pfsense you don’t have to worry with what ipxe file to call upon as you can select it via pfsenses configuration even based upon a per machine bases. so if your environment is uefi & bios based those options are easily configured even down to the specific machine type as relates to what kind o file you want the fog server to call. I mean it is far easier than trying to use dnsmasq to call a certain file.

    for example under Services/DHCP Server/LAN/Edit Static Mapping you can select a certain boot file based upon the settings at Services/DHCP Server/LAN = network booting tab.

    Bottom line pfsense is great to use with fog and makes it a snap to get uefi and bios booting coexistence up and running

  • muchas gracias!!! me servira de mucho y voy a realizar pruebas

  • Moderator

    @lalo Here is how you set it up

    1. Services->DHCP Server
    2. Select the interface where the dhcp server is running
    3. Scroll down the page and select the network booting button.
    4. Fill out the form as below

  • @george1421 En efecto uso pfsense para servidor de dhcp. Y no hay pasos previos de integración de los servidores!!

  • Moderator

    @lalo said in PFSENSE!!!!! is great:

    tendrás una metodología de instalación y configuración del servidor fog y pfsense…

    The connection between FOG and pfSense is pretty simple. I guess that you use pfsense for dhcp server? If so there are only a few fields that must be filled out. I can provide a screen shot of the settings in about 1 hour if you need them.

  • tendrás una metodología de instalación y configuración del servidor fog y pfsense…

  • @george1421 I sure have disabled it but I kept the file for when I transport my fogserver to setup business sites. So it all comes in handy.

  • @Wayne-Workman Fabulous!!! I shall give it a try in a virtual machine. Feed back to follow.

  • I built my own routing management software: https://github.com/wayneworkman/OpenVPNRouter
    Doesn’t have bells and whistles or a pretty web interface yet, but it routes, NATs, does firewall, prevents DNS snooping by forcefully rerouting all DNS queries to my chosen DNS server, sends my whole house’s traffic through a PIA VPN transparently, does DHCP, and emails me my Public IP every time I get a new one, and does port forwarding too, and has automatic “healing” for when the VPN connection goes down.

    The project could use a whole lot of love, I could do so much with it. I’m just less interested in making it better now. I’m pursuing other things at the moment.

  • Developer

    I couldn’t agree more!

    And being opensource, it has the ability to do more than just DHCP and routing.

    I use my pfsense router as a webfilter and also use it for NAT/internet rules (I shut my internet off at night except for certain devices).

    I love the control that pfsense gives you, and I also enjoy the easy set up with fog 😉

  • Moderator

    I agree with you that pfsense is a pretty great solution. I’ve used it for both a firewall as well as an application platform. It is a solid FOSS solution.

    As to your migration, don’t forget to turn of dnsmasq on your fog server now. Its not needed if pfsense is handing out the right file names for your network.