DNSMASQ setup help

[mati-92]

[mati-92]

the error i get from the PXE boot is this

DHCP (net0 08:00:27:6b:7e:bc)… ok
net0: 10.0.2.15/255.255.255.0 gw 10.0.0.2
Next server 10.0.2.4
Filename: ub2.pxe
tftp://10.0.2.4/ub2.pxe… permission denied
no more network devices
FATAL: could not read from the boot medium! system halted

[Wayne Workman]

@mati-92 What is 10.0.2.4 ? what is 10.0.0.2 ? What is ub2.pxe ?

and

do you have a static IP set on your FOG server - and a reservation made on your home network device’s DHCP configuration?

What is your FOG server’s IP?

[mati-92]

my fog servers IP address is 192.168.0.14 and i have made reservations on the DHCP of my router for that address.

[Wayne Workman]

@mati-92 And the other IPs? Do you have a pre-existing network-boot environment?

[mati-92]

i have no idea what the 10.0.0.2 ip addresses are i have had a look in the conf files and i cant see these address in there, could these address be because i am using virtualbox ?i also have no idea what the ub2.pxe my current ip scheme for the entire house is between 192.168.0.1- 192.168.0.255. no pre-existing boot enviroment.

[Wayne Workman]

@mati-92

In such case - please try this as your ltsp.conf file:

port=0
log-dhcp
tftp-root=/tftpboot
dhcp-boot=undionly.kpxe,192.168.0.14,192.168.0.14
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=192.168.0.14,proxy

Then run this command:

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

Then ensure dnsmasq is running like this:

sudo service dnsmasq enable
sudo service dnsmasq restart

See if you can get a status after restarting dnsmasq like this, note any errors:

sudo service dnsmasq status

For future readers, the last three commands are Ubuntu/Debian specific.

[mati-92]

i got this error

[mati-92]

i found the issue with i put a wrong symbol in line 11 im going to test it now

[mati-92]

i ran a test on it and i am still getting that message when trying to boot via pxe

[Wayne Workman]

@mati-92 Check the target computer’s firmware settings. I’ve noticed on some that there are options for network booting that you can set in the firmware itself, such as target server and boot file.

[mati-92]

a little bit of progress i set both vm machines to bridge adaptors. i then boot via pxe on the 2nd vm and the following comes up.

[Wayne Workman]

@mati-92 Well if it’s asking for undionly.0 then give that to it lol.

make a sym-link for it:

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

Good to see progress!

[mati-92]

[Wayne Workman]

@mati-92 Can you post your current ltsp.conf file and then the output of this command again, please?

ls -lahRt /tftpboot

[mati-92]

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