Hello everybody. I want to ask for help with my task.
I can’t configure network boot via TFTP on Mikrotik. I tried various instruction but result is the same, I can’t boot PC via PXE on Mikrotik.
Here is my configuration:
Mikrotik RB3011, ROS 6.39.2, SeliconPower USB 2.0 drive 16Gb
Bootloader - pxelinux.0
I have network boot server working under Debian with various images and it works fine.
I decided to configure such network boot service using mikrotik. I’ve formatted USB drive to ext2, but when it becomes clear that my configuration isn’t working, I tried to change filesystem to fat32 but it didn’t help me.
In general I’ve done such steeps:
DHCP configuration
Formatting USB drive
Moving files to USB
TFTP configuration
Any advices?
Screenshots:
PS: Tell me if you need additional information.
I´m trying to do the exact same thing, and get “tftp: ERROR: code 0” in the log.
My target is to have a PXE Clonezilla on the router, I have tried out several different PXE images (Fedora, Ubuntu, Clonezilla, Kali and more) and can´t get any of them to work..
Don’t assume you know what the problem is, even if you see messages on the server end. Do a packet sniff and open it up in Wireshark to see if it looks like the the problem you think it is. It’s hard to know exactly what the client is doing because there are usually no messages on the client end. So look at the traffic to see what it’s doing.
Maybe the “req. filename” vs. “real filename” thing is an issue? Did you try putting the boot file in the actual tftp root dir? I don’t know if that’s even relevant on a MikroTik TFTP server, I’ve never tried one.
(I learned most of what I know about netbooting using NetBSD as a boot server and client in the late 90s/early 2000s and haven’t done much since…)
I made a Wireshark trace, but I can´t really see the problem..
The PXE client sends a request to read the file “default” as configured in the DHCP servers ´Boot File Name field´, the router answers with the file length.
Next the PXE client sends an error code “Code 0, Not defined, Message: TFTP aborted”
And after that the PXE client sends a new request to read the “default” file, the router sends an acknowledge and then transmit the “default” file, and the PXE client makes an acknowledge after receiving the file.
Thats it, nothing more is happening.
I belive I may have a problem in the “default” file, I think the PXE client should request to get the boot image and start the boot sequence after the last ack.
You try to transmit kernel, initrd and filesystem via tftp? This will be no fun as the system would need ages to boot, caused by the single-block lockstep schema. IMHO pxe booting from a Mikrotik device does not make any sense until they decide to implement a simple web server at least.
