No such file or directory (http: //ipxe.org/2d03e13b)



  • Hello, I’m very new to using FOG. I am trying to image computers using FOG but am running into an issue. I’ve set up a virtualbox with FOG 1.5.8 and Pfsense 2.5.0 but when I go to capture the Windows 10 image it’s unable to capture and is saying “No such file or directory (http://ipxe.org/2d03e13b)”.

    The FOG server, Pfsense server and Windows 10 image are all on a Bridge Network Adapter. I did as much research as I can on this issue before I made this post so any help would be appreciated. Thank you!

    I created the FOG server and Windows 10 image using these two guides:
    https://www.ceos3c.com/open-source/install-fog-server-ubuntu-server-16-04-lts-ultimate-guide-virtualbox/
    https://www.ceos3c.com/sysadmin/create-generalized-windows-10-image-deploy-fog-server/

    Untitled picture4.png
    Untitled picture.png Untitled picture2.png
    FOG server
    Untitled picture3.png
    TFTP server is running
    Untitled picture5.png


  • Moderator

    @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.


  • Developer

    @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.



  • @george1421

    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!


  • Moderator

    @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.9

    10.0.0.8 is defining a default route of 10.0.0.1
    10.0.0.9 isn’t assigning a default route

    10.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 name

    We 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?


  • Moderator

    @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.


  • Developer

    @anon01013 Your pfSense (interface em0) and FOG server (intreface eth0) do have the same IP address 10.11.12.12, why?!?!



  • @Sebastian-Roth This is what I have in the VirtualBox

    Fog server:
    cfba65cd-bffd-440d-8421-5472b379130e-image.png

    0ff4158d-f41f-4e23-8239-0ea1319b74a7-image.png

    PfSense:
    65c8d6e2-3078-42be-acc4-fdd30495767a-image.png
    9d4b66d4-0e83-4dab-a832-3bc4e51ddf31-image.png

    Windows 10 image:
    1ae514db-0750-49a7-9121-55bffeb96d88-image.png


  • Developer

    @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?


  • Developer

    @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 name which is very important for PXE booting. Bother servers seem to point to different TFTP servers (next server).



  • @george1421

    Sorry, I’m still new to this but here’s the output pcap file.

    Thanks!

    output.pcap


  • Developer

    @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.


  • Moderator

    @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.


  • Moderator

    @anon01013 Sorry I didn’t see this til now for some reason. Let me have a look.



  • Hello,

    I followed the process in the link and this is what I got, hopefully I did it right…

    Thanks for the assistance!

    Wireshark_Win10.pcap

    adda6ec1-573f-40cb-98e7-a748667ef1a0-image.png


  • Moderator

    There are a couple of things here.

    1. By default pfsense sets up the dhcp server on the LAN interface and not the WAN.
    2. Also in the network booting section on pfsense you will need to setup the uefi boot file of ipxe.efi if you want to pxe boot uefi based computers.

    The error in the bios boot screen is a bit telling. Run through the following tutorial and capture a pcap of the pxe booting process. If you want to look at the pcap your self, transfer the pcap from the fog server to a computer with wireshark installed. Look at the second packet the one that has DHCP DISCOVER. In the ethernet header it will list the boot server and boot file name. My bet one of those are wrong. If you don’t know how to read wireshark post the pcap here and I’ll look at it for you. https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue


Log in to reply
 

317
Online

7.0k
Users

14.2k
Topics

134.2k
Posts