@george1421
OK another pcap AND the ltsp just in case.
Posts made by KnightRaven
-
RE: Configuring dnsmasq with UEFI for PXE.
-
RE: Configuring dnsmasq with UEFI for PXE.
@george1421
here is the ltsp again…
0_1481911611868_ltsp.conf -
RE: Configuring dnsmasq with UEFI for PXE.
@george1421
Our true DHCP server is not on same subnet(it’s located in a whole other building). However my Fog server that also runs dnsmasq as proxy and the test laptop is on the same local switch.
Here is the output…
0_1481909299445_output.pcap -
RE: Configuring dnsmasq with UEFI for PXE.
@george1421
OK, so far it boots legacy and boots UEFI in DHCP(non proxy) mode only. When I leave dnsmasq in proxy mode PXE does not receive anything(no menu) and will just time out to pressing F* key options to reboot.I tried doing a tcpdump. But not sure what to look for myself. I did see where it was trying to offer the ipxe.efi file. Perhaps you have a way to narrow the results?
-
RE: Configuring dnsmasq with UEFI for PXE.
@Tom-Elliott
Alrighty, a new day, another dollar, and fresh eyes.
Yes I have been restarting dnsmasq. Didn’t realize it would use any ltsp file(maybe any file?) in that folder. And so was getting combined info/options. Still wasn’t working for UEFI in proxy mode when I left.
At another location that I will try working on and see what happens now that I know not to leave copies in the dnsmasq.d folder. -
RE: Configuring dnsmasq with UEFI for PXE.
@george1421
Well So far it’s not working. I’m sure I’m missing something but its getting too late. I might can try again tomorrow.I even tried making a new ltsp.conf file with just your info.
Actually its still picking up the old… I have restarted dnsmasq several times. Legacy is still booting with the old prompt text. Actually appears to be combining somehow. Ugh.
that’s weird. I’ll have to look tomorrow.
Thanks for your time. Y’all are always a big help.
Jason Bradley
-
RE: Configuring dnsmasq with UEFI for PXE.
@george1421
Awesome, looks like I needed to finish adding vendor info as well as add boot info.Will give that a shot before I get out.
-
Configuring dnsmasq with UEFI for PXE.
Configuring dnsmasq with UEFI for PXE.
Using dnsmasq 2.76 and Fog rc 36.
What else needs to be done to ltsp.conf?
Thanks!
Jason -
RE: Dnsmasq bios and uefi
@KnightRaven
ltsp.conf file…
0_1481838650169_ltsp.confI’m about to be out for the day so I may not get a chance to test for a few weeks. The file may also be a bit ugly but i tried to leave as much of the original info in and just updated info as needed.
-
RE: Dnsmasq bios and uefi
@george1421
~ $ dnsmasq -v
Dnsmasq version 2.76 Copyright 2000-2016 Simon Kelley
Compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth no-DNSSEC loop-detect inotifyThis software comes with ABSOLUTELY NO WARRANTY.
Dnsmasq is free software, and you are welcome to redistribute it
under the terms of the GNU General Public License, version 2 or 3. -
RE: Dnsmasq bios and uefi
Hi,
I was just wondering if you actually got this to work in proxy mode? I have tried and can seem to get it to UEFI boot in proxy. I tried setting dnsmasq to serve as DHCP for a moment(and unplugged from rest of network) with just my test client and Fog/PXE and that worked. Was able to get to Fog menu.Using dnsmasq 2.76 and just pulled latest fog rc36.
Do I need to compile something differently that I’m not seeing(it’s posible I missed something)? Or does it just not work in proxymode at this time?
thanks,
Jason -
RE: Where are the logs!?!?!
@Arsenal101
You may have to add it to the <settings pass=“oobeSystem”>. At least I found my old script and had it there. the <autologon> section was just under where your <timezone> section is. -
RE: Computer Won't Image
I’m not a fog expert but from my experiences…
Does it get to the actual image screens?
I’m wondering if you may have used a fixed size image type and the HDD may be smaller than the others.Or being Win 8.1 system could there be a change in the BIOS/UEFI settings casing a quirk?
Just my quick thoughts without knowing more.
-
RE: Where are the logs!?!?!
Just thought I’d add my $0.02 worth. I may not be a pro at answer files but can relay my experiances. First I hate them. But are a neccesary evil at times it seems. I hate that MS essentialy bricks your image for seemingly minor errors or such. With tjhat said…
My experiances have been that it usually is a service. Usually an Antivirus that isnt turned off or uninstalled properly. In our case it has been when I forget to remove Avast.
Also have issues on occasion with CopyProfile. It seems to get confused easy. If you have used another account(a generic perhaps) to setup general settings it may be getting hung on which account to use as the default profile.
I havent tried to use the Drive setup so I don’t know if there is anything there causing an issue.I would agree that the CPI location is not the issue. In my file it usually points or did to a jump/USB drive location that doesn’t exist during imaging.
-
RE: image capture ipxe error input/output 1d0c6139
@Tom-Elliott
OK.
Well, I think I figured it out. I may have missed updating the storage node info. The graphs/pie charts are back working now.Setup capture and is working. Ugh. the one thing I didn’t double check after it all. Being that its the only storage node I didn’t think to check it again.
Thanks for all of y’alls time. sometimes it just needs more eyes and a better understanding of how this works. Y’all have a great day. I need a beverage.
thanks,
Jason -
RE: image capture ipxe error input/output 1d0c6139
@Wayne-Workman
Yes, exactly. I think I checked the settings in fog first. I went to the fog settings -> web and tftp settings in the webgui and changed it there first. But I did change the .fogsettings file and then re-ran the installer.The last couple of updates it didn’t prompt for a schema update when opening the webgui after installing update. Just went straight to login. Not sure if that matters. or is as designed in the RCs.
-
RE: image capture ipxe error input/output 1d0c6139
@KnightRaven @Tom-Elliott @Wayne-Workman
it looks like it may be a multicast issue, if Fog defaults that way. Just heard that the multicast settings haven’t been pushed with the new subnets. Or so I’m told -
RE: image capture ipxe error input/output 1d0c6139
@Tom-Elliott No. They are in the same room and same subnet.
-
RE: image capture ipxe error input/output 1d0c6139
@KnightRaven
Would the imaging be defaulting to using multicast? I’ve heard some other techs report problems with multicasting using Ghost. But unicast seemed to work ok.Ghost has been our standard but it’s an older version. Been trying to setup fog for myself and test it to give an alternative. Been going good til this subnet change. If I can’t get help from our networking side for it to talk across the subnets it may be a bust.