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 08:00] – [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 80: 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 113: 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 126: 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: 
  • Last modified: 2024/11/24 08:16
  • by nc1