I'm having a similar problem, but further along in the booting process.
First, you can specify option 66 "boot-file-name" by setting /ip dhcp-server network set <network> boot-file-name="pxelinux.0". This works great and pxelinux loads.
What I can't get working is the pxelinux config file. I'm using the new gpxelinux.0 from Syslinux. Pxelinux boots ok, but then fails to find a config file, even though pxelinux.cfg/default exists on my router. When I look in the Mikrotik log, it says the "reading from file", which means it should have passed it to the client. I'm using RouterOS 3.27 x86. I've tested this using VirtualBox and a physical machine booting from the network.
When I use the EXACT same setup using tftpd-hpa on linux everything works as expected.
When I use any other boot-file-name for loading in Mikrotik everything works as expected.
I'm wondering if Mikrotik is reading either TEXT or BINARY data from the pxelinux.cfg/default file, and pxelinux doesn't know how to handle it.
Mikrotik, can you shed some light on this? Normis, mrz?
A simple test:
- download syslinux here: http://www.kernel.org/pub/linux/utils/b ... .82.tar.gz
- extract gpxe/gpxelinux.0 and put in / of Mikrotik (/gpxelinux.0)
- create a folder in / of Mikrotik called pxelinux.cfg
- create an empty file inside called default with contents: SAY "Hello World"
- set boot-file-name="gpxelinux.0"
- allow TFTP access:
/ip tftp add req-filename=".*" allow=yes disabled=no
- boot a machine from the network. The message "Hello World" should be displayed. If it can't find pxelinux.cfg/default, you will get "Unable to locate configuration file" near the bottom of the screen.
Please test this and report back. This is primary reason I'm trying to use TFTP server on Mikrotik as it complements DHCP server nicely.
Here is a capture of the relevant log entries. The client IP is 192.168.33.252 and Router IP 192.168.33.1.
I'm not sure why incoming connection from is showing a weird IP. I have no idea who's IP that is. Mikrotik, could you also explain this while you're at it. Thanks.
You do not have the required permissions to view the files attached to this post.