@Wayne-Workman
damn. I couldn’t imagine, that this is so easy… sorry.

My system is Ubuntu Server 14.04.3.
I cannot fully understand why but this worked for me:

First add the proxy with:
export http_proxy=http://username:password@host:port/
export https_proxy=https://username:password@host:port/

Then put in /etc/sudoers:
Defaults env_keep=“https_proxy”

Last:
start the installfog.sh as root and not as sudo

Now it’s better - I still get the Info

 * Setting up storage..........................................OK
 * Setting up and starting DHCP Server......................... !!! No router address found !!!
 !!! No dns address found !!!
OK
 * Setting up and starting TFTP and PXE Servers................OK

but the script continues and everything seems to be ok.

@Wayne-Workman
yes in both files are the addresses set correctly

@Wayne-Workman I really don’t want to dissapoint you
I’ve updated now to the svn 6755 and still get the ! ! ! No router address found ! ! ! and ! ! ! No dns address found ! ! !
How I said before - the setup is complete and everything seems to work. I only get these two “warnings”

Here is my .fogsettings:

## Start of FOG Settings
## Created by the FOG Installer
## Version: 6755
## Install time: Sat 12 Mar 2016 05:58:49 PM CET
ipaddress='192.168.94.111'
interface='eth0'
submask='255.255.255.0'
routeraddress='192.168.94.1'
plainrouter='192.168.94.1'
dnsaddress='192.168.94.1'
dnsbootimage='192.168.94.1'
username='fog'
password="XXXXXX"
osid='2'
osname='Debian'
dodhcp='Y'
bldhcp='1'
blexports='1'
installtype='N'
snmysqluser=''
snmysqlpass=""
snmysqlhost=''
installlang=''
donate='0'
storageLocation='/images'
fogupdateloaded=1
docroot='/var/www/html/'
webroot='fog/'
caCreated='yes'
startrange='192.168.94.60'
endrange='192.168.94.99'
bootfilename='undionly.kpxe'
packages='apache2 php5 php5-json php5-gd....
noTftpBuild=''
notpxedefaultfile=''
sslpath='/opt/fog/snapins/ssl/'
## End of FOG Settings

And this is the dhcpd.conf:

...
next-server 192.168.94.111;
# Specify subnet of ether device you do NOT want service.
# For systems with two or more ethernet devices.
# subnet 136.165.0.0 netmask 255.255.0.0 {}
subnet 192.168.94.0 netmask 255.255.255.0{
    option subnet-mask 255.255.255.0;
    range dynamic-bootp 192.168.94.60 192.168.94.99;
    default-lease-time 21600;
    max-lease-time 43200;
    option routers 192.168.94.1;
    option domain-name-servers 192.168.94.1;
...

Perfect now! Installer and configs are all correct. From my side the problem is solved. Thanks!

I don’t know if it has to do something with the timeout issue but in /etc/default/grub I added

GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0"

because we want to use eth0 name instead of enp1s0.

I changed manually the kernels in /var/www/html/fog/service/ipxe/ to the 4.15.2 Kernel.

Now I get eth0 instead of enp1s0:

Starting syslogd: OK
Starting klogd: OK
Running sysctl: OK
Populating /dev using udev: done
Saving random seed: OK
Staring haveged: haveged: listening socket at 3
OK
Starting eth0 interface and waiting for the link to come u

With the older kernel the issue with the timeout is gone.

@Sebastian-Roth
I went through the wiki article and everything seems to be fine.

I saw that fog is downloading the kernels twice if you do an update. First time if you expand the kernel you want to download and click on “download”. (Kernel will be downloaded as “bzImage”) The second time after you enter the kernel name and click on “install” - this time the kernel will be downloaded with the new name.

@Sebastian-Roth
any ideas regarding the issue with the kernel update?
I disabled the virtual interface and run the 1.5.8 installer again and tried the kernel update - still get the error with ftp_rename() I mentioned in my first post.

My system: ubuntu server 18.4.4

@george1421
I disabled the virtuel interface and changed all settings to the 192.168.111.8 ip address of the fog server.
It seems to work a little better but still the clients are often running into timeouts after the fog menu.
FOG and the client are both connected with the tp-link switch and nothing else

@Sebastian-Roth
i noticed, that the installation process (or ./installfog.sh) is generating a strange netmask in the dhcpd.conf, if a virtuel interface is configured:
network settings of system:

auto eth0
iface eth0 inet static
address 192.168.111.8
netmask 255.255.255.0
gateway 192.168.111.1

dns-nameservers 192.168.111.1 192.168.100.100

virtuel interface:

auto eth0:0
iface eth0:0 inet static
    address 192.100.1.1
    network 192.100.1.0

generated DHCP settings:

subnet 192.32.1.0 netmask 255.255.255.0{
    option subnet-mask 255.255.255.0;
    range dynamic-bootp 192.168.111.10 192.168.111.254;
    default-lease-time 21600;
    max-lease-time 43200;
    option routers 192.168.111.1;
    option domain-name-servers 192.168.111.1;
    next-server 192.168.111.8;

if I disable the virtuel interface before running installfog.sh, everything is ok then.

I manually change all network settings to the 192.100.1.x after the script is finished.

@george1421
I tried to do a quick registration 10 times with my unmanaged tp-link switch and in 6 of 19 cases the client pc didn’t get an ip address and ran into the timeout.
In that cases, where the client got an ip address, the client waited at least 15 seconds until it got the dhcp address from fog.

@Sebastian-Roth

TFTP HOST is set to 192.100.1.1.

Tproblem:
Booting and getting into the FOG menu is working everytime.
In most cases after choosing fog registration, quick image or fog sysinfo, fog is running into the timeout mentioned before - but sometimes it works and the client is getting an ip address and doing the registration or fog is deploying the image. I would say, every 4th time it seems to work.

I tried fog 1.5.8 and 1.5.9-RC1. Both versions have problems with providing DHCP addresses after the fog menu items.

I thought maybe it has something to do with the kernel, so tried to change the used kernel and ran into the update problem with the kernel.

Here the output:

drwxr-xr-x 2 fogproject www-data     4096 May 12 20:23 .
drwxr-xr-x 3 www-data   www-data     4096 May 12 19:56 ..
-rw-r--r-- 1 fogproject www-data     1966 May 12 19:56 advanced.php
-rw-r--r-- 1 fogproject www-data    16272 May 12 19:56 bgdark.png
-rw-r--r-- 1 fogproject www-data    21280 May 12 19:56 bg.png
-rw-r--r-- 1 fogproject www-data     1139 May 12 19:56 boot.php
-rw-r--r-- 1 fogproject www-data  8438432 May 12 19:57 bzImage
-rw-r--r-- 1 fogproject www-data  7836480 May 12 19:57 bzImage32
-rw-r--r-- 1 fogproject www-data   234697 May 12 19:56 grub.exe
-rw-r--r-- 1 fogproject www-data      592 May 12 19:56 index.php
-rw-r--r-- 1 fogproject www-data 20315484 May 12 19:57 init_32.xz
-rw-r--r-- 1 fogproject www-data 20891504 May 12 19:57 init.xz
-rw-r--r-- 1 fogproject www-data    25340 May 12 19:56 memdisk
-rw-r--r-- 1 fogproject www-data  1839104 May 12 19:56 memtest.bin
-rw-r--r-- 1 fogproject www-data   202624 May 12 19:56 refind_aa64.efi
-rw-r--r-- 1 fogproject www-data    29719 May 12 19:56 refind.conf
-rw-r--r-- 1 fogproject www-data   262592 May 12 19:56 refind.efi
-rw-r--r-- 1 fogproject www-data   201600 May 12 19:56 refind_ia32.efi
-rw-r--r-- 1 fogproject www-data   208776 May 12 19:56 refind_x64.efi

In many different subnets we don’t have a dhcp server and dont have free Ip addresses in that small subnets. So we decided to use in every subnet the same fog-configuration. The problem is, that we normally don’t have so many IP addresses available in the subnet, where the fog is acting.
With the virutal interface FOG is providing as many IP addresses to the clients as we want and the fog server is set as the router address.
The IP addresses are only for temporary cases until they get the right ip address.

If there is another possibility to let fog use another network for providing images, let me know. I didn’t find anything.

Hello guys,

I try do download and activate a new kernel. The web interface is saying “Your new FOG Kernel has been installed!” but in the apache error log I get:

[Tue May 12 20:25:35.105748 2020] [proxy_fcgi:error] [pid 22243] [client 192.168.100.16:61051] AH01071: Got error 'PHP message: PHP Warning:  ftp_mkdir(): Create directory operation failed. in /var/www/html/fog/lib/fog/fogftp.class.php on line 493\nPHP message: PHP Warning:  ftp_rename(): Rename failed. in /var/www/html/fog/lib/fog/fogftp.class.php on line 808\n', referer: http://192.168.111.8/fog/management/index.php?node=about&sub=kernel&file=aHR0cHM6Ly9mb2dwcm9qZWN0Lm9yZy9rZXJuZWxzL0tlcm5lbC5Ub21FbGxpb3R0LjQuMTkuMTAxLjY0&arch=64

Maybe the issue is because I try to use FOG with an virtual interface: FOG is running with eth0:1 with IP 192.100.1.1 and the normal IP address is 192.168.111.8

The second issue is, that often fog is not providing an ip address if I want to image or register the client

I get something like:

Starting syslogd: OK
Starting klogd: OK
Running sysctl: OK
Populating /dev using udev: done
Saving random seed: OK
Staring haveged: haveged: listening socket at 3
OK
Starting enp1s0 interface and waiting for the link to come up
No link detected on enp1s0 for 35 seconds,skipping it.
Failed to get an IP via DHCP! Tried on interfaces(s): enp1s0
Please check your network setup and try again!
Press enter to continue

@george1421 We had to switch earlier, you’re right. I thought there is maybe possible to create a ubuntu image, which is supporting both hardware types. There are about 500 computers with legacy and the next hardware will run on uefi.

If we reimage the 500 players, they won’t run as the uefi is not activated in the bios…