May you try to follow steps from this video https://www.youtube.com/watch?v=GIijZ6_i55g in order to Netinstall your device?Is there anybody who will guide me through the process?
Me tooUpdated through Winbox, pressed "Download and install". Previous version was 6.40.4. Connection was over cable. Maybe it depends on this?
What was already done:
1) Tried reset to default config - NO RESULT
2) Tried NetInstall 6.40.5/6.40.4/6.38 - NO RESULT (device is not visible)
3) Tried changing from 100Mbps to 1Gbps speed (thought it may be the reason. Based on RouterBOOT changelog: https://wiki.mikrotik.com/wiki/RouterBOOT_changelog) - NO RESULT (device is not visible)
4) Tried holding reset for more then 300 sec (based on this manual: https://wiki.mikrotik.com/wiki/Manual:R ... bootloader) - NO RESULT. Router reboots even before 300 sec are passed.
Just found those devices in my collection. Would it be enough to get any useful information about the reasons of such disaster? I am interested to solve this problem as fast as i can (if i can ). - NO RESULT (device is not visible)
Is there anybody who will guide me through the process?
If it is disabled by default, then i have not enabled it.If you are not able to Netinstall the device, then maybe you have protected bootloader enabled?
https://wiki.mikrotik.com/wiki/Manual:R ... bootloader
8 R address=::/0 passive=yes auth-method=pre-shared-key secret="AAAAAAAA" generate-policy=port-strict
policy-template-group=l2tp exchange-mode=main-l2tp send-initial-contact=yes nat-traversal=yes proposal-check=obey
hash-algorithm=sha1 enc-algorithm=aes-256,aes-192,aes-128,3des dh-group=modp2048,modp1024 lifetime=1d dpd-interval=2m
dpd-maximum-failures=5
9 DR address=::/0 passive=yes auth-method=pre-shared-key secret="BBBBBBBB" generate-policy=port-strict
policy-template-group=default exchange-mode=main-l2tp send-initial-contact=yes nat-traversal=yes proposal-check=obey
hash-algorithm=sha1 enc-algorithm=aes-256,aes-192,aes-128,3des dh-group=modp2048,modp1024 lifetime=1d dpd-interval=2m
dpd-maximum-failures=5
Well, 80% of my network runs 6.40.4 and 95% of that has fixed configured rates across a whole range of different devices but so far never got the attention to strange system lock-up or reboots..Wireless fix is made for configurations where nv2 and configured rates are used. If you experienced system lock-up or reboots, then this fix will most likely will solve the problem.
It is not a valid configuration. You cannot predict which peer will be used. Probably in older version static peer was added later so it was not used. After reboot/upgrade static peer became more preferred.Found possible problem point. I have two almost similar ipsec peers:
try my way of getting Netinstall work.
do not capitulate!I am having the exact same problem - upgraded a client's hAP ac from 6.40.4 to 6.40.5 and it gets stuck in a boot loop.
I am unable to recover it using any of the techniques listed in this thread - I cannot get it into Netinstall mode (I have successfully done this several times before with other Mikrotik hardware) no matter what I do. I also tried the 300-second reset button hold technique - it has no effect and the hAP ac continues to boot loop as if I hadn't pressed the button.
I realize I should have checked to see if anyone was having difficulties with v6.40.5 before I started the package upgrade process, but I've never had this problem with any Mikrotik gear before.
Any ideas? I consider myself a fairly savvy user and support a number of offices with Mikrotik gear.
thanks!
Norm
Maybe the new naming for the firmware blocks, a direct update to the last stable.Just out of curios: as i tried to upgrade MT under 6.39.1 with "/system package update install" it upgraded to 6.40.4. After the upgrade and reboot I issued the same command and it offered me 6.40.5.
So the whole way was: 6.39.1 -> 6.40.4, and the 6.40.4 -> 6.40.5. Why it won't tried to do the whole process in one step, like 6.39.1 -> 6.40.5?
Strange for me!
Noop, the f/w still named as 3.41, not this weird new way ) And this was current branch all the way as I applied the updates.Maybe the new naming for the firmware blocks, a direct update to the last stable.
Check the Log. Seems like you have expired license.but in others I downloaded the package, it restarted but when starting again it continues with version 6.40.4. Try downloading the package from the CHR and downloading it from the page and copying it to the CHR. Same mistake.
:local result [/ping 200.200.200.201 count=15]
:global status
:if ($result = 15 && $status != true) do={
tool sms send usb2 phone-number=8888888 message="SERVER UP"
:log info "UP SMS"
:set status true
} else={
:if ($result = 0 && $status != false) do={
tool sms send usb2 phone-number=8888888 message="SERVER DOWN"
:log info "DOWN SMS"
:set status false
}
}
21:58:23 system,info netwatch host modified by admin
21:58:41 script,info UP SMS
21:59:49 system,info netwatch host modified by admin
22:00:08 script,info DOWN SMS
admin@Fa1c0n] /tool netwatch> print
Flags: X - disabled
# HOST TIMEOUT INTERVAL STATUS SINCE
0 200.200.200.200 1s 1m up nov/07/2017 20:45:00
1 200.200.200.201 1s 1m30s up nov/09/2017 21:59:49
2 200.200.200.202 1s 3m up nov/07/2017 20:51:20
Same here, SMS text garbled on RB411UAHR (factory reset done after upgrade 6.40.5), and also on router upgraded from 6.40.4 to 6.40.5 , Sierra Wireless MC8792Vtool sms inbox message error
all message recib error
CCR1009-8G-1S-1S+
May/11/2001 07:15:07 GMT +11 a ekKECAdKGSESIC$o @@@@@@
SL@@@@@@d$@@@@@@@Xe@@@@@@@@*CUw@@@@@Ru=o$@@@@oae@@@@@@L;D@@@@@@0:haA
@@@@(@@@@@@
Code: Select all
# jan/02/1970 00:35:16 by RouterOS 6.33.5
/interface bridge
add name=bridge1
/interface wireless security-profiles
add authentication-types=wpa2-psk eap-methods="" management-protection=allowed \
mode=dynamic-keys name=LLP supplicant-identity=""
/interface wireless
set [ find default-name=wlan1 ] band=2ghz-b/g/n disabled=no frequency=auto \
mode=station-pseudobridge-clone security-profile=LLP ssid=LLP \
wireless-protocol=802.11 wps-mode=disabled
/interface bridge port
add bridge=bridge1 interface=wlan1
add bridge=bridge1 interface=ether1
/ip cloud
set update-time=no
/ip service
set telnet disabled=yes
set ftp disabled=yes
set api disabled=yes
set api-ssl disabled=yes
Hi jarda,My similar experience many years ago teached me not to rename the ports. I use comments to mark the ports by their meaning instead and keep the original port names.
Ahhhh the first victim of the new firmware version notation keeping in touch with the RouterOS version notation.Could you please use the proper forum sections and not pollute a firmware announcement topic?need abit of CRS326 help.
...
"Also you can try to power off router, press and hold reset button. power router on and release the button."
tried, no luck
I do not have any serial cable. What should i do? (hAP AC was bought a week ago)
Tried patch cord + netinstall... The device reboots and invisible in Netinstall app
I've also noticed a slight cpu (not as much as yours) increase on CCR1036 after upgrading to 6.40.5 from 6.38.x.increase in cpu usage to 16% from 1% on RB3011UiAS
Code: Select all
/sys script
add name=clear_voip_conntrack owner=admin policy=read,write source="/ip firewall connection remove [find dst-address ~ \":4569\"];\r \n/ip firewall connection remove [find dst-address ~ \":5060\"];\r \n"
/ppp profile
add change-tcp-mss=yes name=voip-reset-conntrack on-down="/sys script run clear_voip_conntrack" on-up="/sys script run clear_voip_conntrack"
/interface pppoe-client
add interface=ether1 keepalive-timeout=60 name=ADSL password=***** profile=voip-reset-conntrack user=user@realm
That is not a vulnerability. Somebody made a ping script that floods the device, and result is that CPU usage rises.Dear Mikrotik Team
A DoS vulnerability has been released to RouterOS 6.40.5.
https://cve.mitre.org/cgi-bin/cvename.c ... 2017-17538
https://www.exploit-db.com/exploits/43317/
What kind of schedule is correspondence such as update?
Best regards.