DNSMASQ setup help

[Wayne Workman]

@mati-92 the sym-link for the undionly.0 file points to a nonsense location.

Delete that and recreate it.

rm -rf /tftpboot/undionly.0
ln -s /tftpboot/undionly.kpxe /tftpboot/undionly.0

[mati-92]

@Wayne-Workman tried the last thing you suggested and i tried it again and still not working.

[Wayne Workman]

Can you run this (I apologize but I need to make sure you got it right).

ls -lahRt /tftpboot

And please provide another photo of any error you’re seeing when trying to network boot.

[mati-92]

[Wayne Workman]

I’d like for you to run these commands and then provide another screen shot of the output of the below command.

rm -f /tftpboot/undionly.0
rm -f /tftpboot/undionly.kpxe.0

[mati-92]

[Wayne Workman]

@mati-92 Does it work now?

[mati-92]

@Wayne-Workman im afraid not i tried it from a physical computer sat on the network and i get tftp open timeout error

[mati-92]

[Tom Elliott]

@mati-92 There’s a typo.

unionly.0 should be undionly.0 MISSING A LETTER D

[mati-92]

@Wayne-Workman said:

ln -s /tftpboot/undionly.kpxe /tftpboot/undionly.0

i checked through all my commands ran from today and edited this one

ln -s /tftpboot/undionly.kpxe /tftpboot/undionly.0 ( i had forgotten the d off the last bit. i ran tried booting from my other virtual machine same error

[Wayne Workman]

@mati-92 Now try this:

ln -s /tftpboot/undionly.kpxe /tftpboot/undionly.kpxe.0

[mati-92]

im afriad i am still getting this error message … connection timed out

[Wayne Workman]

@mati-92 make sure your firewall is off. See if you can tftp and get the undionly.kpxe.0 file. Examples of both of those are here: https://wiki.fogproject.org/wiki/index.php/Troubleshoot_TFTP

[mati-92]

i have no setup in fedora 22 server, i followed the article you left me with last night and this is what i am getting when trying to boot to pxe. im using vm player now as i was having issues in virtualbox installing fedora.

[Wayne Workman]

I helped @mati-92 get past the dnsmasq issues via TeamViewer. however the virtual host he’s trying to network boot is trying to get default.pxe from a strange IP address instead of the virtual fog server.

ideas?

[Tom Elliott]

Is the virtual fog server’s network bridged or natted?

[Wayne Workman]

It was originally NAT’d but I couldn’t figure out why the virtual host was trying to pull default.pxe from the weird IP, so I tried to set it up as bridged and that did not work out at all.

Then I tried to get DHCP installed on the fog server and then put it on an isolated virtual lan but I couldn’t get DHCP to even install.

I am in over my head on this one - I suggested he install on physical software and try then with dnsmasq but he is saying Fedora 22 doesn’t work on his G5 server which I have reservations about… I’m not sure where to go from here - a fresh pair of eyes are needed.

[mati-92]

Morning just a quick update I managed to install fedora 22 on my poweredge sc1425 install fog tried to boot but no look.

[mati-92]

been thinking today that i might give up on this, not as easy as it looks. having many issues.