Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revisionBoth sides next revision
toh:fortinet:fortinet_fortiwifi_50e-2r [2024/11/24 07:54] – [OEM installation using the TFTP method] nc1toh:fortinet:fortinet_fortiwifi_50e-2r [2024/11/24 08:04] – [OEM installation using the TFTP method] nc1
Line 63: Line 63:
 ->  [[docs:guide-user:installation:generic.flashing.tftp]] ->  [[docs:guide-user:installation:generic.flashing.tftp]]
  
-Before you can install OpenWrt on this router, you need to have a TFTP server ready to serve the initial firmware. You need to remember (or write down) TFTP server's IP address and the file name for the firmware. By default, the device will look for a file named ''image.out'', but you can change that (read on to see how).+Before you can install OpenWrt on this router, you need to have a TFTP server ready to serve the initial firmware. As of this writing, OpenWrt for FWF-50E-2R is available only in snapshots, so the initial firmware image can be downloaded from here: 
  
-Before you begin, connect the router's console port to your management computer and start your console program using connection speed 9600 bps. Next, turn on your router. You will see output similar to this: +<code> 
 +https://downloads.openwrt.org/snapshots/targets/mvebu/cortexa9/openwrt-mvebu-cortexa9-fortinet_fwf-50e-2r-initramfs-kernel.bin 
 +</code> 
 + 
 +You need to remember (or write down) TFTP server's IP address and the file name for the firmware. By default, the router will look for a file named ''image.out'', but you can change that (read on to see how). 
 + 
 +Before you begin, while your router is still turned off, connect the router's console port to your management computer and start your console program using connection speed 9600 bps. Next, turn on your router. You will see output similar to this: 
  
 <code> <code>
Line 74: Line 80:
 Total RAM: 2GB Total RAM: 2GB
 Initializing boot device... Initializing boot device...
-Initializing MAC... egiga1+Initializing MAC... 
 Please wait for OS to boot, or press any key to display configuration menu. Please wait for OS to boot, or press any key to display configuration menu.
 </code> </code>
Line 93: Line 99:
 </code> </code>
  
-From here, you have several options. One is to use option **[R]: Review TFTP parameters** to check the current settings and then, go back to your TFTP server and set it up as the router expects. Another option is to change TFTP setting on the router to match the settings on the TFTP server (the ones you have written down) by using option **[C]: Configure TFTP parameters**. Regardless of which option you chose, when everything is ready, use option **[T]: Initiate TFTP firmware transfer** to download and run the initial firmware. Note that one of the FTFP settings is the port the router will use for the FTFP connection, so be sure to connect the FTFP server to the port on the router on which the router expects a connection. But before you do that, let's discuss yet another option.+From here, you have several options. One is to use option **[R]: Review TFTP parameters** to check the current settings and then, go back to your TFTP server and set it up as the router expects. Another option is to change TFTP settings on the router to match the settings on the TFTP server (the ones you have written down) by using option **[C]: Configure TFTP parameters**. Regardless of which option you chose, when everything is ready, use option **[T]: Initiate TFTP firmware transfer** to download and run the initial firmware. Note that one of the FTFP settings is the port the router will use for the FTFP connection, so be sure to connect the FTFP server to the port on the router on which the router expects a connection. But before you do that, let's discuss yet another option.
  
 There is option **G** not shown on the menu, which allows you to specify TFTP parameters interactively. In the opinion of this writer, this is the easiest path, so let's walk through it. There is option **G** not shown on the menu, which allows you to specify TFTP parameters interactively. In the opinion of this writer, this is the easiest path, so let's walk through it.
Line 107: Line 113:
 </code> </code>
  
-In the example above, the user agreed to default settings for TFTP server IP address and local (meaning, router's) IP address, but specified a different name for firmware file (this can be handy if you keep firmware files for several Fortinet devices, so you can tell which file to use with which device). Note that first thing you have been asked to do is to connect the FTFP server to port WAN1, so don't forget to do this.+In the example above, the user agreed to default settings for TFTP server IP address and local (meaning, router's) IP address, but specified a different name for the firmware image file (this can be handy if you keep firmware files for several Fortinet devices, so you can tell which file to use with which device). Note that first thing you have been asked to do is to connect the FTFP server to port WAN1, so don't forget to do this.
  
 When you enter (or confirm) all settings, the router will attempt to retrieve firmware from the TFTP server. If successful, it will ask you how you want to run the firmware:  When you enter (or confirm) all settings, the router will attempt to retrieve firmware from the TFTP server. If successful, it will ask you how you want to run the firmware: 
Line 120: Line 126:
 </code>  </code> 
  
-If you're nervous about irreparably breaking things, choose option **R**; this will tell the router to boot into OpenWrt but not to save it to storage. If you go this route, you will have to repeat the install procedure when you decide to actually install OpenWrt (it will run in-memory, but will not persist past reboot or shutdown). If you're ready to actually install OpenWrt, use option **D**. Either way, you will see the familiar OpenWrt boot sequence. When the boot sequence is complete, press **Enter** to gain OpenWrt command prompt.+If you're nervous about irreparably breaking things, choose option **R**; this will tell the router to boot into OpenWrt but not to save it to storage. If you go this route, you will have to repeat the install procedure when you decide to actually install OpenWrt (for now, it will run in-memory, but will not persist past reboot or shutdown). If you're ready to actually install OpenWrt, use option **D**. Either way, you will see the familiar OpenWrt boot sequence. When the boot sequence is complete, press **Enter** to gain OpenWrt command prompt.
  
 At this point, OpenWrt is running in-memory, so you need to write it to the persistent storage. To do that, you need to perform a sysupgrade. Disconnect your router from the FTFP server and connect one of the router's WAN ports to your upstream device. Test your Internet connection, for example, by pinging Google:  At this point, OpenWrt is running in-memory, so you need to write it to the persistent storage. To do that, you need to perform a sysupgrade. Disconnect your router from the FTFP server and connect one of the router's WAN ports to your upstream device. Test your Internet connection, for example, by pinging Google: 
Line 128: Line 134:
 </code> </code>
  
-If the connection is active, perform sysupgrade. As of this writing, OpenWrt for 50E-2R is available only in snapshots, so your sysupgrade command will look like this: +If the connection is active, perform sysupgrade. As of this writing, OpenWrt for FWF-50E-2R is available only in snapshots, so your sysupgrade command will look like this: 
  
 <code> <code>
  • Last modified: 2024/11/24 08:16
  • by nc1