/default.ipxe... Connection timed out | fog_1.0.1 | Ubuntu 14.04 LTS | Winxp32 Vbox Client

[Krisztian Buscsei]

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

[Krisztian Buscsei]

I’ve got an error message:
setting up and starting vsftp server … failed!
what does it mean?

[Tom Elliott]

it means it failed to start and setup the vsftp server.

I don’t know why, but that’s what it means.

[Tom Elliott]

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?

[Krisztian Buscsei]

[CODE]sudo ./installfog.sh[/CODE]

[Krisztian Buscsei]

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.ipxe

so it has to be the dnsmasq

[Krisztian Buscsei]

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]

[Tom Elliott]

The ProxyDHCP that’s handed out is within the same subnet that your FOG Server is attached to?

[Krisztian Buscsei]

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.0

But 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]

[Krisztian Buscsei]

I’ve just forgot this:
pxelinux.cfg\default

DEFAULT 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

[Paul Muti]

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]

[PaganLinuxGeek]

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.

[Wayne Workman]

[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:

[url]http://fogproject.org/wiki/index.php/FOG_(r2922)_Configuration_on_Fedora_21_Workstation_inside_Windows_Server_2012_Hyper-V_using_ProxyDHCP[/url]

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.

[PaganLinuxGeek]

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 tftpserver

It 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”.

[Wayne Workman]

[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 tftpserver

It 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.

[PaganLinuxGeek]

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.

[Wayne Workman]

[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.

[PaganLinuxGeek]

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?

[Wayne Workman]

[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]and

pxe-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.0

the undionly file comes from /tftpboot[/COLOR][/FONT]

[Wayne Workman]

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.