Automatically Upgrade you router firmware & OS (v.7.x).

 

Automatically Upgrade you router firmware & OS (v.7.x).


/system/script

add dont-require-permissions=no name=RB_Upgrade owner=reinis policy=\
    ftp,reboot,read,write,policy,test,password,sniff,sensitive,romon source=":if\
    \_([/system routerboard get current-firmware] != [/system routerboard get up\
    grade-firmware]) do={\
    \n\r\
    \n/system routerboard upgrade;\
    \n\r\
    \n:delay 10;\
    \n\r\
    \n/system reboot} else={\r\
    \n:log warning \"No RouterBoard update is available\"}\
    \n"



add dont-require-permissions=no name=system_upgrade owner=reinis policy=\
    ftp,reboot,read,write,policy,test,password,sniff,sensitive,romon source="/sy\
    stem/package/update/check-for-updates;\r\
    \n:if ([/system package update get status] = \"New version is available\") d\
    o={\
    \n\r\
    \n/system package update install;\r\
    \n\
    \n:delay 10s;\r\
    \n/system reboot} else={\r\
    \n:log warning \"No System package update is available\"}\
    \n"






/system scheduler

add interval=4w name=system_upgrade on-event=system_upgrade policy=ftp,reboot,read,write,policy,test,password,sniff,sensitive,romon start-date=2024-10-14 start-time=06:00:00
add interval=4w name=RB_Upgrade on-event=RB_Upgrade policy=ftp,reboot,read,write,policy,test,password,sniff,sensitive,romon start-date=2024-10-14 start-time=06:30:00




Popular posts from this blog

Mikrotik v.7 Using cell lock on LHG LTE18

Image
  There  is  a way to do a cell lock on EG18-EA modem, it worked for me on LHG LTE18 kit. All information below is taken from  this thread on the Quectel forum . You will need to figure out PHY-CELLID (ID of the cell itself) and EARFCN (frequency that will be locked as primary band). You can get a list of cells around you and corresponding frequencies using cell monitor via web UI or console with: Code:  Select all interface / lte / cell - monitor lte1 You will get something like this: Code:  Select all PHY - CELLID BAND EARFCN RSRP RSRQ RSSI AGE 247 B7 2850 - 99dBm - 9dB - 68dBm 1s 99 B7 2850 - 104dBm - 15dB - 79dBm 1s 258 B7 2850 - 107dBm - 16dB - 83dBm 1s 69 B7 2850 - 111dBm - 20dB - 79dBm 1s 362 B7 2850 - 115dBm - 20dB - 85dBm 1s Next, use the following command to  set a cell lock : Code:  Select all interface /...
Read more

IPSEC VPN - Invalid ESP packet detected (HMAC validation failed)

Image
https://kb.fortinet.com/kb/documentLink.do?externalID=FD33101 The ESP packet invalid error is due to an encryption key mismatch after a VPN tunnel has been established. When an IPSec VPN tunnel is up, but traffic is not able to pass through the tunnel, Wireshark (or an equivalent program) can be used to determine whether there is an encryption mismatch. A mismatch could occur for many reasons, one of the most common is the instability of an ISP link (ADSL, Cable), or it could effectively be any device in the physical connection. The following information is required to troubleshoot the problem. 1) Take a packet sniffer trace on both FortiGates. 2) Run the "diag vpn tunnel list” command a few times on both FortiGates when generating traffic that will pass through the tunnel. In the following example, the error message was seen on the recipient FortiGate: date=2010-12-28 time=18:19:35 devname=Kosad_VPN device_id=FG300B3910600118 log_id=0101037132 type=event subtype=ipsec pri=critica...
Read more