/default.ipxe... Connection timed out | fog_1.0.1 | Ubuntu 14.04 LTS | Winxp32 Vbox Client
-
The ProxyDHCP that’s handed out is within the same subnet that your FOG Server is attached to?
-
Hi
It look like, I found a solution.
so.
ubuntu 13.10
fog 1.0.1
Installed with the built in dhcp server
After I disabled…
After Install the dnsmasq
Configured as the fog wiki wrote it.
and I am not sure(I did to many things) but probably these two lane:
enable-tftp
dhcp-range=192.168.1.0,proxy,255.255.255.0But anyway I attach the complete configuration file
Thank you for your help
Krisz
[url=“/_imported_xf_attachments/0/826_ltsp.conf-working.txt?:”]ltsp.conf-working.txt[/url]
-
I’ve just forgot this:
pxelinux.cfg\defaultDEFAULT vesamenu.c32
Label fog
MENU DEFAULT
kernel ipxe.krn dhcp && chain [url]http://192.168.1.26/fog/service/ipxe/boot.php:mac=${net0/mac}[/url]
PROMPT 0
TIMEOUT 01 -
I started a fog server build for a client and this time around i got stuck again on the default.ipxe timeout.
I was able to tftp the default.ipxe file from windows and so i restarted the tftpd-hpa daemon, rebooted my laptop, and it started imaging.
I added this to my notes for next time (grabbed from somewhere else online)
[FONT=Calibri] [FONT=Microsoft JhengHei UI][COLOR=#7f7f7f][SIZE=3]tftpd-hpa starts “to early”. You can fix this by editing the /etc/rc.local and add the line[/SIZE][/COLOR][/FONT][/FONT]
[COLOR=#7f7f7f][FONT=Microsoft JhengHei UI][SIZE=3]/bin/sleep 30 && /etc/init.d/tftpd-hpa restart[/SIZE][/FONT][/COLOR]
-
I too am having this issue on fedora 21 system. I can transfer the file via tftp from command line without error. However, when attempting to network boot ipxe as per the new method it reports a /default.ipxe… timeout error. This happen in virtualbox vm (network adapter is set to bridged and intel chipset emulation) and with my HP Pavilion laptop. I can boot the old method (pxe) as per fog 0.32. I’ve edited my /etc/dnsmasq.conf file to provide two network boot options in the boot menu (press f8 for boot menu) with the default being ipxe boot. Since I can netboot using the older method and transfer files via tftp I tend to think the setup for DHCP and tftp is functioning normally.
I’ve checked the messages log file for errors and it’s not reporting any. The httpd access log doesn’t show any requests for the files it’s supposed to transfer via http either. It leads me to believe that it’s not progressing past the tftp transfer stage and into the http transfer stage.
-
[quote=“PaganLinuxGeek, post: 42472, member: 2226”]I too am having this issue on fedora 21 system. I can transfer the file via tftp from command line without error. However, when attempting to network boot ipxe as per the new method it reports a /default.ipxe… timeout error. This happen in virtualbox vm (network adapter is set to bridged and intel chipset emulation) and with my HP Pavilion laptop. I can boot the old method (pxe) as per fog 0.32. I’ve edited my /etc/dnsmasq.conf file to provide two network boot options in the boot menu (press f8 for boot menu) with the default being ipxe boot. Since I can netboot using the older method and transfer files via tftp I tend to think the setup for DHCP and tftp is functioning normally.
I’ve checked the messages log file for errors and it’s not reporting any. The httpd access log doesn’t show any requests for the files it’s supposed to transfer via http either. It leads me to believe that it’s not progressing past the tftp transfer stage and into the http transfer stage.[/quote]
I’m using Fedora 21 also. I wrote up some instructions for installing in Hyper-V (might very closely apply to VMware). These apply to revision 2922 and up.
The instructions are here:
At the bottom, you’ll find troubleshooting help (just a starting place, really).
I think you might find it to be a lot of help.
-
I’ve read this through already actually, thank you. I would suggest adding this little bit to your howto however.
Make sure you are storing dnsmasq configuration into /etc/dnsmasq.conf and NOT /etc/dnsmasq.d/ltsp.conf location.
In desperation a few days ago I moved /etc/dnsmasq.d/ltsp.conf to /etc/dnsmasq.conf and found some success. Seems that contrary to documenatation it does NOT parse the ltsp.conf file…for others reading this:
selinux has been set to “permissive” and also tried with “disabled” same results
systemctl disable firewalld.service has been executed
I’ve tried this using the xinetd tftp-server and using dnsmasq’s built in tftpserverIt shouldn’t matter but I DO have 3 nics in this machine (2 built into mobo, and 1 add-on)… all are enabled and functional on same subnet but with using seperate IP’s, none are in bridged mode, or “teaming”.
-
[quote=“PaganLinuxGeek, post: 42480, member: 2226”]I’ve read this through already actually, thank you. I would suggest adding this little bit to your howto however.
Make sure you are storing dnsmasq configuration into /etc/dnsmasq.conf and NOT /etc/dnsmasq.d/ltsp.conf location.
In desperation a few days ago I moved /etc/dnsmasq.d/ltsp.conf to /etc/dnsmasq.conf and found some success. Seems that contrary to documenatation it does NOT parse the ltsp.conf file…for others reading this:
selinux has been set to “permissive” and also tried with “disabled” same results
systemctl disable firewalld.service has been executed
I’ve tried this using the xinetd tftp-server and using dnsmasq’s built in tftpserverIt shouldn’t matter but I DO have 3 nics in this machine (2 built into mobo, and 1 add-on)… all are enabled and functional on same subnet but with using seperate IP’s, none are in bridged mode, or “teaming”.[/quote]
Glad you liked the howto. I am not sure why the /etc/dnsmasq.d/ltsp.conf didn’t work for you, as that’s what I did on my setup. You are using a newer revision than me so, maybe [URL=‘http://fogproject.org/forum/members/tom-elliott.7271/’][SIZE=11px][U][COLOR=#969696]Tom Elliott[/COLOR][/U][/SIZE][/URL] changed something… not sure. If he confirms, I’ll put notes in the How-To for the newer revision’s config on that part.
By reading through your problem, I was thinking it was a simple password issue, perhaps for the TFTP settings. Maybe the storage management password settings.
I’d recommend disabling SELinux - just to eliminate it from the equation - at least till things are working. Reboot after the change for it to take effect.
Did you run all the systemctl status commands to see if they were all ok?
Also, lately, I’ve read a lot of stuff about how people need to set up “Bridged connections” for the OS that hosts the virtualized FOG box.
-
I HAVE disabled selinux in /etc/selinux/config no change
all the passwords are the default. I’ve made no changes
Yes, all disabled services are not running, all required services are running.
TO repeat: I CAN retrieve the files using tftp on the commandline so I know tftp is working. I can netboot using the older pxe boot menus so I know that dhcp is configured correctly. This is on my home lan right now until I get the bugs worked out then I will install at work. The vbox machine and my laptop will find the dhcp server and start network boot until it gets to the /default.ixpe… stage then it’s timeout errors. -
[quote=“PaganLinuxGeek, post: 42484, member: 2226”]I HAVE disabled selinux in /etc/selinux/config no change
all the passwords are the default. I’ve made no changes
Yes, all disabled services are not running, all required services are running.
TO repeat: I CAN retrieve the files using tftp on the commandline so I know tftp is working. I can netboot using the older pxe boot menus so I know that dhcp is configured correctly. This is on my home lan right now until I get the bugs worked out then I will install at work. The vbox machine and my laptop will find the dhcp server and start network boot until it gets to the /default.ixpe… stage then it’s timeout errors.[/quote]Just trying to cover the simple stuff. I overlook little things sometimes.
You said you were running the v-machine on your laptop using 3 adapters? One is an add-on? an HP Pavilion laptop.
Is the system you’re trying to network boot with virtualized, or is it that HP Pavilion itself? Have you tried disabling the add-on interface?
Have you looked in the CMOS settings for the HP Pavilion (if that’s what you’re attempting to netboot), there are various settings on some systems for how a system attempts to net-boot. In a conversation with Tom (the senior developer), he was talking about how the current revision uses newer methods, so your CMOS settings might work with older iPXE but not the newer PXE methods… just a stab in the dark.
Because you can’t find any errors anywhere and all the services are properly configured, I’m reaching all over the place for ideas.
It’s probably something simple.
-
The machine running FOG has 3 nics and is hosting FOG in the HOST OS it is not in a vm.
I have VirtualBox 4.3 installed and am using it to test fog operation.
Thinking that the issue might actually be with vbox, I connected my pavillion g7 laptop via ethernet and attempted network boot.
The laptop was able to network boot using the older (pxe) method, but encountered the same error as vbox when attempting to boot using the newer (ipxe) method. I am able to do this because my dnsmasq.conf has entries that create a menu with default being ipxe boot (new method) Do you recall what particular bios settings the devel mentioned? -
[quote=“PaganLinuxGeek, post: 42489, member: 2226”]The machine running FOG has 3 nics and is hosting FOG in the HOST OS it is not in a vm.
I have VirtualBox 4.3 installed and am using it to test fog operation.
Thinking that the issue might actually be with vbox, I connected my pavillion g7 laptop via ethernet and attempted network boot.
The laptop was able to network boot using the older (pxe) method, but encountered the same error as vbox when attempting to boot using the newer (ipxe) method. I am able to do this because my dnsmasq.conf has entries that create a menu with default being ipxe boot (new method) Do you recall what particular bios settings the devel mentioned?[/quote]Copied this stuff from some IM history.
[FONT=arial][COLOR=#222222]kkpxe is safer for buggy bios’s and should work on all working models too[/COLOR][/FONT]
[FONT=arial][COLOR=#222222]so the dhcp-boot=undionly.kpxe[/COLOR][/FONT]
[FONT=arial][COLOR=#222222]andpxe-service=X86PC, “Boot form network”, undionly[/COLOR][/FONT]
[FONT=arial][COLOR=#222222] [/COLOR][/FONT]
[FONT=arial][COLOR=#222222]you’ll likely need a copy of whatever file to undionly.0[/COLOR][/FONT]
[FONT=arial][COLOR=#222222]so[/COLOR][/FONT]
[FONT=arial][COLOR=#222222]cp undionly.kkpxe undionly.0the undionly file comes from /tftpboot[/COLOR][/FONT]
-
Have you tried a standard [I][SIZE=12px]dnsmasq.conf [/SIZE][/I]configuration ?
Maybe there is a typo in there? You were saying you customized it to allow use of the older method.
This is what mine looks like:
[CODE]port=0
log-dhcp
tftp-root=/tftpboot
dhcp-boot=undionly.kpxe
dhcp-option=17,/images
dhcp-option=vendor:PXEClient,6,2b
dhcp-no-override
pxe-prompt=“Press F8 for boot menu”, 3
pxe-service=X86PC, “Boot from network” undionly
pxe-service=X86PC, “Boot from local hard disk”, 0
dhcp-range=x.x.x.x,proxy[/CODE]and that’s actually located here:/etc/dnsmasq.d/ltsp.conf
You said it works in the dnsmasq.conf file though. -
I tried the undionly.kkpxe file to the same results…
I HAVE tried the standard FOG 1.2.0 configuration for dnsmasq as well as the older style (fog 0.32)
The dnsmasq.conf shown below has a menu that alllows me to choose which
My gut feeling is that something is preventing the connection to tftp when the client computer loads undionly, and follows the scripted instructions… However since I dont have the beta versions or the source I am at a loss to see what the potential causes are…my machine has three NICS:
eno1 = 192.168.1.116
enp4s0 = 192.168.1.115
enp7s0 = 192.168.1.107-----my current /etc/dnsmasq.conf file…-----
tftp-root=/tftpboot
#enable-tftp
#dhcp-boot=pxelinux.0
dhcp-option=vendor:PXEClient,6,2b
dhcp-no-override
#pxe-prompt=“Press F8 for boot menu…”, 3
#pxe-service=X86PC, “Boot from network”, pxelinux
#pxe-service=X86PC, “Boot from local hard disk”, 0
dhcp-range=192.168.1.116,proxy#port=0
log-dhcp
dhcp-boot=undionly.kpxe,192.168.1.116
dhcp-option=17,/images
dhcp-option=pxe,66,192.168.1.116
pxe-prompt=“Press F8 for boot menu”, 15
pxe-service=X86PC,“iPXE Boot (Newer for Secure Boots)”, undionly
pxe-service=X86PC,“PXE Boot (Older machines)”, pxelinux
pxe-service=X86PC,“Boot from local hard disk”, 0
interface=eno1,enp7s0,enp4s0,loI have verified that the httpd, xinetd, and dnsmasq services are started, and firewalld is NOT.
-
Bump.
-
Still working on it, with no success.
-
[quote=“PaganLinuxGeek, post: 42573, member: 2226”]Still working on it, with no success.[/quote]
So, out of curiosity (and some valid reason to bump this thread), I checked the Wiki’s Working device & Problematic Device list. The pavillion g7 is not listed in either.
-
Well I wouldn’t want to list it as NOT WORKING until I can test it on a known functional FOG setup…
Anyone have one running in the panhandle of Florida? -
Where I’m more confused, is this still based on 1.0.1? If so, can you, at the least, try more updated ipxe files?
-
It is the latest stable release 1.2.0 running on Fedora Workstation 21 it was NOT an upgrade but a new installation as I had recently formatted and installed fedora 21.
I am using dnsmasq to proxy the dhcp options needed to network boot clients.
I HAVE check httpd logs and the clients do NOT progress to the point of requesting files via http
I did have logging enabled on dnsmasq to verify proper operation but have since disabled it again.
This setup is running on the HOST OS and NOT in a vm. I have been attempting to use a vbox vm to test this as well as my personal laptop a pavillion g7
Please let me know what other information you need and I will endeavor to provide it. I can ssh into this machine running at home and manipulate a virtualbox vm via x over ssh.
