/default.ipxe... Connection timed out | fog_1.0.1 | Ubuntu 14.04 LTS | Winxp32 Vbox Client
-
Yes, but I think the system is confused. So it’s trying to use the tftp settings from the 0.27 in which default.ipxe does not exist. Also, it won’t impact the operation of the 0.27 because it knows nothing of the default.ipxe nor cares about it.
-
Why it is trying to use the tftp setting from 0.27
I think I was not clear.I have downloaded a vm 0.27
this one is working fine with the built in dhcpsecond virtal machine: ubuntu 14+fog 1.0.1 +proxy dhcp with the settings from the fog wiki
I did not set anything on the tftp, I’ve just modified the proxydhcp…
And there is default.ipxe in the tftpboot folder -
Alright, lets go to basics.
Try commenting out the port=0 line in your ltsp.conf file:
[code]#port=0[/code] and restart the service, any luck? -
I think that was a step back, I attached the result [ATTACH]816[/ATTACH]
[url=“/_imported_xf_attachments/0/816_005.png?:”]005.png[/url]
-
If I install a fog with the built in dhcp, how can i disable the dhcp after the installation?
-
service dhcpd disable?
-
Thank you
I will start again, but now, with fog 0.32 with built in dhcp, if it is working, I will disable it, and install the proxydhcp… and I come back tomorrow
Thank you for your patience
Krisz
-
I’ve got an error message:
setting up and starting vsftp server … failed!
what does it mean? -
it means it failed to start and setup the vsftp server.
I don’t know why, but that’s what it means.
-
when you ran the installer, did you run:
[code]sudo ./installfog.sh[/code]
or did you run:
[code]./installfog.sh[/code] as a normal user? -
[CODE]sudo ./installfog.sh[/CODE]
-
Good morning
I am here again
So I re installed everything again, ubuntu 13.10 fog 1.0.1
First with dhcp: it was working
Second step: I removed the isc-dhcp-server: it was not booting at all
third step : I installed the dnsmasq, and I configed as it was on the fog wiki : it start booting, but connection time out again at the default.ipxeso it has to be the dnsmasq
-
I followed this [URL=“http://fogproject.org/forum/threads/dnsmasq-help-for-ipxe-stuff.10222/#post-24442”]DNSMasq Help for iPXE stuff[/URL]
but now, it can’t find the boot.php
[url]http://192.168.1.17/fog/service/ipxe/boot.php[/url] -
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”.
