No such file or directory (http: //ipxe.org/2d03e13b)
-
Hello,
I followed the process in the link and this is what I got, hopefully I did it right…
Thanks for the assistance!
-
@anon01013 Sorry I didn’t see this til now for some reason. Let me have a look.
-
@anon01013 The pcap doesn’t match what should have been captured. Its not possible to generate this pcap from the screen shot you provided.
Hint if you reply to my posts, the forum will ping me when you post.
-
@anon01013 Possibly the VirtualBox VM is set to UEFI but pfSense might not provide PXE boot information for UEFI clients?
Note for everyone: As far as I see in the picture this output we see here from iPXE is NOT the one delivered from the FOG server but the one build into VirtualBox.
-
-
@anon01013 In that PCAP file there is no packet from or to the host we see in the picture (08:00:27:36:0d:ac). What is the network setting for this VM?
In the PCAP we see two different DHCP servers answering and none of them does provide PXE boot information on the
file namewhich is very important for PXE booting. Bother servers seem to point to different TFTP servers (next server). -
@anon01013 said:
The FOG server, Pfsense server and Windows 10 image are all on a Bridge Network Adapter.
Re-reading your post I just noticed this part. You have pfSense installed in a VM as well but it has two NICs bound to it. What are the VM network settings for those who NICs as well as the VM network settings for the other two VMs?
-
-
@anon01013 Your pfSense (interface em0) and FOG server (intreface eth0) do have the same IP address 10.11.12.12, why?!?!
Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)
Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG
-
@Sebastian-Roth said in No such file or directory (http: //ipxe.org/2d03e13b):
@anon01013 Your pfSense (interface em0) and FOG server (intreface eth0) do have the same IP address 10.11.12.12, why?!?!
Good catch. I think we have way to many new things in play here TBH. PXE booting is more like a concert with everything needing to work together. I haven’t looked at the pcap at the moment, but I’m going to bet the 2 dhcp servers responding are/is one is pfsense and the second is the home soho router. If this is the case then we can turn of pfsense for now and just install dnsmasq on the fog server to supply the pxe boot info. Its a bit cleaner solution with less parts to go wrong.
-
@anon01013 Oh my, there is a lot of funny business going on with that pcap.
You have 2 dhcp server 10.0.0.8 and 10.0.0.9 with a subnet mask of 255.255.0.0 you also have a dhcp relay agent at 10.0.0.34 that goes somewhere
10.0.0.8 is giving the client an IP address of: 10.0.20.92
10.0.0.9 is giving the client an IP address of: 10.0.21.910.0.0.8 is defining a default route of 10.0.0.1
10.0.0.9 isn’t assigning a default route10.0.0.8 is providing itself as the bootp server but not providing a boot file name
10.0.0.9 is providing itself as the bootp server but not providing a boot file nameWe are seeing so many offers because the dhcp-relay service on 10.0.0.34 is reflecting the dhcp discovers back to both the 10.0.0.8 and 10.0.0.9 dhcp servers. These servers also might be windows AD servers too, I can’t tell because we did not capture that traffic by design.
So now with that said, your FOG server is on a totally different subnet than what your pcap says the dhcp servers are telling the clients to pxe boot to. The fog server is on 10.11.12.12 /24 and your main network (according to the dhcp servers are 10.0.0.0 /16) There is no way the clients issued an IP address from the 10.0.0.8 dhcp servers can reach the fog server unless they go through a router.
I know for someone just starting out I just threw up a bunch of crap you don’t understand and none of its related to FOG. That is because the problem isn’t your FOG server at the moment, its your existing network infrastructure.
You might want to explain what your goal is here so we can help you untwist this configuration.
The first step is… do you want to integrate FOG into your existing 10.0.0.0 /16 network? If so what are your dhcp servers 10.0.0.8 and 10.0.0.9?
-
I see, yeah that sounds like a mess and a lot of hair pulling but the goal is to push out a Windows 10 image to desktops. The business that I work at bought 200 desktops with no OS and they want me to create an imaging lab where I can image these desktops with a Windows 10 OS. Unfortunately, I’m the only technician with the business so I have to figure this out.
Where do I start on untwisting the network infrastructure? Thanks for all the help btw!
-
@anon01013 said in No such file or directory (http: //ipxe.org/2d03e13b):
Where do I start on untwisting the network infrastructure?
Well you might start by telling us more about the existing DHCP servers in your network.
-
@anon01013 Yes I agree, tell us what your dhcp servers are 10.0.0.8 and .9 . What is the manufacturer and version? Do you have access to change the configuration on these devices? Also please identify what is device 10.0.0.34.
Lets start with there, then we can chart the next steps.
BTW: your packet capture really tells us the story of what is going on with your network. Without the pcap it would be impossible to help you with FOG on your network.
