@george1421 Yup that did it! It was a combination of the Fog server’s firewall as well as my trying to connect to the web interface using the imaging network’s IP instead of the business network IP. Once I disabled the firewall again and tried the other IP I was able to finally reach the web interface.
Thanks for the help!
@george1421 Alright, so I’m able to ping the IP of the Fog server’s business network nic, just not the IP of the imaging network nic. And that’s the IP that the web interface is on. The imaging network is isolated which is why I originally asked how I will be able to reach the web interface if it’s on the isolated network’s IP.
@Zerpie If it helps, I followed the directions to a T from the Fedora Server 25 installation wiki https://wiki.fogproject.org/wiki/index.php?title=Fedora_25_Server
And then followed your directions from this thread once I got to the running the Fog installer portion at the bottom.
@george1421 I’m running it on Fedora Server 28.
@george1421 I can ping devices on my network from the Fog server.
I did disable firewalld on the Fog server.
And yes, I removed the gateway from the imaging network interface. I checked on this by running the common “route” and it shows 0.0.0.0 for my imaging network interface, but it also shows 0.0.0.0 for the business network interface as well. Not sure if that’s an issue.
Finally, I ran “ip route” and I’m not sure what all of this means. I censored the IPs of the business network. Not sure if that even matters.
default via x.x.x.254 (The ip of the gateway for the business network interface) dev ens224 proto static metric 101
x.x.x.0/24 (business network) dev ens224 proto kernel scope link src x.x.x.171 (ip of the business network interface) metric 101
153.86.19.0/24 (imaging network) dev ens192 proto kernel scope link src 153.86.19.10 metric 100
I’m far from a networking expert or a Linux expert so I apologize if I’m making any glaring mistakes, but I’m eager to learn as much as I can. The task of finding a new imaging solution was kinda tossed my way after our old IT manager/sysadmin left.
@george1421 said in Fog Server Setup With Two Network Cards For Isolation:
netstat -an|grep -e “:80”
I cannot ping the fog server from the business network. I ran that command and I got the exact same result that you show there. I will need to take my laptop to another part of the building to get onto the imaging network to see if I can reach the web UI for there. I’ll let you know.
@george1421 Awesome! I gave that a try, but once again when it asks me to log into the web UI it is not reachable from the business network that I’m connected to.
I’m not sure if there’s something weird about how our network is setup that is not allowing me to reach out to it, but as you said, the web server will bind to all interfaces. Not sure what I might be missing.
I’ve also disabled the firewall on the Fog server because I’ve seen that mess with being able to access the web UI as well. Still no go, though. I appreciate all your help, George.
@george1421 Thank you for that. When I’m installing Fog do I also want to specify the IP of the imaging network when it asks “What is the IP address to be used by this FOG Server?” Because it’s defaulting to the IP of the business network.
I’m so glad that I’ve stumbled across this thread because this is exactly the type of setup I’m going for with my Fog server.
The first issue I’m running into is how to reach the web interface from the business network if the web interface is hosted on the isolated network. Is that possible? Or will I need to set the Fog server up on a physical machine and log into the web UI at the actual machine? I’m currently trying to setup my server as a VM.
@Wayne-Workman said in Fog tftp only works when I disable firewalld:
sestatus
Turns out this time around it was me not entering the correct info during the install. Wrong router address for the DHCP server and wrong address entered on the DHCP server for option 66. When I ran the installer again this morning I realized what I did wrong right away. So far so good right now…
And it looks like I’ve run into my first new issue on a fresh install. I’ve just run the Fog installer and got to the bit to install/update the database schema, but I am unable to reach the web interface. Not sure where to go from here.
@tom-elliott You’re right, I should have come to the forums much earlier when I started having trouble. The good news is that even though I was frustrated and ready to give up on Fog yesterday, today I’m feeling much more optimistic and I’m still working on getting Fog up and running.
Previously I’ve been installing Fedora and Fog onto a physical machine and trying to run it over an isolated LAN using the built-in DHCP server just to see if I can get it up and running and play around with it to see if it’ll do everything I want it to do. Since that giving me trouble, I’ve gone ahead and spun up a Fedora VM and I’m going to try and integrate Fog into my existing Windows DHCP server. Maybe this different approach will yield better results. I’ll definitely make sure to come here to get help from the community if I run into any other issues moving forward.
@tom-elliott I have tried that, but still running into the same problem. I’ve tried continuing with the firewall disabled, but then of course I run into a new issue when capturing an image.
“Could not complete tasking (/bin/fog.upload)”
Which looks to typically be a problem if you mess with the fog user’s password, which I had not. Either way I checked all areas where that fog user and pass live and made sure the password was matching, but it’s still continuing.
I’m afraid that at this point I’ve spent way too much time trying to even get Fog to work at all that I’m going to need to look for another imaging solution. It seemed promising thought based on the reviews I’ve read, but I’ve been working on this for 3 weeks straight and I haven’t even gotten to the point where I can capture and deploy images.
@wayne-workman Thanks, Wayne. I have followed along with the Fedora 25 Server article you linked. I even did a fresh install this morning while following along to that exact article, but I’m still running into the exact same issue.
I’ve been going crazy trying to solve this problem.
I’m not a Linux guy so I’m making sure to follow all the directions on the wiki as close as possible as to not screw this all up.
I’m running Fog in Fedora 28.
I’ve gone through all the steps in https://wiki.fogproject.org/wiki/index.php/Tftp_timeout… and I’ve at least been able to narrow the problem down to firewalld.
I’m using a Windows 10 machine to test tftp
running tftp -i x.x.x.x get undionly.kpxe
and it works only when I disable firewalld on the Fog server.
I’ve configured it as per https://wiki.fogproject.org/wiki/index.php?title=FOG_security#FIREWALLD multiple times and even done a couple of complete Fedora and then Fog reinstalls and I still end up with the same issue.
Is there something that needs to be done differently specifically for Fedora 28?