PXE issues?

Phantox Jada

Well, if it’s not dhcp, then what could it be?

[QUOTE]You could always try DNSMasq to proxy serve your bootfile and server, sometimes this can alleviate issues with finding the correct files.[/QUOTE]

I can give this a try later today.

Junkhacker

since you’re hosting the server in vmware player, i have to wonder if there’s delays that are giving timeouts or something similar

Phantox Jada

I did not think about that. Should I try virtualbox or something else?

Just out of curiosity, I have Fog server configured with “Bridged: Connected directly to the physical network” with “Replicate physical network connection state” checked. I currently have Fog with a separate IP address as the physical machine. Should they have the same IP or should it be separated like I have them.

Junkhacker

i’m not familiar with vmware player, so i’m afraid that i can’t tell you what setting to use. i’m sure someone could tell you how to get this to work perfectly, but not me. if you’re just trying to get this working for testing/evaluation purposes. an old desktop would might work better for you.

Phantox Jada

A new update: I tried the same thing with a laptop and have the same issue.

As an experiment, I tried to chain load the virtual Ubuntu 13.10 with fog 1.2. The reasoning is because the old pxelinux.0 worked on the old test vm, but not the undionly.kpxe on fog 1.2. As a result, I can get it to boot the fog menu every couple of times, but not consistently. I am attaching a picture to show what it does. If it does boot to fog, it will configure real fast and boot. Otherwise, it does like the picture shows and goes to “press a key to reboot” after a few seconds.

[url]http://postimg.org/image/578ihklj1/[/url]

Junkhacker

what models of clients have you tried pxe booting?

Phantox Jada

We have 3 different clients. The HP Pavilion a1610n, HP Pavilion P6-2011, and Lenovo Ideacentre K33B.

Junkhacker

try using undionly.kkpxe

Phantox Jada

[url=http://postimg.org/image/8b02epwkt/][img]http://s30.postimg.org/8b02epwkt/20140725_113435.jpg[/img][/url]

I get an error. 3c092003

Sivasubramaniam.T

I am also facing the same issue. Please help. (Fog : 1.2.0 in Ubuntu 12.04)

need2

Have you… updated your kernels?

Phantox Jada

Wouldn’t the kernels be up to date with the newest fog (1.2)? Or is that something that has to be done manually?

Phantox Jada

[QUOTE]You could always try DNSMasq to proxy serve your bootfile and server, sometimes this can alleviate issues with finding the correct files.

[URL=‘http://fogproject.org/wiki/index.php/Using_FOG_with_an_unmodifiable_DHCP_server/_Using_FOG_with_no_DHCP_server#DNSMASQ_settings_for_iPXE’]http://fogproject.org/wiki/index.ph...with_no_DHCP_server#DNSMASQ_settings_for_iPXE[/URL][/QUOTE]

This did it!!! Finally, thank you so much. :):D Now that it boots Fog every time, I can learn how to actually use it instead of installing it. Thank you so much.

Sivasubramaniam.T

Hi Phantox,

Can you please guide me to fix this issue. I have same issue. I have Fog 1.2.0 running in Ubuntu 12.04. I am using Windows Server for DHCP service.

Thanks in advance.

Phantox Jada

I really just followed this guide to setting up DNSMasq.

[URL=‘http://fogproject.org/wiki/index.php/Using_FOG_with_an_unmodifiable_DHCP_server/_Using_FOG_with_no_DHCP_server#DNSMASQ_settings_for_iPXE’][I][SIZE=12px]http://fogproject.org/wiki/index.ph...with_no_DHCP_server#DNSMASQ_settings_for_iPXE[/SIZE][/I][/URL]

I didn’t do step 7 or 8 on the guide. Instead, I jumped down to the section “DNSMASQ settings for IPXE” and continued from there.

To be able to edit and create files, I used “sudo gksu nautilus.” I used gedit (text editor) to create the ltsp.conf file and saved it to my desktop. Then using “sudo gksu nautilus” in terminal allowed me to move the ltsp.conf from my Desktop to /etc/dnsmasq.d/ltsp.conf. Make sure to edit ltsp.conf for your setup. For example:

The boot filename, Server name, Server Ip Address

dhcp-boot=undionly.kpxe,[B]x.x.x.x[/B]

Change the [B]x.x.x.x[/B] to your fog server IP address.

I also changed the IP address in this section to point to my fog server.

This range(s) is for the public interface, where dnsmasq functions

as a proxy DHCP server providing boot information but no IP leases.

Any ip in the subnet will do, so you may just put your server NIC ip here.

Since dnsmasq is not providing true DHCP services, you do not want it

handing out IP addresses. Just put your servers IP address for the interface

that is connected to the network on which the FOG clients exist.

If this setting is incorrect, the dnsmasq may not start, rendering

your proxyDHCP ineffective.

dhcp-range=[B]10.0.0.10[/B],proxy

I hope that helps you.

Sivasubramaniam.T

Thanks a lot for your help Phantox. I will try tomorrow and let you know.

I have bit doubt in (dhcp-range=[B]10.0.0.10[/B],proxy) part. Can I give DHCP server IP B[/B] in place of [B]10.0.0.10[/B] as our ip range is in 172.17.x.x

Once again thanks for you help.

Phantox Jada

I didn’t put in my DHCP server IP. I put in the actual fog server IP. I do not know if that was the correct thing to do, but everything is running now.

Jaymes Driver

[quote=“Phantox Jada, post: 34379, member: 25158”]I didn’t put in my DHCP server IP. I put in the actual fog server IP. I do not know if that was the correct thing to do, but everything is running now.[/quote]

That is the correct thing to do, that is what the documentation tells you to do!

Rictor Rockets

EDIT/UPDATE: This article: [url]http://fogproject.org/wiki/index.php/Chainloading_PXE_to_iPXE_using_pxelinux.0[/url]
got things working at long last, at least as far as booting into the FOG Environment, and running the diagnostics mode. I haven’t tried actually imaging or uploading from any of our PC’s yet.

I WILL note that FOG now seems touchier than ever about switch equipment; on the other hand, I keep telling the PTB our switches are desperately in need of replacement, so maybe this will give them an extra kick in the butt

ORIGINAL POST:

Hi there,

I have been banging my head against this same problem. I just upgraded today from FOG 0.32 to 1.2.0 in Ubuntu 12.04

The DNSMasq trick worked like a charm…but now whenever we try to PXE boot, it craps out at this error:

/default.ipxe…Connection timed out ([url]http://ipxe.org/4c126035[/url])

We boot mostly Panasonic Toughbooks and HP Compaq Pro Elite workstations. We had NO problem in the past with PXE booting, not until this upgrade.

The chain http statement in that file is pointing to the correct IP address of the FOG server, and when we run the URL through, we get an output that appears as expected.

Any ideas?

xunil

Hi there,

I updated yesterday from 1.1.2 to 1.2.0, then i get the same error,
after reading the post, i installed & configure dnsmasq.

then now i got this error :

PXE-T01: File not found
DASH-E3B: TFTP Error - File not found
DASH-M0F: Exiting Option ROM

The DHCP score options 66 & 67 are good (like for the 1.1.2)
i tried to restore old tftpboot directory, same error.
i check the dnsmasq, don’t see any errors.

Fog is installed on a Ubuntu 14.04

ps sorry for my bad english