@george1421 ok, I was able to get the port to stick, so here is a screenshot of all of the open ports now.
but we are still getting the no route to host. Is there a port I am missing? Any idea why its doing that? it has to be something with that port not working right or something. when we turn the firewall off, it works just fine, but when we turn the firewall on, we get no route to host.
@george1421 ok, I have it up and running on Rocky Linux, but I am still having the firewald issue where when I create rule 2049/udp it doesn’t show, so when I try to add it manually in the xml file firewalld crashes. any idea how I can get the port to stick in firewalld?
Cant seem to get it going, so im going to try bringing FOG online using rocky linux since its based off of RHEL, and thats what im more familiar with. I will let you know how it goes.
@george1421 I redid all of the rules and just put in the fog ports, ssh, and webmin ports. ufw now looks like this:
is there any other ports or icmp requests I should open? sorry, I am not that familiar with ufw.
@george1421 ok, it halts at tftp and times out.
here are the firewall rules I have. which ones do i need to change or fix?
@george1421 ok, I have added that port. I am not onsite, as i remote in so I am waiting to see if someone onsite can test and get back to me.
@george1421 ok, I have reinstalled ufw. and removed firewalld. will let you know how it goes. here are my rules, do these look ok?
let me know if there are any rules I need to delete or change.
@george1421 I uninstalled ufw/iptables because I prefer firewalld. I used to use Centos, but as centos is now EOL, im having to switch all of our servers over to debian, and firewalld is what im familiar with. but I can’t seem to open port 2049/udp in firewalld for some reason.
We have stopped firewalld for now, and imaging works as expected. I have shown above, I have tried inputing the port via webmin and via commandline and it says its there when I try to add it via command line, so it doesn’t add it again. I might have to bite the bullet and just go with ufw/iptables (they are the same right? I am not that familiar with ufw).
@george1421 We have narrowed it down to an issue with firewalld. no matter how I try to input the rule to allow port 2049/udp it doesn’t stick. I can look the user created rules in /etc/firewalld/zones/public.xml and I can see all of the other ones, but not the one for port 2049/udp. I have gried webmin as well as command line to allow port 2049/udp and it doesn’t seem to want to stick if I use webmin, and if I use commandline it says its already there. when I try to do it via command line I get the following error:
user@imaging:/etc/firewalld/zones# firewall-cmd --permanent --zone=public --add-port=2049/udp
Warning: ALREADY_ENABLED: 2049:udp
success
but when you view the xml file you can see its not listed. here is the contents of /etc/firewalld/zones/public.xml
<?xml version=“1.0” encoding=“utf-8”?>
<zone>
<short>Public</short>
<description>For use in public areas. You do not trust the other computers on networks to not harm your computer. Only selected incoming connections are accepted.</description>
<service name=“ssh”/>
<service name=“dhcpv6-client”/>
<service name=“http”/>
<service name=“https”/>
<port port=“10000” protocol=“tcp”/>
<port port=“69” protocol=“udp”/>
<port port=“1024-65535” protocol=“udp”/>
<port port=“2049” protocol=“tcp”/>
<port port=“111” protocol=“tcp”/>
<port port=“111” protocol=“udp”/>
</zone>
Any ideas on how I can get this to work?
@george1421 here are the results of the above:
here is the instructions
here is the ping to the fog server:
Here is the results of the ip a s command:
and then once typing fog to continue with the boot we are getting the following null error:
any idea where we go from here? the subnet is 255.255.255.0 or /24 cidr so it is correct
I should also mention we had a working FOG server on 1.5.9 running Centos 7, but since the entire Centos distro line is now EOL, I am working to migrate all of our servers over to Debian 11. The DHCP server is a Windows Server 2016 server, but there shouldn’t be any changes needed there as it was working with the other server. All we did was change the OS to a different supported distro, and install the latest version.
yes, the computer is on the same subnet. I have also disabled ipv6. attaching a screenshot of all open ports on the server as well.
hello, I am trying to capture an image on a fresh install of fog on debian 11. I have installed the latest version 1.5.10. I am including a picture of what I get when I try to capture an image. 
Anyone know how I can resolve this issue?
hi, when I do that, it gives me a file called TFTP1168. it takes a bit to connect, but then gives me that file. I am using the command tftp 10.4.47.15 ipxe.efi c:\users\kstevens
@george1421 the server is active and running just fine. We can get into the web interface, ping and everything just fine, and I check the network and don’t find any issues with the network either.
Hi, I have a new fog installed and when we boot to the network, it sits at mtftp for like 5 minutes before we get the fog boot menu. I ssh in and it says the Tito server is inactive/dead so I restart it and it works fine for a few minutes. But then we get back to waiting at mtftp for 5 minutes again. What is happening and how do I fix it? It’s running on a server 2016 hyper-v on centos 7
Hello, I have created a couple of snapins to deploy some applications that end in filename.exe. however both of teh snapins are not being deployed. does anyone know what I might be doing wrong
Hello @george1421 I have tried both bios and uefi. and I get the same issue.