Search results

Jump to: navigation, search
  • ...server to forward PXE traffic to the FOG server. See [[Modifying existing DHCP server to work with FOG]] for assistance with this setting. <li><tt>Would you like to setup a router address for the DHCP server? [Y/n] Y</tt><br>
    5 KB (917 words) - 04:59, 30 July 2012
  • ...by the FOG installation script: PHP 5/7, MySql 5+/MariaDB 10+, Apache 2+, DHCP (pretty much any!), TFTP, FTP, NFS -s --startrange DHCP Start range
    11 KB (1,694 words) - 12:23, 19 May 2021
  • ...oughput and redundancy within a network. They do not provide PXE, TFTP, or DHCP services at secondary sites. To enable additional PXE and TFTP services at ...machines under FOG management must be within the same subnet/VLAN so that DHCP broadcast requests can be directed to the Main server. (see note below)
    57 KB (9,737 words) - 13:13, 30 March 2023
  • imgargs bzImage64 boot=live ip=dhcp edd=on noapic load_ramdisk=1 prompt_ramdisk=0 rw vga=normal sleep=0 logleve ...efi root=/dev/nfs boot=casper netboot=nfs nfsroot=${fog-ip}:${nfs_path} ip=dhcp splash quiet – || read void
    12 KB (1,873 words) - 23:00, 19 September 2017
  • ...append initrd=fog/images/noreg.gz root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns=10.1.1.1 type=down img=MYIMAGE ftp=10.1.1.1 storage=10.1.1.1:/images/ w '''ip=dhcp''' Change to your settings.<br>
    13 KB (2,241 words) - 04:13, 8 July 2016
  • #2 PCs on vlan 4 with IP address lease from DHCP (192.168.18.x) NOT from FOG server - connected to the 2520
    2 KB (309 words) - 10:21, 22 June 2011
  • * Capture and deploy images using DHCP, TFTP, and PXE * Capture and deploy images using DHCP, TFTP, and PXE
    3 KB (414 words) - 22:42, 18 August 2015
  • An existing network is assumed to have DHCP and DNS services already functioning on separate server(s), as well as full <li><tt> Would you like to setup a router address for the DHCP server? [Y/n] n</tt><br>
    5 KB (833 words) - 05:00, 30 July 2012
  • #REDIRECT [[Using FOG with an unmodifiable DHCP server/ Using FOG with no DHCP server]]
    87 bytes (14 words) - 02:30, 4 November 2011
  • === Create tftpd-map and alter configuration if using a separate DHCP server ===
    4 KB (575 words) - 04:21, 8 July 2016
  • for service in http https tftp ftp mysql nfs mountd rpc-bind proxy-dhcp; do firewall-cmd --permanent --zone=public --add-service=$service; ===DHCP & DNS===
    8 KB (1,235 words) - 19:46, 17 August 2018
  • append initrd=fog/images/init.gz root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns=*.*.*.* mode=autoreg web=*.*.*.*/fog/ loglevel=4 append initrd=fog/images/init.gz root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns=*.*.*.* mode=manreg web=*.*.*.*/fog/ loglevel=4
    3 KB (474 words) - 15:38, 3 March 2012
  • ...rver. The basic outline for the process is that we modify the FOG server's DHCP settings to allow it to talk to Macs, send over a GRUB2 boot.efi file with == Modifying your DHCP server to be able to communicate with a Mac==
    7 KB (1,062 words) - 13:47, 4 April 2012
  • ...ch time something triggers resolvconf. Instead,Networking38resolvconf uses DHCP client hooks, and /etc/network/interfaces to generate a list of nameservers
    1 KB (186 words) - 19:05, 9 May 2012
  • ...ng, you should be able to recover the server by copying 2 files back and a dhcp server restart (or the server itself). This is a modification from a guide 7. Edit /etc/dhcp/dhcpd.conf, replacing pxelinux.0 with gpxelinux.0
    3 KB (545 words) - 00:44, 30 January 2013
  • append initrd=fog/images/bypass.gz root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns=YOURDNSSERVER type=down img=YOURIMAGE ftp=FOGSERVERIP storage=FOGSERVER
    3 KB (549 words) - 02:13, 31 January 2013
  • **Type Y and press Enter to setup DHCP Server address. **Enter the DHCP Server address. If it's going to be the FOG Server, set it to the same IP
    6 KB (1,001 words) - 20:04, 11 February 2015
  • #* Type Y and press Enter setup DHCP Server. #* Enter the IP Address associated with your DHCP Server
    9 KB (1,526 words) - 04:27, 8 July 2016
  • = Change your DHCP Option 67 = # Go to your DHCP server and change your Option 67 from ''pxelinux.0'' to '''undionly.kpxe'''
    8 KB (1,323 words) - 04:26, 8 July 2016
  • ...our dhcp server (and it most likely you won't be) make SURE to change your dhcp boot-filename (option 67) to undionly.kpxe
    2 KB (368 words) - 20:19, 13 January 2015

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)