Posts made by blindcat420

@Sebastian-Roth @Tom-Elliott @Wayne-Workman @george1421

I want to thank you guys for all the assistance.

@Sebastian-Roth

I went ahead and reran the fog installer.

That seems to have fixed it. I would have to say it most likely didnt finish last time. But since im a noob i dont really know what to look for. lol.

both legacy and uefi boot to pxe now.

@Sebastian-Roth

I will give that a try. I dont really remember. As far as I know the install should have completed. When I try to run this command from that tftp troubleshooting page. I get this.

Doesn’t look like i have a folder called tftpboot.

When you say rerun the installer are you talking about fog?

@Sebastian-Roth

@Tom-Elliott

I followed the guide to install tftp and this is what i get.

@Sebastian-Roth

So i started xinetd.

Iooks like i get the same error as before. so seems something is wrong with tftp

@Sebastian-Roth

@george1421

192.168.1.3 is the fog server.

for output.pcap i did run that from the fog server and it was before i disabled firewalld.

output2.pcap is after disabling firewalld.

this is what i get with those two commands.

@george1421

here is the updated pcap file.

0_1543078114945_output2.pcap

@Wayne-Workman said in Cant pxe boot to fog.:

sestatus

i disabled firewalld i assume that is different than selinux?

@george1421 @Wayne-Workman

So I got a update. Seems I’m getting more action after disabling the firewall on fog.

vm 1 with legacy boot gives me this now.

vm 2 with uefi boot gives me this.

the laptop gives me the same error as the first picture.

@george1421 @Wayne-Workman

Here is the output.pcap file.

output.pcap

@george1421

@Wayne-Workman

I installed tcpdump and have created the output.pcap file. I dont have much experience with linux hence why I’m messing with it.

How can I move that file to one of my windows file shares? So i can upload it here?

Answers to earlier questions.

I have a few vm’s 1 uses legacy, 1 uses uefi, i have a laptop that is currently set to legacy but i can change it to uefi.

I just installed dnsmasq the other day so it would be whatever the latest version is.

@Sebastian-Roth

Here is a picture. I have created a virtual switch with one of the network adapters. The switch is setup to provide external addresses. I dont know what happens during pxe. But I do know when vm’s boot into windows they obtain an 192.168.1.x ip address.

@Sebastian-Roth

So just to confirm. I have used brand new patch cables from the servers to the switch as well.

@Sebastian-Roth

I have a basic home router. It passes out c class ip addresses. 192.168.1.x

I just got a linksys lgs552p switch from a install I just did.

So from the wall I have the modem, linksys router e2000, cable from router to linksys switch. With the new switch I was able to get my test lab online.

I have two r710 servers that I got from one of my old jobs. I just got them setup really. So I installed server 2016 eval on both. I plan to make both of them hypervisors.

Right now one of the r710 servers has hyper v installed. I have fog running as a vm on that server. The fog ip is 192.168.1.3. I can browse to the portal and log in.

I cant boot to fog though from pxe. I have a gen1 vm created, a gen 2 vm created and a laptop that uses legacy boot. I could switch it to use uefi as well.

I had the laptop hooked up to the switch. Which is where the servers are hooked up as well. So as a test I hooked the laptop up to the router just to verify if the switch was maybe blocking anything. But I cant pxe boot from my router as well.

I updated the server last night and rebooted everything. I just tested all 3 machines and still have the same issue.

I dont get any errors on the vms other than what has been posted. The only error I get is from the laptop which states no boot filename received.

So seems there is a issue with dnsmasq not passing the bootfile name.

Hope that helps clear up my setup.

@george1421

They are on the same subnet.

When I try to pxe boot from a gen 1 vm it fails and gives me boot failure. reboot and select a proper boot device…
When I try to pxe boot from a gen 2 vm it fails and doesnt boot into fog and continues booting to windows 10. - dont see a error.
When I try to pxe boot from a laptop with legacy booting it fails and gives me pxe-e53 no boot filename received.

On all 3 machines secure boot is disabled.

I have a basic home router. I would rather have dhcp from my router instead of my test lab. I havent got as far as creating a server to perform dhcp instead of my router. since its a test lab it may not stay on all the time. its loud and in my room lol. I wanted to see if i could get this working because a guy at my work did. mainly for practice. I do plan to create other things and figured having fog setup to deploy some images would help speed up the process. I have created some syspreped images but have been testing with live vms and my laptop to verify it works before i boot up the images i created.

@george1421

the picture posted earlier was before i removed the <> from the ip address.

i just ran those commands again and got this

so i do get the udp line.

i still cant connect to fog though from any of the machines.

@george1421

this is what i get when i type those commands.

i changed all the <192.168.1.3> to 192.168.1.3 in the config but im still not able to boot to fog.

So I created a fog server the other day on my test lab following the guide located here.
https://wiki.fogproject.org/wiki/index.php?title=CentOS_7

Fog is up and running and I can navigate to the fog web portal.

I also setup ProxyDHCP with dnsmasq following this guide.
https://wiki.fogproject.org/wiki/index.php?title=ProxyDHCP_with_dnsmasq

I assume this guide was setup for both legacy and uefi booting - i could be wrong.

When I try to pxe boot from a gen 1 vm it fails and gives me boot failure. reboot and select a proper boot device…
When I try to pxe boot from a gen 2 vm it fails and doesnt boot into fog and continues booting to windows 10. - dont see a error.
When I try to pxe boot from a laptop with legacy booting it fails and gives me pxe-e53 no boot filename received.

On all 3 machines secure boot is disabled.

I have to assume dnsmasq isnt passing the file. Is there something i’m missing maybe?

The config file is pretty much the same as in step 4 on the article.

#Don't function as a DNS server:
port=0

# Log lots of extra information about DHCP transactions.
log-dhcp

# Set the root directory for files available via FTP.
tftp-root=/tftpboot

# The boot filename, Server name, Server Ip Address
dhcp-boot=undionly.kpxe,,<192.168.1.3>

# Disable re-use of the DHCP servername and filename fields as extra
# option space. That's to avoid confusing some old or broken DHCP clients.
dhcp-no-override

# inspect the vendor class string and match the text to set the tag
dhcp-vendorclass=BIOS,PXEClient:Arch:00000
dhcp-vendorclass=UEFI32,PXEClient:Arch:00006
dhcp-vendorclass=UEFI,PXEClient:Arch:00007
dhcp-vendorclass=UEFI64,PXEClient:Arch:00009

# Set the boot file name based on the matching tag from the vendor class (above)
dhcp-boot=net:UEFI32,i386-efi/ipxe.efi,,<192.168.1.3>
dhcp-boot=net:UEFI,ipxe.efi,,<192.168.1.3>
dhcp-boot=net:UEFI64,ipxe.efi,,<192.168.1.3>

# PXE menu.  The first part is the text displayed to the user.  The second is the timeout, in seconds.
pxe-prompt="Booting FOG Client", 1

# The known types are x86PC, PC98, IA64_EFI, Alpha, Arc_x86,
# Intel_Lean_Client, IA32_EFI, BC_EFI, Xscale_EFI and X86-64_EFI
# This option is first and will be the default if there is no input from the user.
pxe-service=X86PC, "Boot to FOG", undionly.kpxe
pxe-service=X86-64_EFI, "Boot to FOG UEFI", ipxe.efi
pxe-service=BC_EFI, "Boot to FOG UEFI PXE-BC", ipxe.efi

dhcp-range=<192.168.1.3>,proxy

Is there something I may be missing? Any help is appreciated.