@Sebastian-Roth I don’t think it’s necessary unless you just want to do it for kicks. I abandoned it and went with CentOS 7 and was able to get up and running

@george1421 Sorry for the confusion. Installing dnsmasq on the system-v wasn’t the problem, it is indeed with the installer. Installing dnsmasq on a systemd distro has been the headache but I think I may have got it all sorted out. Fingers crossed.

@Sebastian-Roth It maybe too much of a hassle either way. I’m simply trying to get dnsmasq to work as a proxydhcp cause I don’t want to modify my existing dhcp. I can’t install dnsmasq cause systemd-resolved uses the same port. I can’t get systemd-resolved to stop using that port so I can install dnsmasq. stopping it, disabling it. It’s a real pain in the butt. I noticed that there is a fog tutorial on how to use dnsmasq and centos… unfortunately I can’t find one for ubuntu based distros. So you can just close this question and I’ll keep fumbling around until I get it to work.

Is there a version of the fog installer that doesn’t rely on systemctl to run? I’m using Devuan which is debian based but doesn’t include systemd which is the way I like it. However the installer for FOG keeps calling systemctl to install. Is there a way around this or am I just going to have to abandon FOG cause I’m not going to systemd.

@Sebastian-Roth I get No errors. It just endless loops to the same question over and over again until you manually type in the adapter.

@Tom-Elliott changing the setup and plugging directly into a 24 port cisco switch had no effect. I can work around it, I just thought maybe it was a bug in the installer.

@cromag I suppose it could be a setup issue. My setup is a bit different that the original OP. Let me switch some stuff around. I am running the “server” from a port on my work phone so that might have something to do with it. Let me see if hard wiring it directly to a switch fixes the issue.

I too am having the same issue. Choosing defaults or No results in an endless loop of the FOG installer asking if you want to change the default network interface. The only way to get around it is to choose yes and then type in the interface manually.

Would you like to change the default network interface from enp1s0 wlp2s0?
If you are not sure, select No. [y/N] Y
What network interface would you like to use? enp1s0
Fog.1.5.7 running on an ubuntu distro variant. Have had it happen on two different distros. Zorin and Peppermint.

default via 10.10.128.1 dev enp1s0 proto dhcp metric 100 
10.10.128.0/24 dev enp1s0 proto kernel scope link src 10.10.128.87 metric 100 
169.254.0.0/16 dev enp1s0 scope link metric 1000

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether 00:ce:39:cf:2c:53 brd ff:ff:ff:ff:ff:ff
3: wlp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DORMANT group default qlen 1000
    link/ether f4:d1:08:6f:f4:5a brd ff:ff:ff:ff:ff:ff