@george1421
thats the server options within the scope for this particular hall im in.
Posts made by tesparza
-
RE: UEFI PXE boot
-
RE: UEFI PXE boot
@george1421 [mod note: linked removed because it contained sensitive data - geo]
-
RE: UEFI PXE boot
@george1421 said in UEFI PXE boot:
systemctl stop firewalld
https://drive.google.com/open?id=14zDpA9fW6P6qE4Xs6J5Cpgvw4ZClQUd6link to the capture
-
RE: UEFI PXE boot
@george1421 it’s enabled, but has the exception specified in the wiki guided
-
RE: UEFI PXE boot
@george1421 okay I will post tomorrow, I not at work right now. Was trying to post but tcpdump wasn’t allowing me, something about being root preventing me from capturing.
-
RE: UEFI PXE boot
@george1421 what do you think I’m doing wrong. I’m putting the PXEClient:Arch:00007 exactly because the binary matches the wiki pics. I know it has something to do with my DHCP server. Just don’t know what else to check
-
RE: UEFI PXE boot
@george1421 No DHCP server is on the same subnet, it is local in that campus. The problem is it always just looks for undionly.kpxe it never attemps to boot from ipxe.efi even though i put the correct vendor and add the policy option 66 and 67
-
RE: UEFI PXE boot
@Sebastian-Roth I’m a school campus, part of a school district. Each school has its own DHCP server. But the computer in my campus can only get IP’s from my DHCP because the IDF in my campus has the IP helper to route to my DHCP server.
-
RE: UEFI PXE boot
@george1421 [root@localhost admin]# tcpdump -i enp5s0 port 67 or port 68 or port 69 or port 4011
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on enp5s0, link-type EN10MB (Ethernet), capture size 262144 bytes
17:21:59.974458 IP 10.154.18.65.ibm-abtact > localhost.localdomain.tftp: 43 RRQ “undionly.kpxe” octet tsize 0 blksize 1468
17:21:59.977786 IP 10.154.18.65.pra_elmd > localhost.localdomain.tftp: 35 RRQ “undionly.kpxe” octet blksize 1468
^C
2 packets captured
2 packets received by filter
0 packets dropped by kernel
[root@localhost admin]# -
RE: UEFI PXE boot
@Sebastian-Roth
I followed the steps one by one. Binary is the exact same so I typed the Arch:00007 correctly. But still it uses the undionly.kpxe instead of the ipxe.efi
-
RE: UEFI PXE boot
@tesparza Quality is bad but it says
Station IP address is 10.154.19.42
Server IP address is 10.154.72.190 which is correct
MBP filename is undionly.kpxe
MBP filzesize is 97003 Bytes (I believe)
Downloading MBP file…
Then it just goes into Windows 10 -
RE: UEFI PXE boot
was able to slowmo and screen grab what it said. For some reason its looking for undionly.kpxe, but i have ipxe.efi setup.
-
RE: UEFI PXE boot
@Sebastian-Roth Okay, I’m running FOG 1.5.4 and I’m running it on CENTOS 7. I’ll capture the video see if any errors happen. Also I’ll try the packet capture. I’ll upload ASAP