Mikrotik netinstall
![mikrotik netinstall mikrotik netinstall](https://i.ytimg.com/vi/pCnZuGtxv34/hqdefault.jpg)
Use another (existing) OpenWrt router as the netboot server When using BOOTP as the boot protocol, be sure to disconnect from any other network devices (routers) since BOOTP has no provisions for Proxy DHCP or authoritative DHCP across multiple simultaneous BOOTP servers: there must be only one DHCP/BOOTP/ TFTP server running on the network. If you power up the RouterBoard and continue holding the reset button, it will automatically search for a BOOTP server: no need to change any of the RouterBoot settings from their default settings with this approach. To enable rfc951 BOOTP in Tiny PXE, the option 'rfc951=1' must be set in the section of config.ini file of Tiny PXE.Äownload the initramfs-lzma.elf file to your PC, enter it as the Boot file name in Tiny PXE, select your 192.168.88.X connection as the Option 54 DHCP server (be sure your PC is set to a static IP in the 192.168.88.2-192.168.88.254 range), and put Tiny PXE online. Tiny PXE will directly respond to the BOOTP request of the RouterBoard. With rfc951 BOOTP, there is no need to enter the RouterBoot console and change the boot protocol from BOOTP to DHCP. This is possibly the easiest way to netboot a RB493G since Tiny PXE implements rfc951 BOOTP.
![mikrotik netinstall mikrotik netinstall](https://i.ytimg.com/vi/dIvZZL01uQc/maxresdefault.jpg)
#Mikrotik netinstall portable
The freeware Tiny PXE project is a standalone portable Windows application that implements a DHCP server, BOOTP server, and TFTP server.