@Quazz Thanks, i rebooted and was able to run the previous command.
Posts made by K.Hays
-
RE: UEFI-PXE-Boot (Asus t100 Tablet)
-
RE: UEFI-PXE-Boot (Asus t100 Tablet)
@george1421 said in UEFI-PXE-Boot (Asus t100 Tablet):
tcpdump -w output.pcap port 67 or port 68
When i run this command i get “tcpdump: no suitable device found”
Tcpdump is installed, and i can run it with just the tcpdump command, but this specific line is not working. -
RE: UEFI-PXE-Boot (Asus t100 Tablet)
@Junkhacker What exactly do you mean by that?
-
RE: UEFI-PXE-Boot (Asus t100 Tablet)
@Wayne-Workman Firmware update was ineffective.
-
RE: UEFI-PXE-Boot (Asus t100 Tablet)
@Wayne-Workman I am currently updating the firmware. If it is a network issue as you’re thinking, could it be caused by the fact that we’re running a Sever 2008 DHCP?
-
RE: UEFI-PXE-Boot (Asus t100 Tablet)
@Wayne-Workman I can attempt to update the firmware, but I feel like that probably isn’t the issue. We have an HP laptop that we put into UEFI mode to help us troubleshoot and it is doing the same thing as the tablets, and it’s not using a USB adapter.
-
RE: UEFI-PXE-Boot (Asus t100 Tablet)
@Wayne-Workman the two adapters do that, and the other one isn’t recognized as a boot option. It’s only capable of uefi also.
-
RE: UEFI-PXE-Boot (Asus t100 Tablet)
@Scott-Adams I just have to switch bootfiles on the dhcp correct? I dont have to do it anywhere else?
-
RE: UEFI-PXE-Boot (Asus t100 Tablet)
@Scott-Adams Didn’t work. Were also testing it with a Uefi laptop with a built in port and it’s also not working.
-
RE: UEFI-PXE-Boot (Asus t100 Tablet)
@K.Hays Secure boot is off, we are just about to test out the rest of what you stated Scott.
Wayne, all other computers work just fine to image. The main adapter we are using is
Asus 90-XB3900CA00040- USB 2.0 to Ethernet Adapter -
UEFI-PXE-Boot (Asus t100 Tablet)
Were trying to image 250 t100 tablets we have. We got three different network adapters as these tablets have no on board ethernet port. From what Ive read two of the three should work with it. When we boot to the network we get “Start pxe over ipv4” and then it just sits there. Not sure what to do at this point. Have read a lot of forum posts on this but haven’t gotten much luck. Is it even possible at this point. We have server 2008 for the dhcp, i read somewhere that we might need 2012. Other than that we have fog trunk, and have also changed option 67 to point towards ipxe.efi with no luck.
-
RE: Fog: multicasting across subnets
@Sebastian-Roth ill post this the next time I’m at a separate building so that i can run the test. Might be a little while.
@Wayne-Workman That’s awesome actually i didn’t know that. How many computers can fog do max in this way, do you think? -
RE: Fog: multicasting across subnets
@Wayne-Workman The problem is the amount of bandwidth that would take up. Unless unicast doesn’t take any more bandwidth than multicast would then that’s not an option. We would be multicasting up to 30+ computers at a time sometimes and I’m afraid unicasting would take down the network in those situations. and Sebastion i ran through that troubleshoot page already, but thank you.
-
RE: Fog: multicasting across subnets
For now we just decided to put a fog server in each building because summer is approaching quickly and we need a better alternative to ghost. Advice is still welcome if there is any to give at this point. Thanks for the help so far.
-
RE: Fog: multicasting across subnets
@Tom-Elliott Im using 14.04 on the nodes also. The interface names on both are eth2. One of the nodes defaulted to eth0 in the database and the other we manually changed to eth2. I believe we got the same results regardless.