Modifying existing DHCP server to work with FOG

From FOG Project
Revision as of 14:38, 6 June 2014 by Tom-elliott.7271 (talk | contribs) (→‎Cisco)
Jump to: navigation, search

Modifying existing DHCP server to work with FOG

If you already have a DHCP server setup on your network you don't want two. So if you chose to not install DHCP during FOG installation you will need to set some options in your current DHCP server to point PXE services to the FOG server.

Windows

0.32 and below

To set options 066 and 067 on Windows Server:

  1. Open DHCP configuration Start > Administrative Tools > DHCP.
  2. Then expand your server, expand the applicable scope (often only one is there)
  3. right click on Scope Options
  4. click Configure Options
  5. tick 066 and enter the IP Address of the FOG server
  6. tick 067 and enter pxelinux.0 (thats a zero).
  7. Make sure that 060 is unticked.

For a video walk through jump to 6:44, on: http://www.youtube.com/user/hotfortech#p/a/u/1/Ak6kfvGM0Dk

0.33 and up

To set options 066 and 067 on Windows Server:

  1. Open DHCP configuration Start > Administrative Tools > DHCP.
  2. Then expand your server, expand the applicable scope (often only one is there)
  3. right click on Scope Options
  4. click Configure Options
  5. tick 066 and enter the IP Address of the FOG server
  6. tick 067 and enter undionly.kpxe.
  7. Make sure that 060 is unticked.

For a video walk through jump to 6:44, on: http://www.youtube.com/user/hotfortech#p/a/u/1/Ak6kfvGM0Dk

Linux

0.32 and below

If you would like to use an existing Linux based DHCPD server you will need to perform the following steps:

  1. Edit your dhcpd.conf file (ie: vim /etc/dhcpd.conf)
  2. In the global section or in a subnet declaration add next-server X.X.X.X; and filename "pxelinux.0"; where X.X.X.X is the IP of your FOG server.
  3. Restart your dhcpd server (ie: service dhcpd restart)

0.33 and up

If you would like to use an existing Linux based DHCPD server you will need to perform the following steps:

  1. Edit your dhcpd.conf file (ie: vim /etc/dhcpd.conf)
  2. In the global section or in a subnet declaration add next-server X.X.X.X; and filename "undionly.kpxe"; where X.X.X.X is the IP of your FOG server.
  3. Restart your dhcpd server (ie: service dhcpd restart)

Cisco

If you would like to use a DHCP-enabled Cisco router you will need to perform the following steps:

0.32 and below

  1. Enter priveleged mode (enable).
  2. If you don't know your DHCP pool name, enter show running-config and look for ip dhcp pool in the output.
  3. Enter global configuration mode (configure terminal).
  4. Enter DHCP scope configuration mode (ip dhcp pool <pool name>).
  5. Configure the following options:
    1. next-server <ip address to fog server>
    2. bootfile pxelinux.0
  6. Exit configuration mode by entering exit twice.
  7. Save your configuration (copy running-config startup-config).

0.33 and up

  1. Enter priveleged mode (enable).
  2. If you don't know your DHCP pool name, enter show running-config and look for ip dhcp pool in the output.
  3. Enter global configuration mode (configure terminal).
  4. Enter DHCP scope configuration mode (ip dhcp pool <pool name>).
  5. Configure the following options:
    1. next-server <ip address to fog server>
    2. bootfile undionly.kpxe
  6. Exit configuration mode by entering exit twice.
  7. Save your configuration (copy running-config startup-config).

DD-WRT & Tomato

0.32 and below

If you would like to use a DD-WRT or Tomato router for DHCP you will need to perform the following steps:

  1. Go to the Services tab
  2. Enable DNSMasq, and Local DNS
  3. Under Additional DNSMasq Options add the following dhcp-boot=pxelinux.0,,X.X.X.X where X.X.X.X is the IP of your FOG server
  4. Save/Apply settings

Please see our knowledge base article Can I use my existing DD-WRT enabled routers DHCP Server? for more information on this.

0.33 and up

If you would like to use a DD-WRT or Tomato router for DHCP you will need to perform the following steps:

  1. Go to the Services tab
  2. Enable DNSMasq, and Local DNS
  3. Under Additional DNSMasq Options add the following dhcp-boot=undionly.kpxe,,X.X.X.X where X.X.X.X is the IP of your FOG server
  4. Save/Apply settings

Please see our knowledge base article Can I use my existing DD-WRT enabled routers DHCP Server? for more information on this.

Extra Information

The dhcp-boot information from Tomato and DD-WRT is exactly the same information dnsmasq uses. This is because dnsmasq is the default dhcp server for these routers.

OpenWRT

0.32 and below

If you would like to use an OpenWRT router for DHCP you will need to perform the following steps:

  1. Edit etc/config/dhcp
  2. In chapter config 'dnsmasq' add this line: option 'dhcp_boot' 'pxelinux.0,fog,X.X.X.X' where X.X.X.X is the IP of your FOG server
  3. Save the dhcp file
  4. Restart dnsmasq: /etc/init.d/dnsmasq restart

This config has been tested on OpenWRT Attitude Adjustment (r28247).

0.33 and up

If you would like to use an OpenWRT router for DHCP you will need to perform the following steps:

  1. Edit etc/config/dhcp
  2. In chapter config 'dnsmasq' add this line: option 'dhcp_boot' 'undionly.kpxe,fog,X.X.X.X' where X.X.X.X is the IP of your FOG server
  3. Save the dhcp file
  4. Restart dnsmasq: /etc/init.d/dnsmasq restart

This config has been tested on OpenWRT Attitude Adjustment (r28247).

Sonicwall

0.32 and below

If your Sonicwall device is acting as the DHCP server, you will need to perform the following steps:

  1. Login to your Sonicwall web admin interface
  2. Go to Network > DHCP Server
  3. Edit the DHCP Range where your client(s) reside
  4. Click the tab labeled Advanced
  5. Under "Network Boot Settings," configure the following options:
    1. Next Server: X.X.X.X where X.X.X.X is the IP of your FOG server
    2. Boot File: pxelinux.0
  6. Click OK to save

0.33 and up

If your Sonicwall device is acting as the DHCP server, you will need to perform the following steps:

  1. Login to your Sonicwall web admin interface
  2. Go to Network > DHCP Server
  3. Edit the DHCP Range where your client(s) reside
  4. Click the tab labeled Advanced
  5. Under "Network Boot Settings," configure the following options:
    1. Next Server: X.X.X.X where X.X.X.X is the IP of your FOG server
    2. Boot File: undionly.kpxe
  6. Click OK to save

Note that the "Windows" DHCP Options 66 and 67 do not work in Sonicwall DHCP Server. You must use the fields provided by Sonicwall - Next Server and Boot File.Brachytherapy

pfSense v1.23

0.32 and below

If your pfSense device is acting as the DHCP server, you will need to perform the following steps:

  1. Login to your pfSense web admin interface
  2. Go to Services > DHCP Server
  3. Scroll Down to "Enable Network booting" Click the button labeled Advanced to "Show Network booting" options
    1. Check the box to "Enables network booting"
    2. Enter the IP address from the network boot server: X.X.X.X where X.X.X.X is the IP of your FOG server
    3. Enter the filename used for network booting: pxelinux.0
  4. Click the Save button

0.33 and up

If your pfSense device is acting as the DHCP server, you will need to perform the following steps:

  1. Login to your pfSense web admin interface
  2. Go to Services > DHCP Server
  3. Scroll Down to "Enable Network booting" Click the button labeled Advanced to "Show Network booting" options
    1. Check the box to "Enables network booting"
    2. Enter the IP address from the network boot server: X.X.X.X where X.X.X.X is the IP of your FOG server
    3. Enter the filename used for network booting: undionly.kpxe
  4. Click the Save button

Note: You need both a filename and a boot server configured for this to work!

Other DHCP Servers

Retrieved from "https://wiki.fogproject.org/wiki/index.php?title=Modifying_existing_DHCP_server_to_work_with_FOG&oldid=8013"