![]() When a boot protocol is set in RouterBoot, it is remembered: any of the methods here that force a netboot will then use the BOOTP or DHCP boot protocol previously selected in RouterBoot. However, if you have chosen to use a DHCP/BOOTP/ TFTP netboot server that supports rfc951 BOOTP such as dnsmasq or Tiny PXE (with rfc951=1 set in the section of the config.ini), any of these netboot methods will work fine without any changes to the Routerboot boot protocol. ![]() The instructions in this wiki tend to assume you have changed the netboot protocol to DHCP since DHCP netboot is supported by all DHCP servers. Not all RouterBoard devices can boot OpenWRT via DHCP. You can change the RouterBoot boot protocol from BOOTP to DHCP by using the COM port or RouterOS, as documented in this list of netboot methods. The RouterBoard default boot protocol is BOOTP. If it refuses to accept an initramfs image above that size (it will proceed to boot whatever was already installed in the device), that could be the reason.ĭownloading OpenWrt images for Mikrotik RouterBoardsĬonnect the ethernet 1 port of your routerboard (typically the WAN port) to a network configured to reach the DHCP/BOOTP/ TFTP server that you have set up. Note: MikroTik's bootloader ( routerboot) may have a size limitation for TFTP images, approximately 7MiB. Once you are happy with the RAM-based operation of OpenWrt, proceed to the step of flashing OpenWrt in order to permanently write OpenWrt into your RouterBoard. If the RAM-based initramfs version you have selected works for you, feel free to try other versions of OpenWrt, such as Latest release or snapshot. When you power down your RouterBoard after loading an initramfs file, OpenWrt will simply vanish: a power down and reboot of the RouterBoard will revert to the prior version of firmware that is still in flash of the RouterBoard. Since an initramfs image is just a temporary image (only loaded into RAM), it is safe to test a particular version of OpenWrt by netbooting (using DHCP/BOOTP/ TFTP) and downloading the initramfs image. This is explained in the model specific wiki pages.įirst Things First: Don't Lose Your RouterOS License Prior versions of OpenWrt required a subsequent upgrade to once again boot OpenWrt using initramfs: with the current version of OpenWrt that now uses Unsorted Block images (UBI), the initial flash and subsequent upgrades can be performed directly in-place from the LuCI web interface.Īfter OpenWrt is installed to Flash, depending on the model, some platform configuration may be needed. In this way, an initial installation is treated exactly the same as a subsequent OpenWrt upgrade. ![]() bin image into the flash of the RouterBoard. Once you have verified OpenWrt is working on your MikroTik hardware, use the LuCI web interface to permanently flash the appropriate sysupgrade. This RAM-based initramfs OpenWrt image is first used to validate the desired OpenWrt version operates properly without overwriting any existing image in the NAND or NOR flash of the RouterBoard. elf (.bin in some instances) images via TFTP. I've seen some forum post where the first part can be solved by just connecting 2 cables and then assign different IP for each interface.Īs you may notice, I'm really raw in networking and routing, so any GUI/Winbox instruction is appreciated, but CLI commands would be just fine.RouterBoards can netboot OpenWrt initramfs. The device that gives me the WAN link only has 1 "out" port, so there is no way to put 2 cables from the "modem" to the Mikrotik, right now there is 1 cable going from the modem to the Mikrotik device. Any PC from 192.168.85.X trying to access should use WAN IP2 to browse and navigate to that website (while all the rest of the traffic goes through WAN IP1).Any PC from 192.168.85.X should use WAN IP1 and use internet with it.What I'm trying to achieve is to add a second WAN ip to the router, and route traffic to a specific server to use that IP. So far I've configured the network to use one of those public IP and use it for 2 subnets (192.168.85.X and 192.168.5.X) wich are isolated from each other and both can access internet. I have a network with static IP and some public IP (248 mask). After 20 pages of SO results about Mikrotik and some more google results, I'm come here, down on my knees to request some enlightment.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |